# US 11,115,968 B2 · System and method for efficient frequency resource assignment in a communication system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,115,968 B2 - Document ID: US11115968B2 - Status: Granted - Kind: B2 - Application number: 16/534,371 - Filed: 2019-08-07 - Published: 2020-02-20 - Granted: 2021-09-07 - Earliest claimed: 2018-08-16 - Assignees: QUALCOMM Incorporated - Applicants: Qualcomm Incorporated - Inventors: Piyush Gupta; Junyi Li; Vinay Joseph; Mostafa Khoshnevisan - Web page: https://patentgrep.com/patent/US11115968B2 ## CPC - H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal - H04L 5/0053: {Allocation of signalling, i.e. of overhead other than pilot signals} - H04L 5/0094: {Indication of how sub-channels of the path are allocated} - H04W 28/06: Optimizing {the usage of the radio link}, e.g. header compression, information sizing {, discarding information (system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365)} - H04W 76/27: Transitions between radio resource control [RRC] states - H04L 5/0005: {Time-frequency} - H04W 72/232: the control data signalling from the physical layer, e.g. DCI signalling - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method for communication includes receiving a transport block size (TBS) configuration containing at least a portion of a frequency-domain resource allocation, and receiving a downlink control information (DCI) message having an additional portion of the frequency-domain resource allocation, the TBS configuration and the additional portion of the frequency-domain resource allocation having frequency-domain resource allocation information to support data communication. ## Claims ### Claim 1 A method for communication, comprising: receiving a transport block size (TBS) configuration containing at least a portion of a frequency-domain resource allocation; and receiving a downlink control information (DCI) message having an additional portion of the frequency-domain resource allocation, the TBS configuration and the additional portion of the frequency-domain resource allocation having frequency-domain resource allocation information to support data communication, wherein a frequency-domain resource assignment field in the DCI message comprises bits identifying a beginning resource block (RB) location in a communication stream. ### Claim 2 (depends on 1) The method of claim 1, wherein the transport block size (TBS) configuration is communicated using one or more of a radio resource connection (RRC) configuration message, a non-access stratum (NAS) message, a message from the radio access network (RAN) and/or a message from a core network. ### Claim 3 (depends on 1) The method of claim 1, wherein a communication device infers complete frequency-domain resource allocation information from the transport block size (TBS) configuration and the additional portion of the frequency-domain resource allocation to support data communication. ### Claim 4 (depends on 1) The method of claim 1, wherein the DCI message may comprise one or more of a physical downlink shared channel (PDSCH) resource allocation, a physical uplink shared channel (PUSCH) resource allocation, and a combined PDSCH and PUSCH resource allocation. ### Claim 5 (depends on 1) The method of claim 1, wherein when the transport block size (TBS) configuration and the DCI message having an additional portion of a frequency-domain resource allocation are insufficient for communication, receiving a fall back DCI message containing complete frequency resource information. ### Claim 6 (depends on 1) The method of claim 1, wherein the transport block size (TBS) configuration comprises a configuration selected from the group consisting of a fixed-packet size transport block size (TBS) configuration, a TBS+k configuration, a (1+delta)*TBS configuration, and a maximum (max) TBS value. ### Claim 7 (depends on 1) The method of claim 1, further comprising after identifying the beginning resource block location, inferring a total number of resource blocks to support data communication. ### Claim 8 (depends on 1) The method of claim 1, further comprising communicating on resources that include the frequency-domain resource allocation. ### Claim 9 A system for communication, comprising: a communication device configured to receive a transport block size (TBS) configuration containing at least a portion of a frequency-domain resource allocation; and the communication device configured to receive a downlink control information (DCI) message having an additional portion of the frequency-domain resource allocation, the TBS configuration and the additional portion of the frequency-domain resource allocation having frequency-domain resource allocation information to support data communication, wherein a frequency-domain resource assignment field in the DCI message comprises bits identifying a beginning resource block (RB) location in a communication stream. ### Claim 10 (depends on 9) The system of claim 9, wherein the transport block size (TBS) configuration is communicated using one or more of a radio resource connection (RRC) configuration message, a non-access stratum (NAS) message, a message from the radio access network (RAN) and/or a message from a core network. ### Claim 11 (depends on 9) The system of claim 9, wherein the communication device infers complete frequency-domain resource information from the transport block size (TBS) configuration and the additional portion of the frequency-domain resource allocation to support data communication. ### Claim 12 (depends on 9) The system of claim 9, wherein the DCI message may comprise one or more of a physical downlink shared channel (PDSCH) resource allocation, a physical uplink shared channel (PUSCH) resource allocation, and a combined PDSCH and PUSCH resource allocation. ### Claim 13 (depends on 9) The system of claim 9, wherein when the transport block size (TBS) configuration and the DCI message having an additional portion of a frequency-domain resource allocation are insufficient for communication, receiving a fall back DCI message containing complete frequency resource information. ### Claim 14 (depends on 9) The system of claim 9, wherein the transport block size (TBS) configuration comprises a configuration selected from the group consisting of a fixed-packet size transport block size (TBS) configuration, a TBS+k configuration, a (1+delta)*TBS configuration, and a maximum (max) TBS value. ### Claim 15 (depends on 9) The system of claim 9, further comprising after identifying the beginning resource block location, inferring a total number of resource blocks to support data communication. ### Claim 16 (depends on 9) The system of claim 9, further comprising the communication device configured to communicate on resources that include the frequency-domain resource allocation. ### Claim 17 A method for communication, comprising: receiving a transport block size (TBS) configuration containing at least a portion of a frequency-domain resource allocation; receiving a downlink control information (DCI) message having an additional portion of the frequency-domain resource allocation, the TBS configuration and the additional portion of the frequency-domain resource allocation having frequency-domain resource allocation information to support data communication wherein a frequency-domain resource assignment field in the DCI message comprises bits identifying a beginning resource block (RB) location in a communication stream; and after identifying the beginning resource block (RB) location, inferring a total number of resource blocks to support data communication. ### Claim 18 (depends on 17) The method of claim 17, wherein the transport block size (TBS) configuration is communicated using one or more of a radio resource connection (RRC) configuration message, a non-access stratum (NAS) message, a message from the radio access network (RAN) and/or a message from a core network. ### Claim 19 (depends on 17) The method of claim 17, wherein the DCI message may comprise one or more of a physical downlink shared channel (PDSCH) resource allocation, a physical uplink shared channel (PUSCH) resource allocation, and a combined PDSCH and PUSCH resource allocation. ### Claim 20 (depends on 17) The method of claim 17, wherein when the transport block size (TBS) configuration and the DCI message having an additional portion of a frequency-domain resource allocation are insufficient for communication, receiving a fall back DCI message containing complete frequency resource information. ### Claim 21 (depends on 17) The method of claim 17, wherein the transport block size (TBS) configuration comprises a configuration selected from the group consisting of a fixed-packet size transport block size (TBS) configuration, a TBS+k configuration, a (1+delta)*TBS configuration, and a maximum (max) TBS value. ### Claim 22 (depends on 17) The method of claim 17, further comprising communicating on resources that include the frequency-domain resource allocation. ### Claim 23 A non-transitory computer-readable medium storing computer executable code for communication, the code executable by a processor to: receive a transport block size (TBS) configuration containing at least a portion of a frequency-domain resource allocation; receive a downlink control information (DCI) message having an additional portion of the frequency-domain resource allocation, the TBS configuration and the additional portion of the frequency-domain resource allocation having frequency-domain resource allocation information to support data communication, and use a frequency-domain resource assignment field in the DCI message comprising bits to identify a beginning resource block (RB) location in a communication stream. ### Claim 24 (depends on 23) The non-transitory computer-readable medium of claim 23, the code executable by a processor to: receive the transport block size (TBS) configuration using one or more of a radio resource connection (RRC) configuration message, a non-access stratum (NAS) message, a message from the radio access network (RAN) and/or a message from a core network. ### Claim 25 (depends on 23) The non-transitory computer-readable medium of claim 23, wherein the code is executable by a processor to: infer complete frequency-domain resource information from the transport block size (TBS) configuration and the additional portion of the frequency-domain resource allocation to support data communication. ### Claim 26 (depends on 23) The non-transitory computer-readable medium of claim 23, wherein the code is executable by a processor to: receive the DCI message in one or more of a physical downlink shared channel (PDSCH) resource allocation, a physical uplink shared channel (PUSCH) resource allocation, and a combined PDSCH and PUSCH resource allocation. ### Claim 27 (depends on 23) The non-transitory computer-readable medium of claim 23, wherein the code is executable by a processor to: when the transport block size (TBS) configuration and the DCI message having an additional portion of a frequency-domain resource allocation are insufficient for communication, receiving a fall back DCI message containing complete frequency resource information. ### Claim 28 (depends on 23) The non-transitory computer-readable medium of claim 23, wherein the code is executable by a processor to: configure the transport block size (TBS) configuration to comprise a configuration selected from the group consisting of a fixed-packet size transport block size (TBS) configuration, a TBS+k configuration, a (1+delta)*TBS configuration, and a maximum (max) TBS value. ### Claim 29 (depends on 23) The non-transitory computer-readable medium of claim 23, wherein the code is executable by a processor to: after identifying the beginning resource block location, infer a total number of resource blocks to support data communication. ### Claim 30 (depends on 23) The non-transitory computer-readable medium of claim 23, wherein the code is executable by a processor to communicate on resources that include the frequency-domain resource allocation.