Downlink (DL) and Uplink (UL) Scheduling for Transmissions Above 52.6 GHz

Abstract

Some aspects of the present disclosure relate to apparatuses and methods for implementing downlink scheduling and uplink scheduling in communications above 52.6 GHz. For example, some aspects of the present disclosure relate to a base station. The base station includes a transceiver configured to communicate with a user equipment (UE) over a wireless network and a processor communicatively coupled to the transceiver. The processor determines that communication between the base station and the UE is within a frequency range above 52.6 GHz. In response to the determination, the processor overrides a frequency primary resource allocation (FDRA), modifies a resource block group (RBG) size, or modifies a resource indication value (RIV) determination. The processor generates a downlink channel indicator (DCI) based at least on one or more of the overridden FDRA, the modified RBG size, or the modified RIV determination. The processor transmits the DCI to the UE using the transceiver.

Description

[Technical Field]

[0001] The described aspects generally relate to downlink (DL) and uplink (UL) scheduling for transmissions above 52.6 GHz. For example, some aspects of the present disclosure relate to designs for frequency domain resource allocation (FDRA) and / or time domain resource allocation (TDRA). [Background technology]

[0002] A user equipment (UE) communicating with a base station (e.g., an evolved node B (eNB), a next generation node B (gNB), etc.) over a communication link can use an uplink control channel to transmit control information and measurement information to the base station and can use an uplink data channel to transmit data to the base station. The base station can use a downlink control channel to transmit control information to the UE indicating how to use resources on the uplink channel(s). Summary of the Invention

[0003] Certain aspects of the present disclosure relate to apparatus and methods for implementing downlink scheduling (DL) and uplink (UL) scheduling in transmissions above 52.6 GHz, for example, for a 3rd Generation Partnership Project (3GPP) release, such as Release 17 (Rel-17).

[0004] Some aspects of the present disclosure relate to a base station. The base station includes a transceiver configured to communicate with user equipment (UE) over a wireless network and a processor communicatively coupled to the transceiver. The processor determines that communication between the base station and the UE is within a frequency range including one or more frequencies above 52.6 GHz. In response to the determination, the processor overrides a frequency primary resource allocation (FDRA), modifies a resource block group (RBG) size, or modifies a resource indication value (RIV) determination. The processor generates a downlink channel indicator (DCI) based at least on one or more of the overridden FDRA, the modified RBG size, or the modified RIV determination. The processor transmits the DCI to the UE using the transceiver.

[0005] In some examples, to disable the FDRA, the processor is configured to set a bit width associated with the FDRA to 0. In some examples, to modify the RBG size, the processor is configured to modify the RBG size to a value greater than 16. In some examples, to modify the RBG size, the processor is further configured to modify a physical resource block (PRB) bundling size.

[0006] In some examples, to modify the RIV determination, the processor:

[0007] The radio access point is configured to determine a plurality of RIVs, remove one or more RIVs from the plurality of RIVs, and use remaining RIVs from the plurality of RIVs to signal the RIV to the UE.

[0008] In some examples, to modify the RIV determination, the processor is configured to determine a minimum allocated resource block (LRB) value and subtract the minimum LRB value from the one or more LRB values ​​to generate one or more modified LRB values. The processor is further configured to determine one or more RIVs using the one or more modified LRB values ​​and signal the RIVs to the UE using the determined one or more RIVs.

[0009] In some examples, to modify the RIV determination, the processor is configured to determine a plurality of RIVs, select one or more RIVs from the plurality of RIVs for signaling information other than the RIV to the UE, and use the remaining RIVs from the plurality of RIVs to signal the RIV to the UE.

[0010] Some aspects of the present disclosure relate to a method that includes, in response to determining, by a base station, that communication between the base station and a user equipment (UE) is within a frequency range that includes one or more frequencies above 52.6 GHz, disabling a frequency primary resource allocation (FDRA), modifying a resource block group (RBG) size, or modifying a resource indication value (RIV) determination, the method further includes generating, by the base station, a downlink channel indicator (DCI) based at least on one or more of the disabled FDRA, the modified RBG size, or the modified RIV determination, and transmitting, by the base station, the DCI to the UE.

[0011] Some aspects of the present disclosure relate to a non-transitory computer-readable medium storing instructions. When executed by a processor of a base station, the instructions cause the processor to perform operations including disabling a frequency primary resource allocation (FDRA), modifying a resource block group (RBG) size, or modifying a resource indication value (RIV) determination in response to determining that communication between the base station and a user equipment (UE) is within a frequency range that includes one or more frequencies above 52.6 GHz. The operations further include generating, by the base station, a downlink channel indicator (DCI) based at least on one or more of the disabled FDRA, the modified RBG size, or the modified RIV determination, and transmitting, by the base station, the DCI to the UE.

[0012] Some aspects of the present disclosure relate to a user equipment (UE). The UE includes a transceiver configured to wirelessly communicate with a base station and a processor communicatively coupled to the transceiver. The processor receives, using the transceiver, a downlink channel indicator (DCI) from the base station in a frequency range above 52.6 GHz. The DCI is generated based on at least one of a nulled frequency primary resource allocation (FDRA), a modified modified resource block group (RBG) size, or a modified resource indication value (RIV) determination. The processor further uses the transceiver to communicate with the base station using information related to the DCI.

[0013] In some examples, the DCI includes an FDRA field including a bit width set to 0. In some examples, the modified RBG size is set to a value greater than 16. In some examples, the DCI includes an RIV determined from a plurality of RIVs in which one or more RIVs are removed. In some examples, the DCI includes an RIV determined from a plurality of RIVs, the plurality of RIVs being determined based on modified allocated resource block (LRB) values. In some examples, the DCI includes an RIV determined from a plurality of RIVs in which one or more RIVs are used to signal information other than the RIV to the UE.

[0014] Some aspects of the present disclosure relate to a method performed by a user equipment (UE). The method includes receiving a downlink channel indicator (DCI) from a base station in a frequency range above 52.6 GHz. The DCI is generated based on at least one of a nulled frequency primary resource allocation (FDRA), a modified modified resource block group (RBG) size, or a modified resource indication value (RIV) determination. The method further includes communicating with the base station using information related to the DCI.

[0015] Some aspects of the present disclosure relate to a non-transitory computer-readable medium storing instructions. When the instructions are executed by a processor of a user equipment (UE), the instructions cause the processor to perform operations including receiving a downlink channel indicator (DCI) from a base station in a frequency range above 52.6 GHz. The DCI is generated based on at least one of a nulled frequency primary resource allocation (FDRA), a modified modified resource block group (RBG) size, or a modified resource indication value (RIV) determination. The operations further include communicating with the base station using information related to the DCI.

[0016] This Summary of the Invention is provided merely for the purpose of illustrating some aspects to provide an understanding of the subject matter described herein. Accordingly, the above features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter in this disclosure. Other features, aspects, and advantages of the present disclosure will become apparent from the following Detailed Description, Figures, and Claims. [Brief explanation of the drawings]

[0017] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate the present disclosure and, together with the description, further serve to explain the principles of the present disclosure and to enable one skilled in the art(s) to make and use the present disclosure.

[0018] [Figure 1] 1 illustrates an example system implementing a design for implementing downlink (DL) scheduling and uplink (UL) scheduling in transmissions above 52.6 GHz in accordance with certain aspects of the present disclosure.

[0019] [Figure 2A] 1 illustrates an exemplary shared transport block (TB) and time and frequency resource allocations in accordance with certain aspects of the present disclosure.

[0020] [Figure 2B] 1 illustrates one example shared transport block (TB) and time and frequency resource allocations for multiple transmission time interval (multi-TTI) (mutli-TTI) PUSCH transmission, in accordance with certain aspects of the present disclosure.

