Base station, user equipment and method for downlink (DL) and uplink (UL) scheduling of transmissions above 52.6 GHz

Abstract

Some aspects of the present disclosure relate to an apparatus and method for implementing downlink 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) via a wireless network and a processor communicatively coupled to the transceiver. The processor determines that the communication between the base station and the UE is within a frequency range above 52.6 GHz. In response to the determination, the processor disables a frequency master resource assignment (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 on at least one or more of a disabled FDRA, a modified RBG size, or a modified RIV determination. The processor uses the transceiver to transmit the DCI to the UE.

Description

Background Art Technical Field

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

[0004] A user equipment (UE) communicating with a base station (e.g., an evolved Node B (eNB), a next generation Node B (gNB), etc.) through a communication link may transmit control and measurement information to the base station using an uplink control channel, and may transmit data to the base station using an uplink data channel. The base station may transmit control information indicating how to use resources on an uplink channel to the UE using a downlink control channel. Summary of the invention

[0005] Some aspects of the present disclosure relate to apparatus and methods for enabling downlink (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).

[0006] 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) via a wireless network and a processor communicatively coupled to the transceiver. The processor determines that the 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 disables a frequency master resource assignment (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 on at least one or more of the disabled FDRA, the modified RBG size, or the modified RIV determination. The processor uses the transceiver to transmit the DCI to the UE.

[0007] In some examples, to disable FDRA, the processor is configured to set a bit width associated with FDRA to zero. 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.

[0008] In some examples, to modify the RIV determination, the processor is configured to:

[0009] A plurality of RIVs are determined, one or more RIVs are eliminated from the plurality of RIVs, and the RIVs are signaled to the UE using remaining RIVs from the plurality of RIVs.

[0010] 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 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 RIV to the UE using the determined one or more RIVs.

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

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

[0013] 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 base station, the instructions cause the processor to perform operations, the operations including disabling frequency master resource assignment (FDRA), modifying resource block group (RBG) size, or modifying resource indication value (RIV) determination in response to determining that the communication between the base station and the user equipment (UE) is within a frequency range including one or more frequencies above 52.6 GHz. The operations also include generating a downlink channel indicator (DCI) by the base station based on at least one or more of the disabled FDRA, the modified RBG size, or the modified RIV determination, and transmitting the DCI by the base station to the UE.

[0014] 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 uses the transceiver to receive a downlink channel indicator (DCI) in a frequency range above 52.6 GHz from the base station. The DCI is generated based on at least one of a disabled frequency primary resource assignment (FDRA), a 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 associated with the DCI.

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

[0016] 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 disabled frequency primary resource assignment (FDRA), a modified resource block group (RBG) size, or a modified resource indication value (RIV) determination. The method also includes communicating with the base station using information associated with the DCI.

[0017] Some aspects of the present disclosure relate to a non-transitory computer-readable medium storing instructions. When these instructions are executed by a processor of a user equipment (UE), these instructions cause the processor to perform operations including the following items: 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 disabled frequency primary resource assignment (FDRA), a modified resource block group (RBG) size, or a modified resource indication value (RIV) determination. The operation also includes communicating with the base station using information associated with the DCI.

[0018] The present invention is provided for the purpose of illustrating some aspects only, so as to provide an understanding of the subject matter described herein. Therefore, the above-mentioned features are only examples and should not be understood as narrowing the scope or essence of the subject matter in the present disclosure. Other features, aspects and advantages of the present disclosure will become apparent from the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the present disclosure and, together with the description, further serve to explain the principles of the present disclosure and enable those skilled in the relevant art to make and use the present disclosure.

[0020] Figure 1 An example system implementing a design for downlink (DL) and uplink (UL) scheduling in transmissions above 52.6 GHz is shown in accordance with some aspects of the present disclosure.

[0021] Figure 2A An exemplary shared transport block (TB) and time and frequency resource allocations according to some aspects of the present disclosure are shown.

[0022] Figure 2B An example shared transport block (TB) and time and frequency resource allocation for multi-transmission time interval (multi-TTI) PUSCH transmission according to some aspects of the present disclosure is shown.

[0023] Figure 3 An example enhanced TDRA table for TTIPUSCH scheduling according to some aspects of the present disclosure is shown.

[0024] Figure 4 An exemplary table of resource indication values ​​(RIVs) is shown in accordance with some aspects of the present disclosure.

[0025] Figure 5 Another exemplary table of resource indication values ​​(RIVs) according to some aspects of the present disclosure is shown.

[0026] Figure 6 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 some aspects of the present disclosure is shown.

[0027] Figure 7 An example method 700 of a system (eg, a base station) for supporting mechanisms for downlink (DL) and uplink (UL) scheduling in transmissions above 52.6 GHz is shown in accordance with some aspects of the present disclosure.

[0028] FIG. 8A to FIG. 8C Example methods 800 , 820 , and 840 , respectively, are shown for a system (eg, a base station) supporting a mechanism for modifying resource indication value (RIV) determination in transmissions above 52.6 GHz, according to aspects of the present disclosure.

[0029] Fig. 9An exemplary computer system for implementing some aspects or portions thereof.

[0030] The present disclosure is described with reference to the accompanying drawings. In the drawings, generally, the same reference numerals indicate the same or functionally similar elements. Also, generally, the leftmost digit of a reference numeral identifies the drawing in which the reference numeral first appears. DETAILED DESCRIPTION

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

[0032] Figure 1 An exemplary system 100 is shown that implements a design for implementing downlink (DL) and uplink (UL) scheduling for communications above 52.6 GHz according to some aspects of the present disclosure. The exemplary system 100 is provided for illustrative purposes only and is not intended to limit the disclosed aspects. The system 100 may include, but is not limited to, a network node (e.g., a base station such as an eNB, a gNB, etc.) 101 and an electronic device (e.g., a UE) 105. The electronic device 105 (hereinafter referred to as UE 105) may include an electronic device configured to operate based on a variety of wireless communication technologies. These technologies may include, but are not limited to, technologies based on the third generation partnership project (3GPP) standard. For example, the UE 105 may include an electronic device configured to operate using a 3GPP version (such as Release 17 (Rel-17)) or other current / future 3GPP standards. The UE 105 may include, but is not limited to, a wireless communication device, a smart phone, a laptop, a desktop, a tablet, a personal assistant, a monitor, a television, a wearable device, an Internet of Things (IoT), a vehicle communication device, etc. The network node 101 (referred to herein as a base station) may include a node configured to operate based on a variety of wireless communication technologies (such as, but not limited to, technologies based on 3GPP standards). For example, the base station 101 may include a node configured to operate using a 3GPP version (such as Rel-17) or other current / future 3GPP standards. The UE 105 may be connected to the base station 101 and may communicate with the base station using one or more communication links 107.

[0033] Some aspects of the present disclosure relate to one or more new parameter sets (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 relate to addressing the impact on physical signals / channels in a frequency range above 52.6 GHz. For example, some aspects of the present disclosure discuss timeline-related aspects applicable to each parameter set in the new parameter sets, such as bandwidth part (BWP) and beam switching time, hybrid automatic repeat request (hybrid ARQ or HARQ) scheduling, UE processing, preparation and calculation time of 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 beams (SSB) beams for licensed and unlicensed operation in a frequency range above 52.6 GHz. Additionally or alternatively, some aspects of the present disclosure may use a channel access mechanism that assumes beam-based operation in order to comply with regulatory requirements applicable to unlicensed spectrum at frequencies between 52.6 GHz and 71 GHz.

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

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

[0036] 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 based on time slots and can include demodulation reference signal (DMRS) symbols in symbol 2 (or 3). In mapping type B, resource allocation can be based on mini-slots and include front-end loaded DMRS. In some examples, time domain resource allocation can indicate a time 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 the starting symbol (S) and length (L) within the time slot. In an example in Rel-15, the time domain resource allocation does not cross time slot boundaries. In some examples, the time domain resource allocation can also be encoded in a single number called a start and length indicator value (SLIV).

[0037] According to some aspects, the FDRA field may also be sent in the DCI (DL and UL) and may define resource block allocations. For example, the base station 101 may transmit the FDRA field to the UE 105 using the DCI. In some examples, the FDRA field may be sent 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) may be configured as T0, T1, or dynamically switched (e.g., the MSB (most significant bit) indicates the type).

[0038] In some examples, a BWP indicator (which can be used for BWP switching) that identifies a specific BWP for resource allocation may be used. According to some aspects, the 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, the RBG may be a set of contiguous virtual resource blocks (VRBs). In addition, the RBG size may 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 of configuration 1 or configuration 2.

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

[0040] Additionally or alternatively, DL and UL scheduling may be considered with slot aggregation. In some examples, without slot aggregation, time domain resource allocation is not allowed to cross slot boundaries. In these examples, delays to align slot boundaries may be increased. In some examples, with slot aggregation, the reuse in the next slot uses the same time domain resource allocation as the transmission in the first slot.

[0041] Ultra-Reliable Low Latency Communication (URLLC) is a collection of features that provide low latency and ultra-high reliability. According to some aspects, Figure 1 The system 100 may be configured to provide PUSCH repetition information for Rel-16. In some examples, the UE 105 may be configured to transmit multiple repetitions across consecutive time slots. The base station 101 may be configured to schedule the PUSCH repetition information and transmit it to the UE 105. In some examples of DL and UL scheduling of Rel-15, the number of repetitions of the PUSCH with time slot aggregation may be configured semi-statically. In Rel-16, for PUSCH repetition type A, a mechanism similar to that of PUSCH repetition type B may be used to support dynamic indication of the number of repetitions. In some examples, an additional column for the number of repetitions may be added to the TDRA table. Similar to repetition type B, the number of repetitions may be dynamically indicated as part of the TDRA entry.

[0042] For dynamic grants (DG) and configured grants (CG), if the number of repetitions exists in the corresponding TDRA table, the number of repetitions can be provided by numberOfRepetitions-r16. In some examples, numberOfRepetitions-r16 is {1,2,3,4,7,8,12,16} (3 bits), the same as repetition type B. Otherwise, the number of repetitions can be determined according to the Rel-15 process (pusch-AggregationFactor for DG and repK for CG).

[0043] According to some aspects, a system 100 using ULLRC PUSCH repetition type B may support PUSCH repetition in one slot or across multiple consecutive slots. In some examples, the system 100 may support both dynamic grants (DG) and configured grants (CG) (type 1 and type 2). According to some examples, the base station 101 may 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 (e.g., using DCI) may set the TDRA and transmit it to the UE 105. The base station 101 may define the TDRA using S (start 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 may indicate one of the entries in the TDRA table that provides the values ​​of S, L, and K.

[0044] According to some examples, a PUSCH transmission from UE 105 may occur within a time window of L*K symbols starting from the indicated start 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 switching point, the "nominal" repetition may be split into multiple PUSCH repetitions, with one PUSCH repetition in each UL cycle in the slot.

[0045] In some examples of UL LRC PUSCH repetition type B, DMRS sharing across multiple repetitions does not occur, only PUSCH mapping type B is supported, and TBS is determined based on L.

[0046] According to some examples, multiple TTPUSCH transmissions in Rel-15 include repeated transmissions in time to support URLLC or ensure UL coverage. Figure 2A An exemplary shared transport block (TB) and time and frequency resource allocation according to some aspects of the present disclosure is shown. Figure 2A As shown, a transport block (TB) 201 may be scheduled for multiple time slots 203a-203d. In some examples, multiple TTPUSCH transmissions in Rel-16 NR-U may be targeted to schedule multiple time slots and / or mini-time slots 213a-213d with different transport blocks (TBs) 211a-211d using a single UL grant, such as Figure 2B as shown in . Figure 2B An example shared transport block (TB) and time and frequency resource allocation for multiple TTI PUSCH transmissions according to some aspects of the present disclosure are shown. Figure 2B It may lead to higher efficiency and increased UL transmission probability.

[0047] According to some aspects, common fields of the DCI format for multi-TIPUSCH for Rel-16 NR-U are provided in Table 1.

[0048] Table 1 - Common fields of the DCI format for multiple TTPUSCH in Rel-16 NR-U

[0049]

[0050]

[0051] The HARQ process number in Table 1 signaled in the DCI applies to the first scheduled PUSCH. The HARQ process number is then incremented by 1 for subsequent PUSCHs in the scheduled order (with modulo operations as needed). The time domain RA of Table 1 supports at least contiguous time domain resource assignments for PUSCHs of type A and type B.

[0052] Certain aspects of the present disclosure relate to systems and methods for minimizing DCI overhead (eg, time domain resource allocation, frequency domain resource allocation, etc.).

[0053] In some examples, multi-T PUSCH scheduling in Rel-16 NR-U can support multi-T PUSCH scheduling using DCI format 0_1. In these examples, the TDRA table configuration allows a single or multiple consecutive PUSCHs to be indicated in any time slot of multiple scheduled time slots. In some examples, the maximum number of PUSCHs in a row can be 8, however, 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 ​​can be determined based on the configured TDRA table. For example, in the case of scheduling multiple PUSCHs, 1 RV bit is used for each PUSCH, and a value of {0,2}. Alternatively, in the case of scheduling only a single PUSCH, 2 RV bits are used for PUSCH.

[0054] According to some aspects, the conventional TDRA table is extended so that each row indicates multiple PUSCHs (contiguous in the time domain). Figure 3 An exemplary enhanced TDRA table 300 for multi-T IPUSCH scheduling is shown in FIG. Figure 3 Column 301 shows the TDRA index. Figure 3 Column 303 shows the K2 value. Figure 3 Column 305 shows SLIV. And Figure 3 Column 307 of shows the mapping type. In some examples and as Figure 3 As shown, each PUSCH may have a separate SLIV and mapping type. The number of scheduled PUSCHs may be signaled by the number of valid SLIVs indicated in the row of the TDRA table signaled in the DCI. Figure 3Also shown in FIG. 3 is an exemplary PUSCH allocation 309 associated with each TRDA index.

[0055] According to some aspects, system 100 is configured to operate in a frequency range higher than 52.6 GHz. In some examples, the range higher than 52.6 GHz may include a frequency range between about 52.6 GHz and about 71 GHz. In some examples, in a frequency range higher than 52.6 GHz, base station 101 and UE 105 may communicate using narrow beams due to wavelengths at a frequency range higher than 52.6 GHz. In these examples, there is a high probability that only 1 or 2 UEs can match a single beam. In these examples, the scheduler may only have to send scheduling information to a single (or several) UEs, especially in the downlink. Therefore, base station 101 does not need to send scheduling information to many UEs. Therefore, the granularity of frequency domain resource allocation (FDRA) can be reduced to reduce the overhead in DCI.

[0056] According to some aspects, the scheduler is configured to perform a scheduling process. The scheduling process may include a process for allocating resources for frequency data, and may be performed by the network, and the UE may follow the schedule transmitted by the network. In some examples, the scheduler may be part of the base station 101. Additionally or alternatively, the scheduler may be separated from the base station 101, but is part of the network associated with the base station 101 and is 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 UE105 and / or the network), buffer status reports (BSRs), quality of service (QoS) requirements, associated radio bearers, scheduling requests (SRs), etc. Using one or more of the information, the scheduler may determine resource allocations and may transmit resource allocations to the UE 105.

[0057] According to some aspects, in order to combat phase noise in the frequency range above 52.6 GHz, the subcarrier spacing (SCS) can be increased. The increase in SCS can result in a decrease in the duration of a symbol. The decrease in the duration of a symbol (e.g., a time slot) can result in an increase in the number of DCIs that need to be decoded within a specific time interval and the associated scheduling. In some examples, Figure 1 The system 100 can be configured to increase the minimum time domain scheduling unit to be greater than one symbol, support multiple PDSCHs scheduled by one DCI, and / or support one TB mapped to multiple time slots (e.g., TTI bundling). Additionally or alternatively, aspects of the present disclosure provide methods and systems for TDRA to support these schemes. In addition, aspects of the present disclosure provide TDRA methods and systems to consider the use of multiple beams for a specific UE for multi-TTI transmissions.

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

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

[0060] DCI may have different formats. For example, DCI format 0_0, format 0_1, format 0_2 (e.g., URLLC-based DCI format of Rel-16) and / or format 0_x may be used to schedule PUSCH in a cell. For example, DCI format 1_0, format 1_1, format 1_2 (e.g., URLLC-based DCI format of Rel-16) and / or format 0_x may be used to schedule PDSCH in a cell. DCI may also include other formats, such as format 2_0, format 2_1, format 2_2, or format 2_3. DCI may include an FDRA field for frequency domain resource assignment. As discussed above, base station 101 may disable the FDRA field in DCI. For example, base station 101 may use the FDRA field in DCI to set the FDRA bit width to 0. Therefore, base station 101 may indicate to UE 105 that FDRA is not expected to be received, and assume that UE 105 is allocated the entire bandwidth. In some examples, setting the FDRA bit width to 0 is different from disabling TDRA and using only RRC signaling. Disabling the FDRA field (eg, setting the FDRA bit width to 0) may be UE-specific and may be different for UL and DL.

[0061] According to some aspects, the base station 101 can be configured to reduce the FDRA granularity by modifying the resource block group (RBG) size. As discussed above with respect to DL / UL resource allocation type 0, the RBG definition is specific to the BWP size. Since the 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 of 1 to 36, the RBG size is 2 for configuration 1 and 4 for configuration 4. For BWPs of 37 to 72, the RBG size is 4 for configuration 1 and 8 for configuration 4. For BWPs of 73 to 144, the RBG size is 8 for configuration 1 and 16 for configuration 4. And for BWPs of 145 to 275, the RBG size is 16 for both configuration 1 and configuration 4. Some aspects of the present disclosure are configured to modify the value of the RBG size. For example, the RBG size can be modified to have a value greater than 16 to reduce the FDRA granularity. Additionally or alternatively, a physical resource block (PRB) bundling size may be modified.

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

[0063] 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 starting allocated resource block, and the number of RBs within a bandwidth part (BWP). The UE 105 may use the RIV to determine the starting allocated resource block and the number of allocated resource blocks. After determining or estimating the RIV, the base station 101 may be configured to eliminate any RIV that is less than or equal to a RIV threshold. For example, the RIV threshold may include a maximum RIV associated with a minimum LRB (LRBmin). After eliminating 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 method for reducing the maximum RIV and reducing the size of the FDRA field. In some examples, the RIV of the DCI may be determined as follows:

[0064] if

[0065] otherwise

[0066] Here, L RB is the number of allocated resource blocks, RBstart is the starting allocated resource block, and is the number of RBs within the bandwidth part (BWP).

[0067] A non-limiting example of modifying the RIV determination (eg, modifying the RIV calculation) to use a minimum number of allocated RBs is Figure 4 Shown in. Figure 4 An exemplary table 400 of RIVs according to some aspects of the present disclosure is shown. In this example, it is assumed that the BWP has RBsize=14 and LRBmin is 5. In this example, the maximum RIV associated with an LRBmin of 5 is 52. In this example, the base station 101 eliminates RIVs with RIV thresholds less than or equal to 52. In other words, the base station 101 transmits RIVs between 53 and 104, thereby reducing 1 bit used to transmit the RIV in this example, and thus reducing the size of the FDRA field. Therefore, the base station 101 eliminates the RIVs associated with LRBs 1, 2, 3, 4, 13, and 14 ( Figure 4 In this example, base station 101 eliminates the RIVs associated with LRBs that are less than LRBmin and also eliminates the RIVs associated with LRBs 13 and 14 (which are LRBs that are greater than LRBmin).

[0068] According to some aspects, in addition to or as an alternative to eliminating any RIV that is less than the maximum RIV associated with LRBmin, the base station 101 may be configured to determine or estimate a 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 the 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 LRBmin). For example, LRActual = LRBeff*LRBmin, where LRBeff is the number of allocated resource blocks. In this example, RIVs of any LRB size are not eliminated.

[0069] A non-limiting example of modifying the RIV determination (e.g., modifying the RIV calculation) by subtracting the minimum LRB value is shown in Figure 5 Shown in. Figure 5An exemplary table 500 of RIVs according to some aspects of the present disclosure is shown. In this example, it is assumed that the BWP has RBsize=14 and LRBmin is 5. The RIV is calculated as discussed 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, no higher level LRB values ​​are eliminated.

[0070] According to some aspects, in addition to or as an alternative to modifying the RIV table as discussed above, the base station 101 can be configured to use the unutilized RIV values ​​to signal other information to the UE 105. Thus, by using the unutilized RIV values ​​to signal other information to the UE 105, the base station 101 can reduce the size of the FDRA field. For example, instead of eliminating Figure 4 Columns 401 and 403 (which correspond to LRBs 1, 2, 3, 4, 13, and 14), Figure 4 The RIVs in columns 401 and 403 of may be used to signal other information to the UE 105 .

[0071] Figure 6 A block diagram of an exemplary system 600 of an electronic device that implements a mechanism for downlink (DL) and uplink (UL) scheduling for communications above 52.6 GHz according to some aspects of the present disclosure is shown. System 600 can be any electronic device of system 100 (e.g., base station 101, UE 105). System 600 includes a processor 610, one or more transceivers 620, a communication infrastructure 640, a memory 650, an operating system 652, an application 654, and one or more antennas 660. The system shown is provided as an exemplary portion of system 600, and system 600 may include other circuits and subsystems. Moreover, although the system of system 600 is shown as a separate component, aspects of the present disclosure may include any combination of these components, fewer components, or more components.

[0072] The memory 650 may include random access memory (RAM) and / or cache, and may include control logic components (e.g., computer software) and / or data. The memory 650 may include other storage devices or memories, such as, but not limited to, a hard 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 data transmission 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 supports one or more network protocol stacks (e.g., an Internet protocol stack and a cellular protocol stack, etc.) that may include several logical layers. At the corresponding layer of the protocol stack, the operating system 652 includes control mechanisms and data structures to perform functions associated with the layer.

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

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

[0075] According to some aspects, one or more transmitters 620 may be coupled to antenna 660. Antenna 660 may include one or more antennas that may be the same or different types. One or more transceivers 620 allow system 600 to communicate with other devices that may be wired and / or wireless. In some examples, one or more transceivers 620 may include circuits / devices such as processors, controllers, radio components, sockets, plugs, buffers, etc. for connecting to a network and communicating on the network. According to some examples, one or more transceivers 620 include one or more circuits for connecting to and communicating on a wired and / or wireless network.

[0076] 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.TM Subsystems, each including its own radio transceiver and protocol, as will be understood by those skilled in the art based on the discussion provided herein. In some implementations, one or more transceivers 620 may include more or fewer systems for communicating with other devices.

[0077] In some examples, transceiver(s) 620 may include one or more circuits, including a WLAN transceiver, to enable connection and communication via a WLAN network, such as, but not limited to, a network based on the standards described in IEEE 802.11.

[0078] Additionally, or alternatively, the one or more transceivers 620 may include a device for implementing a communication protocol based on, for example, Bluetooth. TM Protocol, Bluetooth TM Low Energy Protocol or Bluetooth TM One or more circuits for connection and communication with low energy long range protocols (including Bluetooth TM For example, the transceiver 620 may include a Bluetooth TM Transceiver.

[0079] Additionally, the one or more transceivers 620 may include one or more circuits (including cellular transceivers) for connecting to and communicating on a cellular network. Cellular networks may include, but are 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 according to a 3GPP release (such as Rel-17) or other current / future 3GPP standards.

[0080] According to some aspects of the present disclosure, the processor 610 alone or in combination with computer instructions stored in the memory 650 and / or one or more transceivers 620 implements the methods and mechanisms discussed in the present disclosure. For example, the processor 610 alone or in combination with computer instructions stored in the memory 650 and / or one or more transceivers 620 implements the mechanisms for disabling or modifying the FDRA field as discussed herein. For example, the processor 610 alone or in combination with computer instructions stored in the memory 650 and / or one or more transceivers 620 implements the mechanisms for modifying RIV determination / calculation to reduce the size of the FDRA field as discussed herein. For example, the processor 610 alone or in combination with computer instructions stored in the memory 650 and / or one or more transceivers 620 implements the mechanisms for beam-based multi-TTIPD(U)SCH scheduling and beam-based repetition type-A / type-B TDRA methods.

[0081] Figure 7 An exemplary method 700 of a system (e.g., a base station) for supporting mechanisms for downlink (DL) and uplink (UL) scheduling for communications above 52.6 GHz according to some aspects of the present disclosure is shown. For convenience and not limitation, Figure 1 , Figure 4 , Figure 5 and Figure 6 Description of the elements Figure 7 Method 700 may be indicative of an electronic device (eg, a device that implements a mechanism for implementing downlink (DL) and uplink (UL) scheduling in transmissions above 52.6 GHz) Figure 1 Method 700 may also be performed by Figure 6 System 600 and / or Fig. 9 The method 700 is performed by a computer system 900. However, the method 700 is not limited to the specific aspects depicted in those 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 these operations may not be performed in the same manner as described above. Figure 7 The same sequence as shown is performed.

[0082] At 702, it is determined that the 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.

[0083] At 704, and in response to determining that the communication between the base station and the UE is in a frequency range above 52.6 GHz, frequency master resource assignment (FDRA) is disabled, resource block group (RBG) size is modified, and / or resource indication value (RIV) determination / calculation is modified. In an exemplary aspect, as discussed 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 reception of the FDRA is not expected and that the UE 105 is assumed to be allocated the entire bandwidth.

[0084] 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.

[0085] Additionally or alternatively, the base station 101 may modify the resource indication value (RIV) determination / calculation to use the minimum number of allocated RBs. Figure 4 and Figure 5 ) and the following about FIG. 8A to FIG. 8C As discussed, the maximum RIV value may be reduced and the size of the FDRA field may be reduced.

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

[0087] The DCI is transmitted to the UE at 708. For example, the base station 101 transmits the DCI to the UE 105. The base station 101 and the UE 105 may communicate with each other using information associated with the DCI.

[0088] FIG. 8A to FIG. 8C Example methods 800, 820, and 840 of a system (e.g., a base station) supporting a mechanism for modifying resource indication value (RIV) determination for communications above 52.6 GHz according to some aspects of the present disclosure are shown, respectively. For convenience and not limitation, reference may be made to Figure 1 , Figure 4 , Figure 5 , Figure 6 and Figure 7 Description of the elements FIG. 8A to FIG. 8C Methods 800, 820, and 840 may represent an electronic device (eg, Figure 1 Methods 800, 820 and 840 may also be performed by Figure 6 System 600 and / or Fig. 9 The computer system 900 is executed. However, the methods 800, 820 and 840 are not limited to the specific aspects depicted in those 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 these operations may not be performed in order. FIG. 8A to FIG. 8C The same order as shown is followed.

[0089] Fig. 8A The method 800 may be used as a method for modifying RIV determination Figure 7 At 802, the RIV is determined (e.g., calculated) or estimated based on one or more parameters. For example, the base station 101 can determine the RIV using, for example, equations (1) and (2) discussed above. The parameters used to determine the RIV can include, but are not limited to, one or more of the number of allocated resource blocks, the starting allocated resource block, and the number of RBs within a bandwidth part (BWP).

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

[0091] At 806, and after eliminating one or more RIVs, the RIVs remaining in the table are used to signal the RIVs to the UE. For example, the base station may signal the RIVs in the DCI based on the RIVs remaining in the table.

[0092] Figure 8B The method 820 may be used as a method for modifying RIV determination Figure 7 In method 820, base station 101 may be configured to determine or estimate a RIV table for a smaller number of allocated resource blocks.

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

[0094] 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.

[0095] Figure 8C The method 840 may be used as a method for modifying RIV determination Figure 7 At 842, the RIV is determined (e.g., calculated) or estimated based on one or more parameters. For example, the base station 101 can determine the RIV using, for example, equations (1) and (2) discussed above. The parameters used to determine the RIV can include, but are not limited to, one or more of the number of allocated resource blocks, the starting allocated resource block, and the number of RBs within the bandwidth part (BWP).

[0096] At 844, and after determining or estimating the RIV, one or more RIVs are selected for use in 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 a 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 unutilized RIV value) to signal the other information to the UE 105. In this example, instead of Fig. 8A One or more RIVs are eliminated as discussed in step 804 of , and a RIV is selected for use in signaling other information to the UE 105.

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

[0098] In addition to or as an alternative to the FDRA granularity reduction discussed above, some aspects of the present disclosure relate to beam-based multi-TTIPD(U)SCH scheduling and beam-based repetition Type-A / Type-B TDRA systems and methods.

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

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

[0101] 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 consist of multiple separate TDRA entries. In some examples, the type of multi-TTI scheduling may be semi-statically pre-configured or dynamically selected.

[0102] According to some aspects, given that beam-based operations are occurring in a frequency range above 52.6 GHz, multi-TTI PDSCH / PUSCH scheduling may be allowed to signal alternative beams for transmission by, for example, indicating different transmission configuration indication (TCI) states for each transmission. In some examples, the TCI state may be used to establish a quasi co-site (QCL) connection between a target reference signal (RS) and a source RS.

[0103] According to some examples, base station 101 can use implicit signaling to signal multiple TTI PDSCH / PUSCH scheduling to UE 105. For example, base station 101 can use rotating through beams in a specific order to implicitly signal multiple TTI PDSCH / PUSCH scheduling to UE 105.

[0104] According to some examples, base station 101 may use explicit signaling to signal multiple TTI PDSCH / PUSCH scheduling to UE 105. For example, base station 101 may use a TDRA table to explicitly signal multiple TTI PDSCH / PUSCH scheduling to UE 105. In this example, the TDRA table may include TCI states in order.

[0105] According to some examples, base station 101 may use another explicit signaling to signal multiple TTI PDSCH / PUSCH scheduling to UE 105. For example, base station 101 may use a bitmap to explicitly signal multiple TTI PDSCH / PUSCH scheduling to UE 105. In this example, the bitmap may indicate which of the active TCI states should be used.

[0106] According to some examples, base station 101 may use another explicit signaling to signal multiple TTI PDSCH / PUSCH scheduling to UE 105. For example, base station 101 may list beams to explicitly signal multiple TTI PDSCH / PUSCH scheduling to UE 105.

[0107] According to various aspects, in the presence of a beam change, the UE 105 is not expected to start transmission of the next beam within the duration of the beam switching gap.

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

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

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

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

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

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

[0114] For example, one or more computer systems (such as Fig. 9 The computer system 900 shown in the figure can be used to implement various aspects. The computer system 900 can be any well-known computer capable of performing the functions described herein, such as Figure 1 Device 101, 105 or Figure 6The computer system 900 includes one or more processors (also referred to as central processing units or CPUs), such as a processor 904. The processor 904 is connected to a communication infrastructure 906 (e.g., a bus). The computer system 900 also includes a user input / output device 903, such as a monitor, a keyboard, a pointing device, etc., which communicates with the communication infrastructure 906 through a user input / output interface 902. The computer system 900 also includes a main memory or primary storage 908, such as a random access memory (RAM). The main memory 908 may include one or more levels of cache. The main memory 908 has control logic components (e.g., computer software) and / or data stored therein.

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

[0116] The removable storage drive 914 may interact with a removable storage unit 918. The removable storage unit 918 includes a computer usable or readable storage device having computer software (control logic) and / or data stored thereon. The removable storage unit 918 may be a floppy disk, a magnetic tape, an optical disk, a DVD, an 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 a well-known manner.

[0117] According to some aspects, secondary memory 910 may include other devices, means, or other methods for allowing computer programs and / or other instructions and / or data to be accessed by computer system 900. Such devices, means, or other methods may include, for example, a removable storage unit 922 and an interface 920. Examples of removable storage unit 922 and interface 920 may include a program cartridge and cartridge interface (such as those found in video game devices), 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.

[0118] The computer system 900 may also include a communication or network interface 924. The communication interface 924 enables the computer system 900 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referenced by reference numeral 928). For example, the communication interface 924 may allow the computer system 900 to communicate with a remote device 928 via a communication path 926, which may be wired and / or wireless and may include any combination of a LAN, a WAN, the Internet, etc. Control logic components and / or data may be transmitted to and from the computer system 900 via the communication path 926.

[0119] The operations in the foregoing aspects can be implemented in various configurations and architectures. Thus, some or all of the operations in the foregoing aspects may be performed in hardware, software, or in both hardware and software. In some aspects, a tangible, non-transient device or article includes a tangible, non-transient computer-usable or readable medium on which a control logic component (software) is stored, also referred to herein as a computer program product or program storage device. This includes, but is not limited to, a computer system 900, a main memory 908, an auxiliary memory 910, and removable storage units 918 and 922, as well as tangible articles embodying any combination of the foregoing. When executed by one or more data processing devices (such as a computer system 900), such control logic components cause such data processing devices to operate as described herein.

[0120] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art how to use Fig. 9 The various aspects of the present disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown. In particular, the various aspects may operate with software, hardware, and / or operating system implementations other than those described herein.

[0121] It should be understood that the Detailed Description section, rather than the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more but not all exemplary aspects of the present disclosure as contemplated by the inventors, and thus are not intended to limit the present disclosure or the appended claims in any way.

[0122] Although the present disclosure has been described herein with reference to exemplary aspects of exemplary fields and applications, it should be understood that the present disclosure is not limited thereto. Other aspects and modifications are possible and are within the scope and essence of the present disclosure. For example, and without limiting the generality of this paragraph, the various aspects are not limited to the software, hardware, firmware and / or entities shown in the figures and / or described herein. In addition, the various aspects (whether or not explicitly described herein) have significant practicality for fields and applications outside the examples described herein.

[0123] Various aspects have been described herein by means of functional building blocks that illustrate specific implementations of specific functions and relationships thereof. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. As long as the specified functions and relationships (or their equivalents) are properly performed, alternative boundaries may be defined. In addition, alternative aspects may perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.

[0124] References herein to "one aspect," "aspect," "one example," "example," or similar phrases indicate that the described aspects may include a particular feature, structure, or characteristic, but each aspect may not necessarily include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same aspect. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with one aspect, it is within the knowledge of a person skilled in the relevant art to incorporate such feature, structure, or characteristic into other aspects, whether or not explicitly mentioned or described herein.

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

[0126] As described above, various aspects of the present technology may include collecting and using data available from various sources, thereby (for example) improving or enhancing functionality. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying information or personal information. The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users.

[0127] The present disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for the legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should only be done after receiving the user's informed consent. In addition, such entities should consider taking any necessary steps to defend and secure access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards that include specific considerations of jurisdiction. For example, in the United States, the collection or access of 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 handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[0128] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware elements and / or software elements to prevent or block access to such personal information data. For example, the present technology may be configured to allow users to selectively participate in "opt-in" or "opt-out" of collecting personal information data at any time during (for example) registration for a service or thereafter. In addition to providing "opt-in" and "opt-out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then be reminded again just before the personal information data is accessed by the application.

[0129] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[0130] Thus, while the present disclosure may broadly cover the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or part of such personal information data.

Claims

1. A base station, comprising: a transceiver configured to wirelessly communicate with user equipment UE; and a processor communicatively coupled to the transceiver and configured to: determining that the 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, disabling a frequency domain resource assignment FDRA by setting a bit width associated with the FDRA to zero or modifying a resource indication value RIV determination based on a minimum allocated resource block LRB value; generating a downlink channel indicator DCI based at least on one or more of the disabled FDRA or the modified RIV determination; as well as The DCI is transmitted to the UE using the transceiver.

2. The base station of claim 1 , wherein to modify the RIV determination, the processor is configured to: Based on the minimum LRB value, determining a maximum RIV; based on the maximum RIV, eliminating one or more RIVs from the plurality of RIVs; and A RIV is signaled to the UE using a remaining RIV from the plurality of RIVs.

3. The base station of claim 1 , wherein to modify the RIV determination, the processor is configured to: Identify multiple RIVs; Eliminating one or more RIVs from the plurality of RIVs based on the minimum LRB value; and A RIV is signaled to the UE using a remaining RIV from the plurality of RIVs.

4. The base station of claim 1 , wherein to modify the RIV determination, the processor is configured to: Determining the minimum 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 modified LRB values; as well as The determined one or more RIVs are used to signal a RIV to the UE.

5. The base station of claim 1 , wherein to modify the RIV determination, the processor is configured to: determining one or more RIVs using one or more modified LRB values ​​generated based on the minimum LRB value; and The determined one or more RIVs are used to signal a RIV to the UE.

6. A method implemented by a base station, comprising: In response to determining by the base station that the communication between the base station and the user equipment UE is in a frequency range above 52.6 GHz, disabling a frequency domain resource assignment FDRA by setting a bit width associated with the FDRA to zero or modifying a resource indication value RIV determination based on a minimum allocated resource block LRB value; generating, by the base station, a downlink channel indicator (DCI) based at least on one or more of a disabled FDRA or a modified RIV determination; as well as The base station transmits the DCI to the UE.

7. The method of claim 6, wherein modifying the RIV determination comprises: Based on the minimum LRB value, determining a maximum RIV; based on the maximum RIV, eliminating one or more RIVs from the plurality of RIVs; as well as A RIV is signaled to the UE using a remaining RIV from the plurality of RIVs.

8. The method of claim 6, wherein modifying the RIV determination comprises: Identify multiple RIVs; based on the minimum LRB value, eliminating one or more RIVs from the plurality of RIVs; as well as A RIV is signaled to the UE using a remaining RIV from the plurality of RIVs.

9. The method of claim 6, wherein modifying the RIV determination comprises: Determining the minimum 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 modified LRB values; as well as The determined one or more RIVs are used to signal a RIV to the UE.

10. The method of claim 6, wherein modifying the RIV determination comprises: determining one or more RIVs using one or more modified LRB values ​​generated based on the minimum LRB value; as well as The determined one or more RIVs are used to signal a RIV to the UE.

11. A user equipment UE, comprising: a transceiver configured to wirelessly communicate with a base station; and a processor communicatively coupled to the transceiver and configured to: receiving, using the transceiver, a downlink channel indicator DCI in a frequency range above 52.6 GHz from the base station, wherein the DCI is generated based on at least one of a disabled frequency domain resource assignment FDRA comprising a bit width set to zero or a modified resource indication value RIV determination based on a minimum allocated resource block LRB value; and Using the transceiver, communicating with the base station using information associated with the DCI. 12 . The UE of claim 11 , wherein the DCI comprises a RIV determined from a plurality of RIVs from which one or more RIVs are eliminated based on the minimum LRB value.

13. The UE of claim 11, wherein the DCI includes a RIV determined from a plurality of RIVs, and wherein the plurality of RIVs are determined based on a modified LRB value, the modified LRB value being determined based on the minimum LRB value.

14. The UE of claim 11, wherein the DCI comprises a RIV determined from a plurality of RIVs, one or more RIVs from among the plurality of RIVs being used to signal information other than the RIV to the UE.

Images