[0021] [Figure 3] 1 illustrates one example extended TDRA table for multi-TTI PUSCH scheduling, in accordance with certain aspects of the present disclosure.

[0022] [Figure 4] 1 illustrates one example table for resource indication values ​​(RIVs), according to some aspects of the present disclosure.

[0023] [Figure 5] 10 illustrates another example table for resource indication values ​​(RIVs), in accordance with certain aspects of the present disclosure.

[0024] [Figure 6] 1 illustrates a block diagram of an example system of electronic devices implementing mechanisms for downlink (DL) and uplink (UL) scheduling in transmissions above 52.6 GHz, in accordance with certain aspects of the present disclosure.

[0025] [Figure 7] 7 illustrates one example method 700 for a system (e.g., a base station) supporting mechanisms for downlink (DL) and uplink (UL) scheduling in transmissions above 52.6 GHz, in accordance with certain aspects of the present disclosure.

[0026] [Figure 8A] 8A-8C illustrate example methods 800, 820, and 840, respectively, for a system (e.g., a base station) supporting a mechanism for modifying resource indication value (RIV) determinations for transmissions above 52.6 GHz, in accordance with certain aspects of the present disclosure. [Figure 8B] 8A-8C illustrate example methods 800, 820, and 840, respectively, for a system (e.g., a base station) supporting a mechanism for modifying resource indication value (RIV) determinations for transmissions above 52.6 GHz, in accordance with certain aspects of the present disclosure. [Figure 8C] 8A-8C illustrate example methods 800, 820, and 840, respectively, for a system (e.g., a base station) supporting a mechanism for modifying resource indication value (RIV) determinations for transmissions above 52.6 GHz, in accordance with certain aspects of the present disclosure.

[0027] [Figure 9] 1 is an exemplary computer system for implementing some aspects or portion(s) of some aspects.

[0028] The present disclosure is described with reference to the accompanying drawings, in which like reference numbers generally indicate identical or functionally similar elements, and the left-most digit(s) of a reference number generally identify the drawing in which the reference number first appears. DETAILED DESCRIPTION OF THE INVENTION

[0029] Certain aspects of the present disclosure include apparatus and methods for implementing downlink scheduling (DL) and uplink (UL) scheduling in transmissions above 52.6 GHz for a 3rd Generation Partnership Project (3GPP) release, such as Release 17 (Rel-17), or other current / future 3GPP standards.

[0030] FIG. 1 illustrates an example system 100 implementing a design for implementing downlink (DL) and uplink (UL) scheduling for communication above 52.6 GHz according to some aspects of the present disclosure. The example system 100 is provided for illustrative purposes only and does not limit aspects of the disclosure. The system 100 may include, but is not limited to, a network node (e.g., a base station such as an eNB or gNB) 101 and an electronic device (e.g., a UE) 105. The electronic device 105 (hereinafter referred to as the UE 105) may include an electronic device configured to operate based on a wide variety of wireless communication techniques. These techniques may include, but are not limited to, techniques based on 3rd Generation Partnership Project (3GPP) standards. For example, the UE 105 may include an electronic device configured to operate using a 3GPP release such as Release 17 (Rel-17) or other current / future 3GPP standards. The UEs 105 may include, but are not limited to, wireless communication devices, smartphones, laptops, desktops, tablets, personal assistants, monitors, televisions, wearable devices, Internet of Things (IoT), and vehicular communication devices. The network nodes 101 (referred to herein as base stations) may include nodes configured to operate based on a wide variety of wireless communication techniques, including, but not limited to, techniques based on 3GPP standards. For example, the base stations 101 may include nodes configured to operate using a 3GPP release such as Rel-17 or other current or future 3GPP standards. The UEs 105 may be connected to and in communication with the base stations 101 using one or more communication links 107.

[0031] Some aspects of the present disclosure are directed to new numerologies (e.g., μ values ​​in 3GPP Technical Specification (TS) 38.211) for operation in a frequency range above 52.6 GHz (e.g., one or more frequencies in a frequency range between about 52.6 GHz and about 71 GHz). Some aspects of the present disclosure are directed to addressing an effect(s) on physical signals / channels in the frequency range above 52.6 GHz. For example, some aspects of the present disclosure describe timeline-related aspects adapted to each of the new numerologies, e.g., bandwidth portion (BWP) and beam switching time, hybrid automatic repeat request (Hybrid ARQ or HARQ) scheduling, UE processing, preparation and calculation times for the physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH) / sounding reference signal (SRS), and channel state information (CSI), etc. Some aspects of the present disclosure can support up to 64 signal block beam (SSB) beams for licensed and unlicensed operation in the frequency range above 52.6 GHz. Additionally or alternatively, some aspects of the present disclosure may use channel access mechanisms (single or multiple) that assume beam-based operation in order to comply with regulatory requirements applicable to unlicensed spectrum for frequencies between 52.6 GHz and 71 GHz.

[0032] Some aspects of the present disclosure are directed to frequency-domain scheduling enhancements / optimizations for PDSCH / PUSCH, such as, but not limited to, supporting UL scheduling when frequency-domain resource allocation with a granularity different from FR1 / 2 (e.g., sub-physical resource block (PRB) or two or more PRBs) is supported. Some aspects of the present disclosure are directed to time-domain scheduling enhancements for PDSCH / PUSCH, such as, but not limited to, increasing the minimum time-domain scheduling unit to be greater than one symbol, supporting multiple PDSCHs scheduled by one downlink control information (DCI), and supporting one transport block (TB) mapped to multiple slots (i.e., transmission time interval (TTI) bundling). Some aspects of the present disclosure are directed to enhancements and / or alternatives to the scheduling request mechanism to reduce scheduling latency due to beam sweeping.

[0033] According to some aspects, DL and UL scheduling (e.g., in Rel-15) can include time domain scheduling (e.g., using a time domain resource allocation (TDRA) field) and / or frequency domain scheduling (e.g., using a frequency domain resource allocation (FDRA) field). In some examples, the TDRA field can be transmitted using a DCI for DL ​​scheduling and / or UL scheduling. For example, the base station 101 can transmit the TDRA field to the UE 105 using a DCI. In some examples, the TDRA field can define a pointer to a row in a lookup table configured by radio resource control (RRC) message(s) and / or other 3GPP methods.

[0034] In some examples, time-domain scheduling can be based on mapping type A or mapping type B. In mapping type A, resource allocation can be slot-based and can include a demodulation reference signal (DMRS) symbol in symbol 2 (or 3). In mapping type B, resource allocation can be minislot-based and can include frontloaded DMRS. In some examples, the time-domain resource allocation can indicate a slot offset. For example, K0 can be used for DL ​​and K2 can be used for UL. Additionally or alternatively, the time-domain resource allocation can also indicate a starting symbol within a slot (S) and length (L). In one example in Rel-15, the time-domain resource allocation does not cross slot boundaries. In some examples, the time-domain resource allocation can also be encoded with a single number called a start and length indicator value (SLIV).

[0035] According to some aspects, the FDRA field can also be transmitted in DCI (DL and UL) and can define resource block allocation. For example, the base station 101 can transmit the FDRA field to the UE 105 using DCI. In some examples, the FDRA field can be transmitted using one or more of Type 0 DCI (non-fallback DCI only) and Type 1 DCI (fallback and non-fallback DCI). For non-fallback DCI, the radio resource control (RRC) can be configured as T0, T1, or dynamic switching (e.g., the MSB (Most Significant Bit) indicates the type).

[0036] In some examples, a BWP indicator may be used to identify a specific BWP for resource allocation (which may be used for BWP switching). According to some aspects, a resource allocation type specifies how the scheduler allocates resource blocks for each transmission. For example, DL / UL resource allocation type 0 may use a bitmap to indicate a set of allocated resource block groups (RBGs). In some examples, an RBG may be a set of contiguous virtual resource blocks (VRBs). The RBG size may also depend on the BWP size, and in some examples, the BWP size is configurable. As a non-limiting example, Table 5.1.2.2.1-1 (Nominal RBG Size P) and Table 6.1.2.2.1-1 (Nominal RBG Size P) of TS 38.214 may indicate the RBG size based on the BWP size for configuration 1 or configuration 2.

[0037] In some examples, in resource allocation type 1, resources are allocated to one or more contiguous RBs. For example, in the DL case, a resource indicator value (RIV) is used to allocate a set of virtual resource blocks (VRBs). The VRBs may be mapped to interleaved (distributed RA) or non-interleaved (localized RA) physical resource blocks (PRBs). In some examples, interleaved VRBs may be mapped using resource block bundling, e.g., using a set of contiguous RBs within a BWP that is different from the precoding granularity. In some examples, in the UL case, a resource indicator value (RIV) is used to allocate a set of VRBs mapped to a set of contiguous PRBs.

[0038] Additionally or alternatively, DL and UL scheduling may be considered with slot aggregation. In some examples, without slot aggregation, time domain resource allocations are not allowed to cross slot boundaries. In these examples, latency for aligning slot boundaries may be increased. In some examples, with slot aggregation, a repetition in the next slot uses the same time domain resource allocation as the transmission in the first slot.

[0039] Ultra-reliable low-latency communication (URLLC) is a set of features that provides low latency and ultra-high reliability. According to some aspects, the system 100 of FIG. 1 may be configured to provide PUSCH repetition information for Rel-16. In some examples, the UE 105 may be configured to transmit the number of repetitions over consecutive slots. The base station 101 may be configured to schedule and communicate the PUSCH repetition information to the UE 105. In some examples of DL and UL scheduling for Rel-15, the number of repetitions for PUSCH with slot aggregation may be semi-statically configured. In Rel-16, dynamic indication of the number of repetitions may be supported for PUSCH repetition type A using a mechanism similar to PUSCH repetition type B. In some examples, an additional column for the number of repetitions may be added to the TDRA table. The number of repetitions may be dynamically indicated as part of the TDRA entry, similar to repetition type B.

[0040] For both dynamic grants (DG) and configured grants (CG), the number of iterations may be provided by the number of iterations r16, if present in the corresponding TDRA table. In some examples, the number of iterations r16 is {1, 2, 3, 4, 7, 8, 12, 16} (3 bits), the same as the iteration type B. Otherwise, the number of iterations may be determined according to the Rel-15 procedure (pusch aggregation factor for DG and repK for CG).

[0041] According to some aspects, the system 100 can support PUSCH repetitions within one slot or across multiple consecutive slots using ULLRC PUSCH repetition type B. In some examples, the system 100 can support both dynamic grants (DG) and configured grants (CG) (Type 1 and Type 2). According to some examples, the base station 101 can schedule PUSCH repetition type B via DCI format 0_1 / 0_2 instead of DCI format 0_0. In some examples, the base station 101 can configure and communicate a TDRA to the UE 105 (e.g., using a DCI). The base station 101 can define the TDRA using S (starting symbol), L (length of each nominal repetition), and K (number of nominal repetitions). For example, the TDRA field in the DCI or Type 1 CG configuration can point to one of the entries in a TDRA table, which provides values ​​for S, L, and K.

[0042] According to some examples, PUSCH transmission from the UE 105 may occur within a time window of L×K symbols, starting from the indicated starting symbol. Each nominal repetition may be segmented into one or more actual repetitions depending on the slot boundary and the UL / DL direction of the symbol. If a "nominal" repetition crosses a slot boundary or a DL / UL switch point, this "nominal" repetition may be split into multiple PUSCH repetitions, one PUSCH repetition for each UL period within the slot.

[0043] In some examples of ULLRC PUSCH repetition type B, DMRS sharing across multiple repetitions is not implemented, only PUSCH mapping type B is supported, and the TBS is determined based on L.

[0044] According to some examples, multi-TTI PUSCH transmission in Rel-15 includes repeated transmissions in time to support URLLC or to ensure UL coverage. Figure 2A illustrates one exemplary shared transport block (TB) and time and frequency resource allocations in accordance with certain aspects of the present disclosure. For example, as shown in Figure 2A, transport block (TB) 201 may be scheduled for multiple slots 203a-203d. In some examples, multi-TTI PUSCH transmission in Rel-16 NR-U may target scheduling multiple slots and / or minislots 213a-213d with different transport blocks (TBs) 211a-211d using a single UL grant, as shown in Figure 2B. Figure 2B illustrates one exemplary shared transport block (TB) and time and frequency resource allocations for multi-TTI PUSCH transmission in accordance with certain aspects of the present disclosure. The exemplary Figure 2B can result in higher efficiency and increased UL transmission probability.

[0045] According to some aspects, common fields for DCI formats for multi-TTI PUSCH for Rel-16 NR-U are provided in Table 1. [Table 1]

[0046] The HARQ process number in Table 1 signaled in the DCI is applied to the first scheduled PUSCH. The HARQ process number is then incremented by one for subsequent PUSCHs in scheduled order (modulo arithmetic if necessary). The time domain RA in Table 1 supports consecutive time domain resource allocation for at least Type A and Type B PUSCHs.

[0047] Certain aspects of the present disclosure are directed to systems and methods for minimizing DCI overhead, eg, time domain resource allocation, frequency domain resource allocation, and the like.

[0048] In some examples, multi-TTI PUSCH scheduling in Rel-16 NR-U can be supported using DCI format 0_1. In these examples, the TDRA table configuration allows for single or multiple consecutive PUSCHs to be indicated in any of multiple scheduled slots. In some examples, the maximum number of PUSCHs in a row may be eight, although aspects of the present disclosure are not limited to this example. According to some aspects, the number of NDI bits and RV bits in DCI format 0_1 ​​may be determined based on the configured TDRA table. For example, if multiple PUSCHs are scheduled, one RV bit is used per PUSCH, with a value of {0, 2}. Alternatively, if only a single PUSCH is scheduled, two RV bits are used for the PUSCH.

[0049] According to some aspects, the legacy TDRA table is extended so that each row indicates multiple PUSCHs (consecutive in the time domain). An exemplary extended TDRA table 300 for multi-TTI PUSCH scheduling is shown in FIG. 3. Column 301 of FIG. 3 indicates the TDRA index. Column 303 of FIG. 3 indicates the K2 value. Column 305 of FIG. 3 indicates the SLIV. Column 307 of FIG. 3 indicates the mapping type. In some examples, as shown in FIG. 3, each PUSCH can have a separate SLIV and mapping type. The number of scheduled PUSCHs can be signaled by the number of indicated valid SLIVs in a row of the TDRA table, which is signaled in the DCI. An exemplary PUSCH allocation 309 associated with each TDRA index is also shown in FIG. 3.

[0050] According to some aspects, the system 100 is configured to operate in a frequency range above 52.6 GHz. In some examples, the range above 52.6 GHz can include a frequency range from about 52.6 GHz to about 71 GHz. In some examples, in the frequency range above 52.6 GHz, the base station 101 and the UE 105 can communicate using narrow beams due to wavelengths in the frequency range above 52.6 GHz. In these examples, there is a high probability that only one or two UEs will match a single beam. In these examples, the scheduler may only need to transmit to a single (or a few) UEs, particularly in the downlink. Thus, the base station 101 does not need to transmit scheduling information for many UEs. Therefore, the granularity of frequency domain resource allocation (FDRA) may be reduced to reduce overhead in DCI.

[0051] According to some aspects, the scheduler is configured to perform a scheduling process. The scheduling process may include a process of allocating resources for transmitting data and may be performed by the network, and the UE may follow a schedule communicated by the network. In some examples, the scheduler may be part of the base station 101. Additionally or alternatively, the scheduler may be separate from the base station 101 but part of a network associated with the base station 101 and coupled to the base station 101. Aspects of the present disclosure are not limited to these examples, and the scheduler may have other architectures. In some examples, the scheduler may receive information such as, but not limited to, measurements (from the UE 105 and / or the network), buffer status reports (BSRs), quality of service (QoS) requirement(s), associated radio bearers, scheduling requests (SRs), etc. Using one or more of this information, the scheduler may determine a resource allocation and communicate the resource allocation to the UE 105.

[0052] According to some aspects, the subcarrier spacing (SCS) may be increased to address phase noise in the frequency range above 52.6 GHz. Increasing the SCS may result in a reduction in the duration of a symbol. Reducing the duration of a symbol (e.g., a slot) may result in an increase in the number of DCIs that need to be decoded within a particular time interval and associated scheduling. In some examples, the system 100 of FIG. 1 may be configured to increase the minimum time-domain scheduling unit to greater than one symbol, support multiple PDSCHs scheduled by one DCI, and / or support one TB mapped to multiple slots (e.g., TTI bundling). Additionally or alternatively, aspects of the present disclosure provide methods and systems for TDRA to support these schemes. Also, aspects of the present disclosure provide TDRA methods and systems for factoring using multiple beams for a particular UE for multi-TTI transmissions.

[0053] As mentioned above, in some examples, the system 100 is configured to operate in a frequency range above 52.6 GHz. In these examples, a single UE or up to two UEs are in the beam, and the base station 101 may be configured to reduce the FDRA granularity.

[0054] According to some aspects, the base station 101 is configured to signal to the UE 105 that there is only one UE per transmission. For example, the base station 101 can signal to the UE 105 that when the base station 101 transmits to the UE 105, the transmission is only for the UE 105. In this example, the base station 101 does not signal an FDRA. Thus, the UE 105 does not expect to receive an FDRA and assumes that the UE 105 is allocated the entire bandwidth. In some examples, the base station 101 can indicate to the UE 105 that the FDRA bit width is 0. For example, the base station 101 can use an FDRA field in the DCI to indicate to the UE 105 that the FDRA bit width is 0.

[0055] The DCI may have different formats. For example, DCI format 0_0, format 0_1, format 0_2 (e.g., a URLLC-based DCI format for Rel-16), and / or format 0_x may be used for scheduling the PUSCH in one cell. For example, DCI format 1_0, format 1_1, format 1_2 (e.g., a URLLC-based DCI format for Rel-16), and / or format 0_x may be used for scheduling the PDSCH in one cell. The DCI may also include other formats, such as format 2_0, format 2_1, format 2_2, or format 2_3. The DCI may include an FDRA field used for frequency domain resource allocation. As described above, the base station 101 may disable the FDRA field in the DCI. For example, the base station 101 may use the FDRA field in the DCI to set the FDRA bit width to 0. Thus, the base station 101 can instruct the UE 105 not to expect to receive an FDRA and to assume that the UE 105 is allocated the entire bandwidth. In some examples, setting the FDRA bit width to 0 differs from disabling TDRA and using only RRC signaling. Disabling the FDRA field (e.g., setting the FDRA bit width to 0) can be UE specific and can be different for the UL and DL.

[0056] According to some aspects, the base station 101 may be configured to reduce FDRA granularity by modifying resource block group (RBG) size. As described above with respect to DL / UL resource allocation type 0, the RBG definition is specific to the BWP size. Because a BWP has a specific SCS, the RBG definition is SCS-specific and BWP size-specific. The current value of the RBG size is limited to a maximum of 16. For example, for BWPs 1 through 36, the RBG size is 2 for configuration 1 and 4 for configuration 4. For BWPs 37 through 72, the RBG size is 4 for configuration 1 and 8 for configuration 4. For BWPs 73 through 144, the RBG size is 8 for configuration 1 and 16 for configuration 4. Also, for BWPs 145 through 275, the RBG size is 16 for both configurations 1 and 4. Some aspects of the present disclosure are configured to modify the RBG size value. For example, the RBG size may be modified to have a value greater than 16 to reduce the FDRA granularity. Additionally or alternatively, the physical resource block (PRB) bundling size may be modified.

[0057] According to some aspects, the base station 101 may be configured to reduce the FDRA granularity by modifying the resource indication value (RIV) determination (e.g., modifying the RIV calculation). In some examples, the DCI may include the RIV. For example, the base station 101 may be configured to modify the RIV determination / calculation to use the minimum number of allocated RBs for resource allocation type 1. In this example, the maximum RIV value may be reduced, and the size of the FDRA field may be reduced.

[0058] In one example, the base station 101 may be configured to determine or estimate the RIV based on one or more parameters. The parameters may include, but are not limited to, one or more of the number of allocated resource blocks (LRBs), the allocated starting resource block, and the number of RBs in the bandwidth portion (BWP). The UE 105 may use the RIV to determine the allocated starting resource block and the number of allocated resource blocks. After determining or estimating the RIV, the base station 101 may be configured to remove any RIV that is less than or equal to an RIV threshold. For example, the RIV threshold may include a maximum RIV associated with a minimum LRB (LRBmin). After removing one or more RIVs, the base station may signal the RIV in the DCI based on the remaining RIVs in the table. This may be a simple way to reduce the maximum RIV and reduce the size of the FDRA field. In some examples, the RIV of the DCI may be determined as follows:

[0059]

number

[0060]

number

[0061] Here, L RB is the number of allocated resource blocks, and RB start is the allocated starting resource block,

number

[0062] A non-limiting example of modifying the RIV determination (e.g., modifying the RIV calculation) to use the minimum number of allocated RBs is shown in FIG. 4. FIG. 4 shows an example table 400 for RIV according to some aspects of the present disclosure. In this example, assume that the BWP has RB size=14 and the LRB min is 5. In this example, the maximum RIV associated with an LRB min of 5 is 52. In this example, the base station 101 removes RIVs that are less than the RIV threshold of 52. In other words, the base station 101 transmits RIVs between 53 and 104, which in this example reduces the RIV transmission by one bit, thus reducing the size of the FDRA field. Therefore, the base station 101 removes RIVs associated with LRBs 1, 2, 3, 4, 13, and 14 (columns 401 and 403 of FIG. 4). In this example, the base station 101 removes RIVs associated with LRBs smaller than the LRB min, and also removes RIVs associated with LRBs 13 and 14 (which are LRBs larger than the LRB min).

[0063] According to some aspects, in addition to or instead of removing any RIVs smaller than the maximum RIV associated with the LRB min, the base station 101 may be configured to determine or estimate an RIV table for a smaller number of allocated resource blocks. In other words, the base station 101 may change the resolution before determining or estimating the RIV. In this example, the base station 101 is configured to determine or assume a minimum LRB. The base station 101 may then subtract the minimum LRB value from the LRB value before determining or estimating the RIV. The base station 101 may then estimate the RIV. In this example, the RIV is effectively mapped to a resource block bundle (e.g., an RBB of size LRB min). For example, LRActual = LRBeff × LRBmin, where LRBeff is the number of allocated resource blocks. In this example, RIVs of any LRB size are not removed.

[0064] A non-limiting example of modifying the RIV determination (e.g., modifying the RIV calculation) by subtracting the minimum LRB value is shown in FIG. 5. FIG. 5 shows an example table 500 for RIV according to some aspects of the present disclosure. In this example, assume that the BWP has RBsize=14 and LRBmin is 5. The RIV is calculated as described above with respect to equations (1) and (2). In this example, the effective maximum RIV (RIVeffmax) is 46 (e.g., 5.5 bits) or 55 (e.g., 5.78 bits) compared to 104 (6.7 bits). In this example, higher level LRB values ​​are not removed.

[0065] According to some aspects, in addition to or instead of modifying the RIV table as described above, the base station 101 may be configured to use unused RIV values ​​to signal other information to the UE 105. Thus, the base station 101 can reduce the size of the FDRA field by using unused RIV values ​​to signal other information to the UE 105. For example, instead of deleting columns 401 and 403 of FIG. 4 (corresponding to LRBs 1, 2, 3, 4, 13, and 14), the RIVs in columns 401 and 403 of FIG. 4 may be used to signal other information to the UE 105.

[0066] 6 illustrates a block diagram of an example system 600 of an electronic device implementing mechanisms for downlink (DL) scheduling and uplink (UL) scheduling for communications above 52.6 GHz in accordance with some aspects of the present disclosure. System 600 may be any of the electronic devices of system 100 (e.g., base station 101, UE 105). System 600 includes a processor 610, one or more transceivers 620, a communications infrastructure 640, memory 650, an operating system 652, an application 654, and one or more antennas 660. The illustrated system is provided as an example portion of system 600, which may include other circuit(s) and subsystem(s). Also, while the components of system 600 are illustrated as separate components, aspects of the present disclosure may include any combination of these components, fewer components, or more components.

[0067] The memory 650 may include random access memory (RAM) and / or cache and may include control logic (e.g., computer software) and / or data. The memory 650 may also include other storage devices or memories, such as, but not limited to, a hard disk drive and / or a removable storage device / unit. According to some examples, an operating system 652 may be stored in the memory 650. The operating system 652 may manage the transfer of data from the memory 650 and / or one or more applications 654 to the processor 610 and / or one or more transceivers 620. In some examples, the operating system 652 maintains one or more network protocol stacks (e.g., an Internet protocol stack, a cellular protocol stack, etc.), which may include multiple logic layers. At a corresponding layer of the protocol stack, the operating system 652 includes control mechanisms and data structures for performing functions associated with that layer.

[0068] According to some examples, applications 654 may be stored in memory 650. Applications 654 may include applications (e.g., user applications) used by wireless system 600 and / or a user of wireless system 600. Applications in applications 654 may include applications such as, but not limited to, Siri™, FaceTime™, radio streaming, video streaming, remote control, and / or other user applications.

[0069] The system 600 may also include a communications infrastructure 640. The communications infrastructure 640 provides, for example, communication between the processor 610, the one or more transceivers 620, and the memory 650. In some implementations, the communications infrastructure 640 may be a bus. The processor 610, in conjunction with instructions stored in the memory 650, performs operations that enable the system 600 of the system 100 to implement mechanisms for downlink (DL) and uplink (UL) scheduling for transmissions above 52.6 GHz, as described herein.

[0070] According to some aspects, the one or more transmitters 620 may be coupled to an antenna 660. The antenna 660 may include one or more antennas, which may be of the same or different types. The one or more transceivers 620 enable the system 600 to communicate with other devices, which may be wired and / or wireless. In some examples, the one or more transceivers 620 may include a processor, a controller, a radio, a socket, a plug, a buffer, and similar circuits / devices used for connecting to and communicating in a network. According to some examples, the one or more transceivers 620 include one or more circuits for connecting to and communicating in a wired and / or wireless network.

[0071] According to some aspects of the present disclosure, the one or more transceivers 620 may include a cellular subsystem, a WLAN subsystem, and / or a Bluetooth™ subsystem, each including their own radio transceiver and protocol(s), as would be understood by one of ordinary skill in the art based on the discussion provided herein. In some implementations, the one or more transceivers 620 may include more or fewer systems for communicating with other devices.

[0072] In some examples, the one or more transceivers 620 may include one or more circuits (including a WLAN transceiver) for enabling connection(s) and communication over a WLAN network, such as, but not limited to, a network based on the standards set forth in IEEE 802.11.

[0073] Additionally or alternatively, the one or more transceivers 620 may include one or more circuits (including a Bluetooth™ transceiver) to enable connection(s) and communication based on, for example, the Bluetooth™ protocol, the Bluetooth™ Low Energy protocol, or the Bluetooth™ Low Energy Long Range protocol. For example, the transceiver 620 may include a Bluetooth™ transceiver.

[0074] Additionally, the one or more transceivers 620 may include one or more circuits (including a cellular transceiver) for connecting to and communicating in a cellular network. The cellular network may include, but is not limited to, 3G / 4G / 5G networks such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), etc. For example, the one or more transceivers 220 may be configured to operate in accordance with a 3GPP release such as Rel-17, or other current or future 3GPP standards.

[0075] According to some aspects of the present disclosure, the processor 610, alone or in combination with computer instructions stored in memory 650 and / or one or more transceivers 620, implements the methods and mechanisms discussed in this disclosure. For example, the processor 610, alone or in combination with computer instructions stored in memory 650 and / or one or more transceivers 620, implements a mechanism for invalidating or modifying the FDRA field as described herein. For example, the processor 610, alone or in combination with computer instructions stored in memory 650 and / or one or more transceivers 620, implements a mechanism for modifying the RIV determination / calculation to reduce the size of the FDRA field as described herein. For example, the processor 610, alone or in combination with computer instructions stored in memory 650 and / or one or more transceivers 620, implements a mechanism for beam-based multi-TTI PD(U)SCH scheduling and beam-based TDRA methods for recursive Type A / Type B.

[0076] FIG. 7 illustrates an example method 700 for a system (e.g., a base station) supporting mechanisms for downlink (DL) scheduling and uplink (UL) scheduling in communications above 52.6 GHz in accordance with certain aspects of the present disclosure. For convenience and without limitation, FIG. 7 may be described with reference to elements of FIGS. 1, 4, 5, and 6. Method 700 may represent operations of an electronic device (e.g., base station 101 of FIG. 1) implementing mechanisms for performing downlink (DL) scheduling and uplink (UL) scheduling in transmissions above 52.6 GHz. Method 700 may also be performed by system 600 of FIG. 6 and / or computer system 900 of FIG. 9. However, method 700 is not limited to the specific aspects illustrated in these figures, and other systems may be used to perform the method, as will be understood by those skilled in the art. It should be understood that not all operations may be required, and that operations may not be performed in the same order as illustrated in FIG. 7.

[0077] At 702, it is determined that communication between the base station and the UE is in a frequency range above 52.6 GHz. For example, the base station 101 is configured to determine that it is communicating with the UE 105 in a frequency range above 52.6 GHz.

[0078] At 704, in response to determining that communication between the base station and the UE is in a frequency range above 52.6 GHz, the frequency primary resource allocation (FDRA) is disabled, the resource block group (RBG) size is modified, and / or the resource indication value (RIV) determination / calculation is modified. In one exemplary aspect, as described above, the base station 101 can disable the FDRA field in the DCI. For example, the base station 101 can use the FDRA field in the DCI to set the FDRA bit width to 0 to indicate to the UE 105 that it does not expect to receive an FDRA and assume that the UE 105 is allocated the entire bandwidth.

[0079] Additionally or alternatively, the base station 101 may modify the value of the RBG size. For example, the base station 101 may modify the RBG size to have a value greater than 16 to reduce the FDRA granularity. For example, the base station 101 may modify the maximum RBG size to have a value greater than 16. Additionally or alternatively, the base station 101 may modify the physical resource block (PRB) bundling size.

[0080] Additionally or alternatively, base station 101 can modify its resource indication value (RIV) determination / calculation to use the minimum number of allocated RBs. As discussed above (e.g., with respect to Figures 4 and 5) and below with respect to Figures 8A-8C, the maximum RIV value can be reduced and the size of the FDRA field can be reduced.

[0081] Downlink control information (DCI) is generated at 706. For example, the base station 101 generates the DCI based at least on one or more of the overridden FDRA, the modified RBG size, and the modified RIV determination.

[0082] At 708, the DCI is transmitted to the UE. For example, the base station 101 transmits the DCI to the UE 105. The base station 101 and the UE 105 can use information related to the DCI to communicate with each other.

[0083] 8A-8C illustrate example methods 800, 820, and 840, respectively, for a system (e.g., a base station) supporting a mechanism for modifying resource indication value (RIV) determination for communications above 52.6 GHz, in accordance with certain aspects of the present disclosure. For convenience and without limitation, FIGS. 8A-8C may be described with reference to elements of FIGS. 1, 4, 5, 6, and 7. Methods 800, 820, and 840 may represent operation of an electronic device (e.g., base station 101 of FIG. 1) implementing a mechanism for modifying RIV determination in transmissions above 52.6 GHz. Methods 800, 820, and 840 may also be performed by system 600 of FIG. 6 and / or computer system 900 of FIG. 9. However, methods 800, 820, and 840 are not limited to the specific aspects illustrated in these figures, and other systems may be used to perform the methods, as will be appreciated by those skilled in the art. It should be understood that not all acts may be required, and that acts may not be performed in the same order as shown in Figures 8A-8C.

[0084] The method 800 of FIG. 8A may be performed as part of steps 704, 706, and 708 of FIG. 7 to modify the RIV determination. At 802, the RIV is determined (e.g., calculated) or estimated based on one or more parameters. For example, the base station 101 may determine the RIV using, for example, equations (1) and (2) above. The parameters used to determine the RIV may include, but are not limited to, one or more of the number of allocated resource blocks, the allocated starting resource block, and the number of RBs in the bandwidth portion (BWP).

[0085] At 804, after determining or estimating the RIV, one or more RIVs are deleted. For example, the base station 101 can be configured to delete any RIV that is less than or equal to an RIV threshold. For example, the RIV threshold can include a maximum RIV associated with a minimum LRB (LRBmin).

[0086] At 806, after deleting one or more RIVs, the remaining RIVs in the table are used to signal an RIV to the UE. For example, the base station can signal an RIV in the DCI based on the remaining RIVs in the table.

[0087] Method 820 of Figure 8B may be performed as part of steps 704, 706, and 708 of Figure 7 to modify the RIV determination. In method 820, base station 101 may be configured to determine or estimate an RIV table for a smaller number of allocated resource blocks.

[0088] At 822, a minimum LRB is determined or assumed. For example, the base station 101 is configured to determine or assume the minimum LRB. At 824, the minimum LRB value is subtracted from the LRB value to generate a corrected LRB value. For example, the base station 101 can subtract the minimum LRB value from the LRB value before determining or estimating the RIV.

[0089] At 826, the RIV is determined (e.g., calculated) or estimated using the modified LRB value. For example, the base station 101 can determine or estimate the RIV using the modified LRB value. At 828, the RIV is signaled to the UE using the determined RIV. For example, the base station can signal the RIV in a DCI based on the determined RIV.

[0090] Method 840 of FIG. 8C may be performed as part of steps 704, 706, and 708 of FIG. 7 to modify the RIV determination. At 842, the RIV is determined (e.g., calculated) or estimated based on one or more parameters. For example, base station 101 may determine the RIV using, for example, equations (1) and (2) above. The parameters used to determine the RIV may include, but are not limited to, one or more of the number of allocated resource blocks, the allocated starting resource block, and the number of RBs in the bandwidth portion (BWP).

[0091] At 844, after determining or estimating the RIV, one or more RIVs are selected for signaling other information (information other than the RIV) to the UE. For example, the base station 101 may be configured to select any RIV that is less than or equal to an RIV threshold. For example, the RIV threshold may include a maximum RIV associated with a minimum LRB (LRBmin). The base station 101 may be configured to use the selected RIV (e.g., an unused RIV value) for signaling other information to the UE 105. In this example, instead of deleting one or more RIVs as described in step 804 of FIG. 8A, an RIV is selected to be used for signaling other information to the UE 105.

[0092] At 846, after selecting one or more RIVs, the remaining RIVs in the table are used to signal the RIV to the UE. For example, the base station can signal the RIV in the DCI based on the remaining RIVs in the table.

[0093] In addition to or in lieu of the FDRA granularity reduction described above, some aspects of the present disclosure are directed to TDRA systems and methods for beam-based multi-TTI PD(U)SCH scheduling and beam-based repetitive Type A / Type B.

[0094] According to some aspects, for example, in Rel-16, the TDRA table configuration may allow for a single PUSCH or multiple consecutive PUSCHs to be indicated in any of multiple scheduled slots. In some examples, the maximum number of PUSCHs in a row may be eight, and the TDRA may indicate K0 / K2, SLIV, and / or mapping type. Some aspects of the present disclosure are directed to beam-based multiple transmission time interval (multi-TTI) PDSCH / PUSCH scheduling. For example, the base station 101 of FIG. 1 may be configured to generate beam-based multi-TTI PDSCH / PUSCH scheduling and communicate the scheduling to the UE 105. The beam-based multi-TTI PDSCH / PUSCH scheduling may be used for communication between the base station 101 and the UE 105.

[0095] In some aspects, the beam-based multi-TTI PDSCH / PUSCH scheduling of the present disclosure can enable both uplink (UL) multi-TTI scheduling and downlink (DL) multi-TTI scheduling. Additionally or alternatively, the beam-based multi-TTI PDSCH / PUSCH scheduling can enable non-contiguous transmission of the PDSCH / PUSCH. For example, the beam-based multi-TTI PDSCH / PUSCH scheduling can be used to signal multiple K0 / K2 values. In some examples, the beam-based multi-TTI PDSCH / PUSCH scheduling can be used to signal multiple SLIVs. In some examples, one SLIV can be used for each transmission.

[0096] According to some aspects, TDRA signaling may be used for multi-TTI scheduling. For example, the TDRA signaling for multi-TTI scheduling may be a pre-configured entry. Alternatively, the TDRA signaling for multi-TTI scheduling may be composed of multiple separate TDRA entries. In some examples, the type of multi-TTI scheduling may be semi-statically pre-configured or dynamically selected.

[0097] According to some aspects, when beam-based operation is implemented in the frequency range above 52.6 GHz, multi-TTI PDSCH / PUSCH scheduling may be enabled to signal alternative beams for transmission, for example, by indicating a different transmission configuration indication (TCI) state for each transmission. In some examples, the TCI state may be used to establish a quasi-co-located (QCL) connection between a target reference signal (RS) and a source RS.

[0098] According to some examples, the base station 101 can use implicit signaling to signal multi-TTI PDSCH / PUSCH scheduling to the UE 105. For example, the base station 101 can use rotation through beams in a particular order to implicitly signal multi-TTI PDSCH / PUSCH scheduling to the UE 105.

[0099] According to some examples, the base station 101 can use explicit signaling to signal multi-TTI PDSCH / PUSCH scheduling to the UE 105. For example, the base station 101 can use a TDRA table to explicitly signal multi-TTI PDSCH / PUSCH scheduling to the UE 105. In this example, the TDRA table can, in turn, include the TCI status.

[0100] According to some examples, the base station 101 can use separate explicit signaling to signal the multi-TTI PDSCH / PUSCH scheduling to the UE 105. For example, the base station 101 can use bitmap(s) to explicitly signal the multi-TTI PDSCH / PUSCH scheduling to the UE 105. In this example, the bitmap can indicate which of the active TCI states should be used.

[0101] According to some examples, the base station 101 can use another explicit signaling to signal the multi-TTI PDSCH / PUSCH scheduling to the UE 105. For example, the base station 101 can list beams to explicitly signal the multi-TTI PDSCH / PUSCH scheduling to the UE 105.

[0102] According to an aspect, when there is a beam change, the UE 105 is not expected to start transmitting on the next beam within the duration of the beam switching gap.

[0103] Some aspects of the present disclosure are also directed to beam-based repetition Type A and / or Type B. In some examples, repetition may be allowed without explicit DCI. For example, in repetition Type A, slot repetition may be implemented by repeating a transmission in the next slot at the same symbol. For repetition Type B, minislot repetition may be implemented by repeating multiple repetitions based on a set of rules. Some aspects of the present disclosure are directed to adding beam diversity to repetition Type A and / or Type B.

[0104] According to some examples, the base station 101 may use implicit signaling to signal the beam-based repetition Type A and / or Type B to the UE 105. For example, the base station 101 may use rotation through the beams in a particular order to implicitly signal the beam-based repetition Type A and / or Type B to the UE 105.

[0105] According to some examples, the base station 101 may use explicit signaling to signal the beam-based repetition type A and / or type B to the UE 105. For example, the base station 101 may use a TDRA table to explicitly signal the beam-based repetition type A and / or type B to the UE 105. In this example, the TDRA table may include the TCI status in order.

[0106] According to some examples, the base station 101 can use separate explicit signaling to signal the beam-based repetition type A and / or type B to the UE 105. For example, the base station 101 can use bitmap(s) to explicitly signal the beam-based repetition type A and / or type B to the UE 105. In this example, the bitmap can indicate which of the active TCI states should be used.

[0107] According to some examples, the base station 101 can use separate explicit signaling to signal the beam-based repetition type A and / or type B to the UE 105. For example, the base station 101 can list beams to explicitly signal the beam-based repetition type A and / or type B to the UE 105.

[0108] In some instances of repetition type B, when the SCS is high and the base station 101 performs symbol-based beam switching, the beam switching gap is adapted.

[0109] Various aspects may be implemented using one or more computer systems, such as, for example, computer system 900 shown in FIG. 9 . Computer system 900 may be any known computer capable of performing the functions described herein, such as devices 101, 105 of FIG. 1 or device 600 of FIG. 6 . Computer system 900 includes one or more processors (also referred to as central processing units, or CPUs), such as processor 904. Processor 904 is connected to a communications infrastructure 906 (e.g., a bus). Computer system 900 also includes user input / output device(s) 903, such as a monitor, keyboard, pointing device, etc., that communicate with communications infrastructure 906 via user input / output interface(s) 902. Computer system 900 also includes main or primary memory 908, such as random access memory (RAM). Main memory 908 may include one or more levels of cache. Main memory 908 stores control logic (e.g., computer software) and / or data.

[0110] Computer system 900 may also include one or more secondary storage devices or secondary memories 910. Secondary memories 910 may include, for example, a hard disk drive 912 and / or a removable storage device or drive 914. Removable storage drive 914 may be a floppy disk drive, a magnetic tape drive, a compact disk drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0111] The removable storage drive 914 may interact with a removable storage unit 918. The removable storage unit 918 includes a computer-usable or computer-readable storage device on which computer software (control logic) and / or data is stored. The removable storage unit 918 may be a floppy disk, magnetic tape, compact disk, DVD, optical storage disk, and / or any other computer data storage device. The removable storage drive 914 reads from and / or writes to the removable storage unit 918 in well-known fashion.

[0112] According to some aspects, secondary memory 910 may include other means, intermediaries, or other techniques for allowing computer programs and / or other instructions and / or data to be accessed by computer system 900. Examples of such means, intermediaries, or other techniques may include, for example, removable storage unit 922 and interface 920. Examples of removable storage unit 922 and interface 920 may include a program cartridge and cartridge interface (such as found in a video game device), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0113] Computer system 900 may further include a communications interface or network interface 924. Communications interface 924 enables computer system 900 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referred to by reference numeral 928). For example, communications interface 924 may enable computer system 900 to communicate with remote devices 928 over communications path 926, which may be wired and / or wireless and may include any combination of a LAN, a WAN, the Internet, etc. Control logic and / or data may be transmitted to and from computer system 900 via communications path 926.

[0114] The operations in the aforementioned aspects may be implemented in a wide variety of configurations and architectures. Thus, some or all of the operations in the aforementioned aspects may be performed in hardware, software, or both. In some aspects, a tangible, non-transitory apparatus or article of manufacture is also referred to herein as a computer program product or program storage device that includes a tangible, non-transitory computer-usable or readable medium having control logic (software) stored thereon. This may include, but is not limited to, computer system 900, main memory 908, secondary memory 910, removable storage units 918 and 922, and tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (e.g., computer system 900), causes such data processing devices to operate as described herein.

[0115] Based on the teachings contained herein, it will be apparent to one or more skilled in the relevant art(s) how to make and use aspects of the present disclosure using data processing devices, computer systems and / or computer architectures other than those shown in Figure 9. In particular, aspects may operate with software, hardware, and / or operating system implementations other than those described herein.

[0116] It is understood that it is the "Detailed Description" section, and not the "Summary" and "Abstract" sections, that are intended to be used to interpret the claims. The Summary and Abstract sections may describe one or more exemplary aspects of the disclosure, but not all of the exemplary aspects of the disclosure, as contemplated by the inventor(s), and therefore, the Summary and Abstract sections are not intended to limit the scope of the disclosure or the appended claims in any way.

[0117] While the present disclosure is described herein with reference to exemplary embodiments for exemplary fields and applications, it should be understood that the present disclosure is not limited to the exemplary embodiments. Other embodiments and variations of embodiments are possible and are within the scope and spirit of the present disclosure. For example, without limiting the generality of this paragraph, the embodiments are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. Moreover, embodiments (whether or not explicitly described herein) have significant utility for fields and applications beyond the examples described herein.

[0118] Aspects have been described herein with the help of functional building blocks that illustrate the implementation of certain functions and relationships thereof. Boundaries of these functional building blocks have been arbitrarily defined herein for convenience of description. Alternative boundaries may be defined so long as the specified functions and relationships (or their equivalents) are appropriately performed. In addition, alternative aspects may execute functional blocks, steps, operations, methods, etc. using an order different from that described herein.

[0119] References herein to "one embodiment," "an embodiment," "exemplary embodiment," or similar phrases indicate that the described embodiment(s) may include a particular feature, structure, or characteristic, but all embodiments may not necessarily include that particular feature, structure, or characteristic. Also, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it would be within the knowledge of one of ordinary skill in the art to incorporate such feature, structure, or characteristic into other embodiments, whether or not explicitly mentioned or described herein.

[0120] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

[0121] As noted above, aspects of the present technology may include collecting and using data available from various sources, for example, to improve or enhance functionality. This disclosure contemplates that, in some cases, this collected data may include personal information data that uniquely identifies or can be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, addresses, data or records regarding a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), birth date, or any other identifying or personal information. This disclosure recognizes that the use of such personal information data in the present technology may be for the user's benefit.

[0122] This disclosure contemplates that entities involved in the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will adhere to robust privacy policies and / or privacy practices. Specifically, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining the strict confidentiality of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use changes. Personal information from users should be collected for the entity's lawful and legitimate use and should not be shared or sold except for those lawful uses. Furthermore, such collection / sharing should only be carried out after the user's informed consent is obtained. Furthermore, such entities should consider taking all necessary measures to protect and secure access to such personal information data and to ensure that others with access to the personal information data adhere to their privacy policies and procedures. Furthermore, such entities may be able to undergo third-party assessments to demonstrate their adherence to widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific types of personal data collected and / or accessed and should comply with applicable laws, regulations, and standards, including jurisdiction-specific considerations. For example, in the United States, the collection of or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be addressed accordingly. Therefore, different privacy practices should be maintained in each country with respect to different types of personal data.

[0123] Notwithstanding the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use of or access to personal information data. That is, the present disclosure contemplates that hardware and / or software elements may be provided to prevent or block access to such personal information data. For example, the present technology may be configured to allow a user to select to "opt in" or "opt out" of participating in the collection of personal information data, e.g., during registration for a service or at any time thereafter. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notice regarding the access or use of personal information. For example, the user may be informed upon downloading an app that will access the user's personal information data, and then again immediately before the app accesses the user's personal information data.

[0124] Furthermore, it is the intent of this disclosure that personal information data should be managed and handled in a manner that minimizes the risk of unintentional or unauthorized access or use. Risk can be minimized by limiting data collection and deleting data when it is no longer needed. Additionally, and where applicable in certain health-related applications, data anonymization can be used to protect user privacy. De-identification can be facilitated, where appropriate, by removing certain identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data at a city level rather than an address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods.

[0125] Thus, while this disclosure may broadly cover the use of personal information data to implement one or more various disclosed embodiments, this disclosure also contemplates that various embodiments may be implemented without requiring access to such personal information data, i.e., various embodiments of the present technology are not rendered inoperable by the absence of all or a portion of such personal information data.

Claims

1. A base station, a transceiver configured to wirelessly communicate with a user equipment (UE); a processor communicatively coupled to the transceiver, determining that the communication between the base station and the UE is within a frequency range that includes one or more frequencies above 52.6 GHz; In response to the determining, disabling a frequency domain resource allocation (FDRA) by setting a bit width associated with the FDRA to zero; generating a downlink channel indicator (DCI) based on the disabled FDRA; transmitting the DCI to the UE using the transceiver; a processor configured to: A base station comprising:

2. A base station, a transceiver configured to wirelessly communicate with a user equipment (UE); a processor communicatively coupled to the transceiver, determining that the communication between the base station and the UE is within a frequency range that includes one or more frequencies above 52.6 GHz; modifying a resource indication value (RIV) determination in response to said determination; To modify the RIV determination, the processor: determining a plurality of RIVs; deleting one or more RIVs from the plurality of RIVs; configured to signal an RIV to the UE using a remaining RIV from the plurality of RIVs; generating a downlink channel indicator (DCI) based on the revised RIV determination; transmitting the DCI to the UE using the transceiver; a processor configured to: A base station comprising:

3. A base station, a transceiver configured to wirelessly communicate with a user equipment (UE); a processor communicatively coupled to the transceiver, determining that the communication between the base station and the UE is within a frequency range that includes one or more frequencies above 52.6 GHz; modifying a resource indication value (RIV) determination in response to said determination; To modify the RIV determination, the processor: determining a minimum allocated resource block (LRB) value; subtracting the minimum LRB value from one or more LRB values ​​to generate one or more modified LRB values; determining one or more RIVs using the one or more corrected LRB values; configured to signal an RIV to the UE using the determined one or more RIVs; generating a downlink channel indicator (DCI) based on the revised RIV determination; transmitting the DCI to the UE using the transceiver; a processor configured to: A base station comprising:

4. A base station, a transceiver configured to wirelessly communicate with a user equipment (UE); a processor communicatively coupled to the transceiver, determining that the communication between the base station and the UE is within a frequency range that includes one or more frequencies above 52.6 GHz; modifying a resource indication value (RIV) determination in response to said determination; To modify the RIV determination, the processor: determining a plurality of RIVs; selecting one or more RIVs from the plurality of RIVs for signaling information other than RIVs to the UE; configured to signal the RIV to the UE using a remaining RIV from the plurality of RIVs; generating a downlink channel indicator (DCI) based on the revised RIV determination; transmitting the DCI to the UE using the transceiver; a processor configured to: A base station comprising:

5. In response to determining, by the base station, that communication between the base station and a user equipment (UE) is within a frequency range above 52.6 GHz, disabling a Frequency Domain Resource Allocation (FDRA) by setting a bit width associated with the FDRA to 0; generating, by the base station, a downlink channel indicator (DCI) based on the disabled FDRA; transmitting, by the base station, the DCI to the UE; A method comprising:

6. modifying a resource indication value (RIV) determination, by a base station, in response to determining that communication between the base station and a user equipment (UE) is within a frequency range above 52.6 GHz; modifying the RIV determination determining a plurality of RIVs; deleting one or more RIVs from the plurality of RIVs; signaling an RIV to the UE using a remaining RIV from the plurality of RIVs; generating, by the base station, a downlink channel indicator (DCI) based on the modified RIV determination; transmitting, by the base station, the DCI to the UE; A method comprising:

7. modifying a resource indication value (RIV) determination, by a base station, in response to determining that communication between the base station and a user equipment (UE) is within a frequency range above 52.6 GHz; modifying the RIV determination determining a minimum allocated resource block (LRB) value; subtracting the minimum LRB value from one or more LRB values ​​to generate one or more modified LRB values; determining one or more RIVs using the one or more corrected LRB values; and signaling an RIV to the UE using the determined one or more RIVs; generating, by the base station, a downlink channel indicator (DCI) based on the modified RIV determination; transmitting, by the base station, the DCI to the UE; A method comprising:

8. modifying a resource indication value (RIV) determination, by a base station, in response to determining that communication between the base station and a user equipment (UE) is within a frequency range above 52.6 GHz; modifying the RIV determination determining a plurality of RIVs; selecting one or more RIVs from the plurality of RIVs for signaling information other than RIVs to the UE; signaling the RIV to the UE using a remaining RIV from the plurality of RIVs; generating, by the base station, a downlink channel indicator (DCI) based on the modified RIV determination; transmitting, by the base station, the DCI to the UE; A method comprising:

9. A user equipment (UE), a transceiver configured to wirelessly communicate with a base station; a processor communicatively coupled to the transceiver, receiving, using the transceiver, a downlink channel indicator (DCI) from the base station in a frequency range above 52.6 GHz; the DCI is generated based on an FDRA field including a bit width set to 0; using the transceiver to communicate with the base station using information related to the DCI; a processor configured to: A user equipment (UE) comprising:

10. A user equipment (UE), a transceiver configured to wirelessly communicate with a base station; a processor communicatively coupled to the transceiver, receiving, using the transceiver, a downlink channel indicator (DCI) from the base station in a frequency range above 52.6 GHz; the DCI is generated based on a modified resource indication value (RIV) determination, the DCI including an RIV determined from a plurality of RIVs from which one or more RIVs have been removed; using the transceiver to communicate with the base station using information related to the DCI; a processor configured to: A UE comprising:

11. A user equipment (UE), a transceiver configured to wirelessly communicate with a base station; a processor communicatively coupled to the transceiver, receiving, using the transceiver, a downlink channel indicator (DCI) from the base station in a frequency range above 52.6 GHz; The DCI is generated based on a modified resource indication value (RIV) determination, the DCI including an RIV determined from a plurality of RIVs, the plurality of RIVs being determined based on modified allocated resource block (LRB) values, and modifying the RIV determination includes: determining a minimum allocated resource block (LRB) value; subtracting the minimum LRB value from one or more LRB values ​​to generate one or more modified LRB values; determining one or more RIVs using the one or more corrected LRB values; using the transceiver to communicate with the base station using information related to the DCI; a processor configured to: A UE comprising:

12. A user equipment (UE), a transceiver configured to wirelessly communicate with a base station; a processor communicatively coupled to the transceiver, receiving, using the transceiver, a downlink channel indicator (DCI) from the base station in a frequency range above 52.6 GHz, the DCI being generated based on a modified resource indication value (RIV) determination, the DCI including an RIV determined from a plurality of RIVs, one or more RIVs of the plurality of RIVs being selected to signal information other than an RIV to the UE, and an RIV being signaled to the UE using the remaining RIVs of the plurality of RIVs; using the transceiver to communicate with the base station using information related to the DCI; a processor configured to: A UE comprising:

Images