Patent Grant
12010052
This document is directed generally to wireless communications.
In current communication system, a transport block size (TBS) is determined by a set of resource parameters allocated by a base station, i.e. gNB. For transmissions of downlink/uplink (DL/UL) shared channel, different combinations of rate and TBS may have different base graphs of low-density parity check (LDPC) in physical downlink shared channel (PDSCH) and/or physical uplink shared channel (PUSCH). If the TBS determined by a user equipment (UE) is different from that understood by the gNB, the data transmissions between the UE and the gNB may fail. Hence, to ensure the reliability of data transmissions between the UE and the gNB, the TBS determined based on the same resource parameters should be the same and unique between the UE and network (e.g. the gNB) side.
This document relates to methods, systems, and devices for determining a transport block size, in particular to methods, systems, and devices for determining a transport block size based on a parameter or a signaling.
The present disclosure relates to a wireless communication method for use in a wireless terminal. The wireless communication method comprises:
Various embodiments may preferably implement the following features: Preferably, the parameter or the signaling is a UE capability parameter or a UE feature or a high-layer signaling, or a UE category n, wherein n is an integer and not smaller than 1.
Preferably, the wireless terminal supports a release version determined by a high-layer parameter.
Preferably, the parameter or the signaling is available for the wireless terminal.
Preferably, the wireless communication method further comprises determining the intermediate value based on a method determined by the parameter or the signaling.
Preferably, the wireless terminal does not support a release version determined by a high-layer parameter.
Preferably, the parameter or the signaling is not available for the wireless terminal.
Preferably, the wireless communication method further comprises determining the intermediate value based on a predefined method.
Preferably, the event is whether the intermediate value is modified by a predefined function; and the predefined function is one of rounding down, rounding up, rounding or retaining at a float precision.
Preferably, the event is whether the plurality of resource parameters with specific values is valid.
Preferably, the event is whether modifying a product of the plurality of resource parameters into a range by a predefined function is valid, and the predefined function is one of rounding down, rounding up, rounding or retaining at a float precision.
Preferably, the function of retaining at a float precision represents reserving at least a decimal place or one place after the decimal point.
Preferably, the (NRE*R*Qm*v)=3824.2536 and the function of retaining at a float precision reserves 3824.2536 as a number in the range between 3824.0001 and 3824.2536, for example, determine 3824.2536 as 3824.1, or determine 3824.2536 as 3824.2, or determine 3824.2536 as 3824.25, or determine 3824.2536 as 3824.5, or determine 3824.2536 as 3824.125.
Preferably, the predefined function is one of rounding down, rounding up, or rounding and the range is an integer.
Preferably, the integer is 3824.
Preferably, the predefined function is retaining at the float precision and the range is between two float numbers.
Preferably, the two float numbers are between 3824 and 3825.
Preferably, the event is whether the TBS corresponding to each intermediate value of an intermediate value set is valid.
Preferably, the TBS corresponding to each intermediate value of the intermediate value set comprises at least one of 3824, 3840 or 3848.
Preferably, the TBS corresponding to each intermediate value of the intermediate value set is determined based on a predefined function of modifying the intermediate value.
Preferably, the predefined function is rounding down and the TBS corresponding to each intermediate value of the intermediate value set comprises 3840 and 3848.
Preferably, the predefined function is rounding up and the TBS corresponding to each intermediate value of the intermediate value set comprises 3824.
Preferably, the wireless communication method further comprises determining a base graph of data processing based on the TBS, wherein a threshold which is related to the TBS and used for determining the base graph is adjusted by a modified factor at at least one event.
Preferably, the modified factor is smaller than or equal to 24 and is greater than or equal to −24.
Preferably, the at least one event comprises at least one of the intermediate value being a number between two adjacent integers; the intermediate value is a number that is equal to one of the two adjacent integers; or the TBS is among the TBSs in a quantized set, wherein the TBSs in the quantized set is between 3824 and 3848, and are evenly divisible by 8.
Preferably, the two adjacent integers are 3824 and 3825.
Preferably, the wireless communication method further comprises transmitting, to the wireless network node, the parameter or the signaling associated with the intermediate value of determining the TBS.
Preferably, if the parameter or the signaling is not transmitted to the wireless network node, the UE shall determine the intermediate value based on the method associated with the event determined by the last recent parameter or the signaling.
Preferably, wherein the TBS is determined by determining the TBS by using a predefined calculation method of determining the intermediate value when determining that the parameter or the signaling does not exist or that the parameter or the signaling is not transmitted to the wireless network node.
Preferably, the predefined calculation method rounds the intermediate value down.
Preferably, the predefined calculation method rounds the product of intermediate value and 2N down, wherein N is an integer that not smaller than 5.
Preferably, wherein the predefined calculation method rounds the intermediate value up.
Preferably, the predefined calculation method rounds the intermediate value.
Preferably, wherein the predefined calculation method retains the intermediate value at a float precision.
Preferably, the plurality of resource parameters with specific values is valid in the predefined calculation method.
Preferably, modifying a product of the plurality of resource parameters with the specific values into a range by a predefined function is valid in the predefined calculation method, and the predefined function is one of rounding down, rounding up, rounding or retaining at a float precision.
Preferably, the predefined function is one of rounding down, rounding up, or rounding and the range is an integer.
Preferably, the integer is 3824.
Preferably, the predefined function is retaining at the float precision and the range is between two float numbers.
Preferably, the two float numbers are between 3824 and 3825.
Preferably, the TBS corresponding to each intermediate value of an intermediate value set is valid in the predefined calculation method.
Preferably, the TBS corresponding to each intermediate value of the intermediate value set comprises at least one of 3824, 3840 or 3848.
Preferably, the TBS corresponding to each intermediate value of the intermediate value set is determined based on a predefined function of modifying the intermediate value.
Preferably, the predefined function is rounding down and the TBS corresponding to each intermediate value of the intermediate value set comprises 3840 and 3848.
Preferably, the predefined function is rounding up and the TBS corresponding to each intermediate value of the intermediate value set comprises 3824.
Preferably, the wireless communication method further comprises performing data communications with a wireless communication node based on the TBS.
Preferably, the wireless communication method further comprises receiving, from a wireless network node, control information comprising the plurality of resource parameters; calculating the intermediate value based on the plurality of resource parameters; modifying the intermediate value based on the parameter or the signaling; and determining the TBS based on the modified intermediate value.
The present disclosure relates to wireless communication method for use in a wireless network node. The wireless communication method comprises:
Various embodiments may preferably implement the following features:
Preferably, the parameter or the signaling is a UE capability parameter or a UE feature or a high-layer signaling, or a UE category n, wherein n is an integer and not smaller than 1.
Preferably, the wireless communication method further comprises:
Preferably, the wireless communication method further comprises at least one of the following:
Preferably, the wireless communication method further comprises:
Preferably, the wireless communication method further comprises at least one of the following:
Preferably, the wireless communication method further comprises:
Preferably, the wireless communication method further comprises:
Preferably, the event is whether the intermediate value is modified by a predefined function; and the predefined function is one of rounding down, rounding up, rounding or retaining at a float precision.
Preferably, the event is whether the plurality of resource parameters with specific values is valid.
Preferably, the event is whether modifying a product of the plurality of resource parameters into a range by a predefined function is valid, and the predefined function is one of rounding down, rounding up, rounding or retaining at a float precision.
Preferably, the predefined function is one of rounding down, rounding up, or rounding and the range is an integer.
Preferably, the integer is 3824.
Preferably, the predefined function is retaining at the float precision and the range is between two float numbers.
Preferably, the two float numbers are between 3824 and 3825.
Preferably, the event is whether the TBS corresponding to each intermediate value of an intermediate value set is valid.
Preferably, the TBS corresponding to each intermediate value of the intermediate value set comprises at least one of 3824, 3840 or 3848.
Preferably, the TBS corresponding to each intermediate value of the intermediate value set is determined based on a predefined function of modifying the intermediate value.
Preferably, the predefined function is rounding down and the TBS corresponding to each intermediate value of the intermediate value set comprises 3840 and 3848.
Preferably, the predefined function is rounding up and the TBS corresponding to each intermediate value of the intermediate value set comprises 3824.
Preferably, the wireless communication further comprises determining a base graph of data processing based on the TBS, wherein a threshold which is related to the TBS and used for determining the base graph is adjusted by a modified factor at at least one event.
Preferably, the modified factor is smaller than or equal to 24 and is greater than or equal to −24.
Preferably, the at least one event comprises at least one of the intermediate value being a number between two adjacent integers; the intermediate value is a number that is equal to one of the two adjacent integers; or the TBS is among the TBSs in a quantized set, wherein the TBSs in the quantized set is between 3824 and 3848, and are evenly divisible by 8.
Preferably, the two adjacent integers are 3824 and 3825.
Preferably, the wireless communication method further comprises receiving, from the wireless terminal, the parameter or the signaling associated with the intermediate value of determining the TBS.
Preferably, if the parameter or the signaling is not transmitted from the wireless terminal, the intermediate value shall be determined by the method associated with the event determined by the last recent reported parameter or the signaling.
Preferably, the TBS is determined by determining the TBS by using a predefined calculation method of determining the intermediate value when determining that the wireless terminal does not have the parameter or the signaling or that the parameter or the signaling is not transmitted from the wireless terminal.
Preferably, the predefined calculation method rounds the product of intermediate value and 2N down,
Preferably, the predefined calculation method rounds the intermediate value down.
Preferably, the predefined calculation method rounds the intermediate value up.
Preferably, the predefined calculation method rounds the intermediate value.
Preferably, the predefined calculation method retains the intermediate value at a float precision.
Preferably, the plurality of resource parameters with specific values is valid in the predefined calculation method.
Preferably, modifying a product of the plurality of resource parameters with the specific values into a range by a predefined function is valid in the predefined calculation method, and the predefined function is one of rounding down, rounding up, rounding or retaining at a float precision.
Preferably, the predefined function is one of rounding down, rounding up, or rounding and the range is an integer.
Preferably, the integer is 3824.
Preferably, the predefined function is retaining at the float precision and the range is between two float numbers.
Preferably, the two float numbers are between 3824 and 3825.
Preferably, the TBS corresponding to each intermediate value of an intermediate value set is valid in the predefined calculation method.
Preferably, the TBS corresponding to each intermediate value of the intermediate value set comprises at least one of 3824, 3840 or 3848.
Preferably, the TBS corresponding to each intermediate value of the intermediate value set is determined based on a predefined function of modifying the intermediate value.
Preferably, the predefined function is rounding down and the TBS corresponding to each intermediate value of the intermediate value set comprises 3840 and 3848.
Preferably, the predefined function is rounding up and the TBS corresponding to each intermediate value of the intermediate value set comprises 3824.
Preferably, the wireless communication method further comprises performing data communications with the wireless terminal based on the TBS.
Preferably, the wireless communication method further comprises transmitting, to the wireless terminal, control information comprising the plurality of resource parameters; calculating the intermediate value based on the plurality of resource parameters; modifying the intermediate value based on the parameter or the signaling; and determining the TBS based on the modified intermediate value.
The present disclosure relates to a wireless communication method for use in a wireless terminal. The wireless communication method comprises determining a base graph of data processing based on a transport block size, TBS, wherein a threshold which is related to the TBS and used for determining the base graph is adjusted by a modified factor at at least one event.
Various embodiments may preferably implement the following features:
Preferably, the modified factor is smaller than or equal to 24 and is greater than or equal to −24.
Preferably, the at least one event comprises at least one of an intermediate value of determining the TBS being a number between two adjacent integers; the intermediate value is a number that is equal to one of the two adjacent integers; or the TBS is among the TBSs in a quantized set, wherein the TBSs in the quantized set is between 3824 and 3848, and are evenly divisible by 8.
Preferably, the two adjacent integers are 3824 and 3825.
Preferably, the wireless communication method further comprises performing data communications with a wireless communication node based on the TBS and the base graph.
The present disclosure relates to a wireless communication method for use in a wireless network node. The wireless communication method comprises determining a base graph of data processing based on a transport block size, TBS, wherein a threshold which is related to the TBS and used for determining the base graph is adjusted by a modified factor at at least one event.
Various embodiments may preferably implement the following features: Preferably, the modified factor is smaller than or equal to 24 and is greater than or equal to −24.
Preferably, the at least one event comprises at least one of an intermediate value of determining the TBS being a number between two adjacent integers; the intermediate value being a number that is equal to one of the two adjacent integers; or the TBS being among the TBSs in a quantized set, wherein the TBSs in the quantized set is between 3824 and 3848, and are evenly divisible by 8.
Preferably, the two adjacent integers are 3824 and 3825.
Preferably, the wireless communication method further comprises performing data communications with a wireless terminal based on the TBS and the base graph.
The present disclosure relates to a wireless terminal, comprising a processor. The processor is configured to:
Various embodiments may preferably implement the following features: Preferably, the parameter or the signaling is a UE capability parameter or a UE feature or a high-layer signaling, or a UE category n, wherein n is an integer and not smaller than 1.
Preferably, the processor is further configured to perform a wireless communication method of any of the foregoing described methods.
The present disclosure relates to a wireless network node, comprising a processor which is configured to:
Various embodiments may preferably implement the following features:
Preferably, the parameter or the signaling is a UE capability parameter or a UE feature or a high-layer signaling, or a UE category n, wherein n is an integer and not smaller than 1.
Preferably, the processor is further configured to perform a wireless communication method of any of the foregoing described methods.
The present disclosure relates to a wireless terminal, comprising a processor. The processor is configured to:
determine a base graph of data processing based on a transport block size, TBS, wherein a threshold which is related to the TBS and used for determining the base graph is adjusted by a modified factor at at least one event.
Various embodiments may preferably implement the following feature:
Preferably, the processor is further configured to perform a wireless communication method of any of the foregoing described methods.
The present disclosure relates to a wireless network node, comprising a processor which is configured to:
Various embodiments may preferably implement the following feature:
Preferably, the processor is further configured to perform a wireless communication method of any of the foregoing described methods.
The present disclosure relates to a computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a wireless communication method of any of the foregoing described methods.
The exemplary embodiments disclosed herein are directed to providing features that will become readily apparent by reference to the following description when taken in conjunction with the accompany drawings. In accordance with various embodiments, exemplary systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of the present disclosure.
Thus, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and/or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the specific order or hierarchy presented unless expressly stated otherwise.
The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.
In an embodiment, the storage unit 110 and the program code 112 may be omitted and the processor 100 may include a storage unit with stored program code.
The processor 100 may implement any one of the steps in exemplified embodiments on the wireless terminal 10.
The communication unit 120 may be a transceiver. The communication unit 120 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless network node (e.g. a base station).
In an embodiment, the storage unit 210 and the program code 212 may be omitted. The processor 200 may include a storage unit with stored program code.
The processor 200 may implement any steps described in exemplified embodiments on the wireless network node 20.
The communication unit 220 may be a transceiver. The communication unit 220 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless terminal (e.g. a user equipment).
In an embodiment, a procedure of determining a transport block size (TBS) for a UE/BS may include the following steps:
Step 1: Computing the number NNE of resource elements by obtaining time and frequency domain resource allocation configured by control information (e.g. L1 signaling and high-layer parameters). In an embodiment, the UE receives the control information from the BS.
In an embodiment, step 1 determines the total number NiE of resource elements within the slot allocated for physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) by:
NRE=min(156,NRE′)·nPRB.
Step 2: Computing an intermediate value Ninfo by calculating a product of the number NRE of resource elements, a value R related to rate, a modulation order Qm and the number v of layers, for determining the TBS; and performing step 3 when the intermediate value Ninfo is not greater than 3824, otherwise, performing step 4.
In an embodiment, the intermediate value Ninfo is obtained by:
Ninfo=NRE·R·Qm·v
Step 3: Quantizing the intermediate value Ninfo by the following formula:
where n=max(3, └log2 Ninfo┘−6),
Step 4: Quantizing the intermediate value Ninfo by the following formula:
where n=└log2 (Ninfo−24)┘−5.
In the above procedure of determining the TBS, the value R related to rate and the modulation order Qm used to determine the intermediate value Ninfo in step 2 is obtained by an index of modulation and coding scheme (IMCS) and modulation and coding scheme (MCS) tables configured by L1 signaling (e.g. downlink control information (DCI)) and high-layer parameters. In the MCS tables, the value R related to rate is a float value. Therefore, the intermediate value Ninfo needs to be retained sufficient precision, to avoid making a wrong choice on performing the step 3 or step 4 as the subsequence step based on the comparison between the intermediate value Ninfo and the integer (i.e. 3824) in step 2.
However, the UE with different capability may have different implementations on the numeric precision of the intermediate value Ninfo. For example, the UE only working with integers may use step 3 as the next step of TBS determination when the intermediate value Ninfo is larger than 3824 and less than 3825. In comparison, the UE working with floats may use step 4 as the next step when the intermediate value Ninfo is larger than 3824 and less than 3825. Under such a condition, two different TBSs, e.g. 3824 and 3840, may be determined based on the same resource parameters.
Moreover, the UE and/or the BS may determine different base graphs (e.g. base graphs of low density parity check (LDPC)) related to data processing (e.g. encoding data) if the UE and the BS have different understandings on the numeric precision of the intermediate value since the base graph is determined based on the TBS. For example, when the value R related to rate is larger than ¼ and less than ⅔, a base graph BG1 is determined if the TBS is greater than 3824 and a base graph BG2 is determined if the TBS is smaller than or equal to 3824. In other words, the UE and the BS may determine different base graphs when the UE and the BS have different understandings on the numeric precision of the intermediate value, resulting in transmission failures. These are all irretrievable impacts on the wireless communication system.
In an embodiment, considering different understandings on determining (e.g. modifying) the intermediate value Ninfo, the present disclosure provides a method of determining the TBS based on a parameter or a signaling associated with an event of determining the intermediate value Ninfo, so as to ensure the reliability of data transmissions between the UE and the BS. In an embodiment, the parameter or the signaling indicates the capability of UE processing (e.g. modifying) the intermediate value Ninfo during the procedure of determining the TBS.
In an embodiment, BS obtains the release version of the UE based on a high-layer parameter. In an embodiment, the high-layer parameter can indicate at lease one of the release versions. In an embodiment, the release versions supported by a UE includes at least one of the following: release 15, release 16, release 17. For example, the high-layer parameter is the information element AccessStratumRelease indicates the release supported by the UE.
In an embodiment, the spare7 can represent the release after release 15. For example, the spare7 represents the release16 supported by the UE. In an embodiment, the UE shall inform the BS of the current release supported by the UE. In an embodiment, the UE can report the UE feature(s) information supported by the UE. In an embodiment, the UE feature(s) information corresponds to the reported release version. In an embodiment, the UE feature(s) information corresponds to the other release version except for the reported release version. In an embodiment, the UE feature(s) information includes the parameter or signaling associated with the event of determining the intermediate value of the TBS determination procedure. In an embodiment, the feature associated with the event of determining the intermediate value is available for rel15-UE. In an embodiment, the feature associated with the event of determining the intermediate value is available for rel16-UE. In an embodiment, the feature associated with the event of determining the intermediate value is available for both rel15-UE and rel16-UE. Note that, the rel15-UE represents the UE supporting release 15, the rel16-UE represents the UE supporting release 16, and so on.
In an embodiment, the parameter associated with an event of determining the intermediate value Ninfo is used for a predefined type of UE. In an embodiment, the predefined type of UE is a UE supporting release 15. In an embodiment, the UE supporting release 15 shall determine the intermediate value based on the method indicated by the UE feature reported by the UE. In an embodiment, the UE supporting other release(s) after release 15, e.g. release 16, determines the intermediate value based on the predefined method.
In an embodiment, the predefined type of UE is a UE supporting the release after release 15. For example, the predefined type of UE is a UE supporting release 16. In an embodiment, the UE supporting release 16 shall determine the intermediate value based on the reported method indicated by the feature.
In an embodiment, the predefined type of UE is a UE supporting release 16. In an embodiment, the UE supporting release 16 shall determine the intermediate value based on the method indicated by the UE feature reported by the UE. In an embodiment, the UE shall determine the intermediate value based on the method supported by the UE in release 16 if the UE supporting release 16 falls back to the release 15-UE feature(s).
In an embodiment, the predefined type of UE is a UE supporting both release 15 and the release(s) after release 15. For example, the predefined type of UE is a UE supporting release 15 and release 16. In an embodiment, the UE shall determine the intermediate value based on the method supported by the UE in release 16 if the UE supporting release 16 falls back to the release 15-UE feature(s).
In an embodiment, the predefined method of determining the intermediate value is
Ninfo=function(NRE·R·Qm·v)
In an embodiment, the BS schedules data to the UE based on the parameter or the signaling. In an embodiment, the UE calculates the intermediate value Ninfo based on the parameter or the signaling for determining the TBS. In an embodiment, the UE has (e.g. equips with) the parameter or the signaling and transmits (e.g. reports) the parameter or the signaling to the BS.
In an embodiment, the parameter or the signaling is a UE capability parameter or a UE feature or a high-layer signaling, or a UE category n, wherein n is an integer and not smaller than 1.
In an embodiment, the BS determines the TBS by using a predefined calculation method associated with the intermediate value Ninfo according to the parameter or the signaling. In an embodiment, the UE determines the TBS by using a predefined calculation method associated with the intermediate value Ninfo according to the parameter or the signaling. In an embodiment, the UE does not have the parameter or the signaling, or the parameter or the signaling is not transmitted to the BS. In an embodiment, the TBS associated with the intermediate value Ninfo or resource allocation satisfied with a predefined condition is not expected or required to be used in the predefined calculation method. In an embodiment, the predefined condition is that the intermediate value Ninfo equals to at least one of the float numbers between 3824 and 3825. In an embodiment, the predefined condition is the intermediate value Ninfo is rounded down to 3824. In an embodiment, the predefined condition is the intermediate value Ninfo is rounded up to 3825.
In an embodiment, the method of calculating (e.g. modifying) the intermediate value Ninfo during the procedure of determining the TBS is determined based on the parameter or the signaling. In an embodiment, the event which is associated with the intermediate value Ninfo and indicated by the parameter or the signaling is whether the intermediate value Ninfo is modified by a predefined function during the procedure of determining the TBS. In an embodiment, the predefined function is one of rounding down, rounding up, rounding or retaining at a float precision.
In an embodiment, the parameter or the signaling indicates whether the UE supports retaining the intermediate value Ninfo at the float precision (i.e. modifying the intermediate value Ninfo by retaining the intermediate value Ninfo at the float precision) during the procedure of determining the TBS. When the parameter or the signaling indicates the UE supports retaining the intermediate value Ninfo at the float precision, the UE and/or the BS calculates the intermediate value Ninfo (e.g. by Ninfo=NRE·R·Qm·v) at the float precision. When the parameter or the signaling indicates the UE does not support retaining the intermediate value Ninfo at the float precision, the UE and/or BS calculates the intermediate value Ninfo by using a predefined function. For example, the UE and/or BS may calculates the intermediate value Ninfo by:
Ninfo=function(NRE·R·Qm·v)
In an embodiment of the UE determines not having the parameter or the signaling (e.g. the parameter or the signaling does not exist) indicating whether the UE supports retaining the intermediate value Ninfo at the float precision or the parameter or the signaling indicating whether the UE supports retaining the intermediate value Ninfo at the float precision is not transmitted to the BS, the UE and/or BS calculates the intermediate value Ninfo (e.g. by Ninfo=NRE·R·Qm·v) at the float precision.
In an embodiment of the UE does not have the parameter or the signaling indicating whether the UE supports retaining the intermediate value Ninfo at the float precision or the parameter or the signaling indicating whether the UE supports retaining the intermediate value Ninfo at the float precision is not transmitted to the BS, the UE and/or BS calculates the intermediate value Ninfo by using a predefined function during the procedure of determining the TBS. For example, the UE and/or BS may calculate the intermediate value Ninfo by:
Ninfo=function(NRE·R·Qm·v)
In an embodiment, the parameter or the signaling indicates whether the UE supports calculating the intermediate value Ninfo by using a predefined function, wherein the predefined function may be rounding down, rounding up or rounding. For example, the parameter or the signaling indicates whether the UE supports calculating the intermediate value Ninfo by:
Ninfo=function(NRE·R·Qm·v)
In an embodiment of the parameter or the signaling indicating the UE supports calculating the intermediate value Ninfo by using the predefined function, the UE and/or BS calculates the intermediate value Ninfo by using the predefined function.
In an embodiment of the parameter or the signaling indicating the UE does not support calculating the intermediate value Ninfo by using the predefined function, the UE and/or BS calculates the intermediate value Ninfo by retaining the intermediate value Ninfo at the float precision.
In an embodiment of the UE does not have the parameter or the signaling indicating whether the UE supports calculating the intermediate value Ninfo by using the predefined function or the parameter or the signaling indicating whether the UE supports calculating the intermediate value Ninfo by using the predefined function is not transmitted to the BS, the UE and/or BS calculates the intermediate value Ninfo by using the predefined function. For example, the UE and/or BS may calculate the intermediate value Ninfo by:
Ninfo=function(NRE·R·Qm·v)
In an embodiment, the parameter or the signaling indicates valid or available resource parameters (e.g. with specific values) of determining the intermediate value Ninfo. In an embodiment, the TBS(s) corresponding to the resource parameters indicated by the parameter or the signaling may not be used for data transmission when the resource parameters are determined invalid based on the parameter or the signaling.
In an embodiment, the parameter or the signaling is signaled per UE. In an embodiment, if the UE supports both the frequency ranges FR1 and FR2, the parameter or the signaling has the same value for the frequency ranges FR1 and FR2. In an embodiment, if the UE supports both FDD and TDD, the parameter or the signaling has the same value for FDD and TDD. In an embodiment, the parameter or the signaling is an RRC parameter. In an embodiment, the parameter or the signaling is a MAC parameter. In an embodiment, the parameter or the signaling is a physical layer parameter.
In an embodiment, the parameter or the signaling indicates whether the resource parameters satisfying a predefined condition are valid or available for determining the intermediate value Ninfo. In an embodiment, the predefined condition may be whether function(NRE·R·Qm·v) is equal to a number within a range, wherein function(x) represents transforming (e.g. modifying) the value of x into an integer. In an embodiment, function(x) represents rounding the value of x down to an integer. In an embodiment, function(x) represents rounding the value of x up to an integer. In an embodiment, function(x) represents rounding the value of x to an integer. In an embodiment, function(x) denotes retaining the value of x at the float precision. In an embodiment, the range is a fixed integer. In an embodiment, the range is between two adjacent integers (e.g. 3824 and 3825).
In an embodiment, when determining not having the parameter or the signaling indicating whether the resource parameters satisfying the predefined condition is valid or determining the parameter or the signaling is not transmitted to the BS, the UE and/or BS may assume that the resource parameters satisfying the predefined condition are valid (e.g. the TBS(s) corresponding to the resource parameters satisfying the predefined condition is valid).
In an embodiment, when determining not having the parameter or the signaling indicating whether the resource parameters satisfying the predefined condition is valid or determining the parameter or the signaling is not transmitted to the BS, the UE and/or BS may assume that the resource parameters satisfying the predefined condition are invalid (e.g. the TBS(s) corresponding to the resource parameters satisfying the predefined condition is invalid).
In an embodiment, the parameter or the signaling indicates whether the resource parameters satisfying floor(NRE·R·Qm·v)=3824 are valid, wherein floor(x) denotes rounding the value of x down to an integer. When the parameter or the signaling indicates the resource parameters satisfying floor(NRE·R·Qm·v)=3824 are valid, the UE and/or BS may use the TBS(s) determined based on the resource parameters satisfying floor(NRE·R·Qm·v)=3824 for data transmissions. When the parameter or the signaling indicates the resource parameters satisfying floor(NRE·R·Qm·v)=3824 are invalid, the UE and/or BS does not use the TBS(s) determined based on the resource parameters satisfying floor(NRE·R·Qm·v)=3824 for data transmissions.
In an embodiment of determining not having the parameter or the signaling indicating whether the resource parameters satisfying floor(NRE·R·Qm·v)=3824 are valid, the UE and/or the BS assumes the resource parameters satisfying floor(NRE·R·Qm·v)=3824 are valid. For example, the UE may assume the TBS(s) corresponding to the resource parameters satisfying floor(NRE·R·Qm·v)=3824 is valid when determining not having the parameter or the signaling indicating whether the resource parameters satisfying floor(NRE·R·Qm·v)=3824.
In an embodiment of determining not having the parameter or the signaling indicating whether the resource parameters satisfying floor(NRE·R·Qm·v)=3824 are valid, the UE and/or the BS assumes the resource parameters satisfying floor(NRE·R·Qm·v)=3824 are invalid. For example, the UE may assume the TBS(s) corresponding to the resource parameters satisfying floor(NRE·R·Qm·v)=3824 is invalid when determining not having the parameter or the signaling indicating whether the resource parameters satisfying floor(NRE·R·Qm·v)=3824.
In an embodiment, the parameter or the signaling indicates whether the resource parameters satisfying 3824<float(NRE·R·Qm·v)<3825 are valid, wherein float(x) denotes retaining the value of x as the float precision. When the parameter or the signaling indicates the resource parameters satisfying 3824<float(NRE·R·Qm·v)<3825 are valid, the UE and/or BS may use the TBS(s) determined based on the resource parameters satisfying 3824<float(NRE·R·Qm·v)<3825 for data transmissions. When the parameter or the signaling indicates the resource parameters satisfying 3824<float(NRE·R·Qm·v)<3825 are invalid, the UE and/or BS does not use the TBS(s) determined based on the resource parameters satisfying 3824<float(NRE·R·Qm·v)<3825 for data transmissions.
In an embodiment of determining not having the parameter or the signaling indicating whether the resource parameters satisfying 3824<float(NRE·R·Qm·v)<3825 are valid, the UE and/or the BS assumes the resource parameters satisfying 3824<float(NRE·R·Qm·v)<3825 are invalid. For example, the UE may assume the TBS(s) corresponding to the resource parameters satisfying 3824<float(NRE·R·Qm·v)<3825 is invalid when determining not having the parameter or the signaling indicating whether the resource parameters satisfying 3824<float(NRE·R·Qm·v)<3825.
In an embodiment, the parameter or the signaling indicates whether the resource parameters satisfying 3824≤float(NRE·R·Qm·v)<3825 are valid, wherein float(x) denotes retaining the value of x as the float precision. When the parameter or the signaling indicates the resource parameters satisfying 3824≤float(NRE·R·Qm·v)<3825 are valid, the UE and/or BS may use the TBS(s) determined based on the resource parameters satisfying 3824≤float(NRE·R·Qm·v)<3825 for data transmissions. When the parameter or the signaling indicates the resource parameters satisfying 3824 float(NRE·R·Qm·v)<3825 are invalid, the UE and/or BS does not use the TBS(s) determined based on the resource parameters satisfying 3824≤float(NRE·R·Qm·v)<3825 for data transmissions.
In an embodiment of determining not having the parameter or the signaling indicating whether the resource parameters satisfying 3824≥float(NRE·R·Qm·v)<3825 are valid, the UE and/or the BS assumes the resource parameters satisfying 3824≥float(NRE·R·Qm·v)<3825 are invalid. For example, the UE may assume the TBS(s) corresponding to the resource parameters satisfying 3824≤float(NRE·R·Qm·v)<3825 is invalid when determining not having the parameter or the signaling indicating whether the resource parameters satisfying 3824≤float(NRE·R·Qm·v)<3825.
In an embodiment, the parameter or the signaling indicates valid or available TBS(s), e.g., for UE and/or BS. In an embodiment, the parameter or the signaling indicates the valid or available TBS(s) by indicating valid or available intermediate value(s) Ninfo In an embodiment, this parameter or the signaling is signaled per UE. If the UE supports both the frequency ranges FR1 and FR2, this parameter or the signaling has the same value for the frequency ranges FR1 and FR2. If the UE supports both FDD and TDD, this parameter or the signaling has the same value for FDD and TDD. In an embodiment, the parameter or the signaling is a RRC parameter. In an embodiment, this parameter or the signaling is a MAC parameter. In an embodiment, this parameter or the signaling is a physical layer parameter.
In an embodiment, the parameter or the signaling indicates whether TBS(s) in a TBS set is supported (e.g. valid). In an embodiment, the parameter or the signaling indicates whether TBS(s) corresponding to each intermediate value Ninfo in an intermediate value set is supported (e.g. valid). When the parameter or the signaling indicates TBS(s) in the TBS set or corresponding to the each intermediate value Ninfo in the intermediate value set is supported, the UE may use the indicated TBS for performing data transmissions. When the parameter or the signaling indicates TBS(s) in the TBS set or corresponding to each intermediate value Ninfo in the intermediate value set is not supported, the UE may not use the indicated TBS for performing data transmissions. In an embodiment, all of TBSs in the TBS set or corresponding to each intermediate value Ninfo in the intermediate value set are integers, which can be evenly divisible by 8. In an embodiment, TBS(s) in the TBS set or corresponding to each intermediate value Ninfo in the intermediate value set comprises at least one of 3824, 3840 and/or 3848.
In an embodiment of the parameter or the signaling indicating valid or available TBS(s), the UE and/or BS may assume the indicated TBS(s) is valid for data transmissions when determining that the UE does not have the parameter or the signaling and/or that the UE does not transmit the parameter or the signaling to the BS.
In an embodiment of the parameter or the signaling indicating valid or available TBS(s), the UE and/or BS may assume the indicated TBS(s) is invalid for data transmissions when determining that the UE does not have the parameter or the signaling and/or that the UE does not transmit the parameter or the signaling to the BS.
In an embodiment, the parameter or the signaling indicates whether TBS=3824 (i.e. TBS set or the TBS corresponding to each intermediate value Ninfo in an intermediate value set comprises 3824) is supported. When the parameter or the signaling indicates TBS=3824 is supported, the UE and/or BS may perform data transmissions by using the TBS with the value of 3824. When the parameter or the signaling indicates TBS=3824 is not supported, the UE and/or BS does not use the TBS with the value of 3824 to perform data transmissions. In this embodiment, the function of modifying the intermediate value Ninfo may be rounding down (i.e. Ninfo=floor(NRE·R·Qm·v)). In this embodiment, the function of modifying the intermediate value Ninfo may be rounding up (i.e. Ninfo=ceil(NRE·R·Qm·v), wherein ceil(x) denotes rounding the value of x up to an integer). In this embodiment, the function of modifying the intermediate value Ninfo may be rounding. In this embodiment, the function of modifying the intermediate value Ninfo may be retaining at the float precision (i.e. Ninfo=float(NRE·R·Qm·v), wherein float(x) denotes retaining the value of x at the float precision).
In an embodiment of the parameter or the signaling indicating whether TBS=3824 is supported, the UE and/or BS may assume the TBS with the value of 3824 is valid for data transmissions when determining that the UE does not have the parameter or the signaling and/or that the parameter or the signaling is not transmitted to the BS.
In an embodiment of the parameter or the signaling indicating whether TBS=3824 is supported, the UE and/or BS may assume the TBS with the value of 3824 is invalid for data transmissions when determining that the UE does not have the parameter or the signaling and/or that the parameter or the signaling is not transmitted to the BS.
In an embodiment, the parameter or the signaling indicates whether TBSs=3840 and 3848 (i.e. TBS set or the TBSs corresponding to each intermediate value Ninfo in an intermediate value set comprise 3840 and 3848) are supported. When the parameter or the signaling indicates TBSs=3840 and 3848 are supported, the UE and/or BS may perform data transmissions by using the TBS with the value of 3840 or 3848. When the parameter or the signaling indicates TBSs=3840 and 3848 are not supported, the UE and/or BS does not use the TBS with the value of 3840 or 3848 to perform data transmissions. In this embodiment, the function of modifying the intermediate value Ninfo may be rounding down (i.e. Ninfo=floor(NRE·R·Qm·v)). In this embodiment, the function of modifying the intermediate value Ninfo may be rounding up (i.e. Ninfo=ceil(NRE·R·Qm·v), wherein ceil(x) denotes rounding the value of x up to an integer). In this embodiment, the function of modifying the intermediate value Ninfo may be rounding. In this embodiment, the function of modifying the intermediate value Ninfo may be retaining at the float precision (i.e. Ninfo=float(NRE·R·Qm·v), wherein float(x) denotes retaining the value of x at the float precision).
In an embodiment of the parameter or the signaling indicating whether TBSs=3840 and 3848 is supported, the UE and/or BS may assume the TBS with the value of 3840 or 3848 is valid for data transmissions when determining that the UE does not have the parameter or the signaling and/or that the parameter or the signaling is not transmitted to the BS.
In an embodiment of the parameter or the signaling indicating whether TBSs=3840 and 3848 is supported, the UE and/or BS may assume the TBS with the value of 3840 or 3848 is invalid for data transmissions when determining that the UE does not have the parameter or the signaling and/or that the parameter or the signaling is not transmitted to the BS.
In an embodiment, a base graph of data processing (e.g. base graph of LDPC coding) is determined based on the TBS and a threshold which related to the TBS and used for determining the base graph is adjusted by a modified factor β at at least one event. In an embodiment, the modified factor is smaller than or equal to 24 and is greater than or equal to −24. In an embodiment, the at least one event comprises at least one of:
More specifically, in an embodiment, the base graph BG2 for UL/DL data transmissions is determined based on a predefined condition PC1. In an embodiment, the base graph BG1 for UL/DL data transmissions is determined based on a predefined condition PC2. In an embodiment, the predefined condition PC1 is configured by the L1 signaling or high-layer signaling. In an embodiment, the predefined condition PC1 is a float value R related to the rate is larger than a threshold r0 and not larger than a threshold r1, wherein the thresholds r0 and r1 are float numbers and may be equal to zero. In an embodiment, the predefined condition PC1 is the TBS is larger than a threshold t0 and not larger than a threshold t1, wherein the thresholds t0 and t1 are integer numbers and not smaller than 0. In an embodiment, the predefined condition PC2 is configured by L1 signaling or high-layer signaling. In an embodiment, the predefined condition PC2 is the value R related to the rate is larger than a threshold r2 and not larger than a threshold r3, wherein the thresholds r2 and r3 are float numbers and may be equal to zero. In an embodiment, the predefined condition PC2 is the TBS is larger than a threshold t2 and not larger than a threshold t3, wherein the thresholds t2 and t3 are integer numbers and not smaller than 0. In an embodiment, the threshold t1 is equal to the threshold t2 based on a specific condition of the value R. In an embodiment, the threshold r1 is equal to the threshold r2 based on a specific condition of TBS. In an embodiment, the threshold t0 is equal to the threshold t2 and the threshold t1 is equal to the threshold t3 based on a specific condition of the value R. In an embodiment, the threshold r0 is equal to the threshold r2 and the threshold r1 is equal to the threshold r3 based on a specific condition of TBS.
In an embodiment, if the TBS is larger than the threshold t0 and not larger than the threshold t1 when the value R satisfies a specific condition SC1, the base graph BG2 for UL/DL data transmissions is determined selected. In this embodiment, the threshold t1 is adjusted to 3824+β. In an embodiment, if TBS is larger than the threshold t2 and not larger than the threshold t3 when the value R satisfies the same specific condition SC1, the base graph BG1 for UL/DL data transmissions is determined, wherein the threshold t2 is adjusted to be equal to the threshold t1. In an embodiment, the modified factor β is a positive integer and not smaller than 16. In an embodiment, the modified factor β is a negative integer and not greater than −8. In an embodiment, the specific condition SC1 is that the value R is not larger than ⅔. In an embodiment, the specific condition SC1 is that the value R is larger than ¼.
In an embodiment, the UE assumes that the TBS determined as a specific value may be the TBS with another value when the data is not successfully decoded by using the TBS with the specific value. In an embodiment, the specific value is 3824, 3840 or 3848, and the TBS with another value is one of 3824, 3840 and 3848 except for the specific value.
In an embodiment, the modified factor β is 24. In this embodiment, when the value R≤¼, the base graph BG2 for data processing is determined (e.g. selected). When ¼<R≤⅔ and the TBS is larger than the threshold t0=0 and not larger than the threshold t1=3848, the base graph BG2 is selected. In an implementation, when ¼<R≤⅔ and the TBS is larger than the threshold t2=3848, the base graph BG1 for data processing is selected. In an embodiment, when R>⅔ and the TBS is not larger than 292, the base graph BG2 is selected. In an embodiment, when R>⅔ and the TBS is larger than 292, the base graph BG1 is selected. For example, the BG selection mechanism may be expressed as the table shown in
In an embodiment, if when the UE modifies the intermediate value Ninfo by retaining the intermediate value Ninfo at the float precision during the procedure of determining the TBS and is scheduled with TBS=3840 and ¼<R≤⅔, the UE may assume that TBS=3824 after the transport block (TB) cyclic redundancy check (CRC) is not decoded successfully. For example, when the UE modifies the intermediate value Ninfo by retaining the intermediate value Ninfo at the float precision during the procedure of determining the TBS and determines that TBS=3840, the UE selects the base graph BG2 to encode or decode the scheduling data. If the UE dose not decode the TB CRC successfully, the UE may assume that TBS=3824 and decodes the schedule data and TB CRC bits by using the TBS=3824.
Based on the table shown in
In an embodiment, the modified factor β is −8. In this embodiment, when the value R≤¼, the base graph BG2 for data processing is determined (e.g. selected). When ¼<R≤⅔ and the TBS is smaller than the threshold 3824 (i.e. 3816<t1<3824), the base graph BG2 is selected. In an implementation, when ¼<R≤⅔ and the TBS is not smaller than 3824, the base graph BG1 for data processing is selected. In an embodiment, when R>⅔ and the TBS is not larger than 292, the base graph BG2 is selected. In an embodiment, when R>⅔ and the TBS is larger than 292, the base graph BG1 is selected. For example, the BG selection mechanism may be expressed as the table shown in
Based on the table shown in
In an embodiment, the modified factor β is the maximum value of TBS available for UL/DL data transmission. In this embodiment, when the value R<¼, the base graph BG2 for data processing is determined (e.g. selected). When ¼<R≤⅔ and the TBS is larger than the threshold t0=0, the base graph BG2 is selected. For example, the BG selection mechanism may be expressed as the table shown in
In an embodiment, when the value R<¼, the base graph BG2 for data processing is determined (e.g. selected). When ¼<R and the TBS is larger than the threshold t0=292, the base graph BG1 is selected. For example, the BG selection mechanism may be expressed as the table shown in
In an embodiment, the UE calculating the intermediate value Ninfo in the integer precision may utilize a new base graph based on a predefined condition. In an embodiment, the predefined condition is that intermediate value Ninfo is not smaller than 3824 and smaller than 3825. In an embodiment, the predefined condition is that the TBS is equal to 3824 and the scheduled data is not received successfully by the UE. In an embodiment, the predefined condition is that the TBS is equal to 3840 or 3848 and the scheduled data is not received successfully by the UE. In an embodiment, the predefined condition is that the TBS is equal to 3824 and the intermediate value Ninfo calculated by Ninfo=floor(NRE·R·Qm·v). In an embodiment, the predefined condition is that the TBS is equal to 3840 or 3848 and the intermediate value Ninfo is calculated by: Ninfo=float(NRE·R·Qm·v).
In an embodiment, for the second step of TBS determination procedure, if floor(NRE*R*Qm*v*2N)<3824*2N, the UE shall use step 3 as the next step of the TBS determination, otherwise, the UE shall use step 4 as the next step of the TBS determination. In an embodiment, N is an integer that is not smaller than 5.
In an embodiment, the UE and/or BS determines the intermediate value Ninfo based on a plurality of resource parameters, for determining the TBS. In an embodiment, the plurality of parameters comprises the total number NRE of resource elements, the value R related to rate, the modulation order Qm and the number v of layers. In an embodiment, the intermediate value Ninfo is a fixed function of the product of the plurality of parameters. In an embodiment, the fixed function is one of rounding down, or rounding up, or rounding.
For example, the UE determines the total number NRE of resource elements and then calculates the intermediate value Ninfo by:
Ninfo=function(NRE·R·Qm·v)
While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand exemplary features and functions of the present disclosure. Such persons would understand, however, that the present disclosure is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.
It is also understood that any reference to an element herein using a designation such as “first,” “second,” and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
A skilled person would further appreciate that any of the various illustrative logical blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two), firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as “software” or a “software unit”), or any combination of these techniques.
To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, units, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure. In accordance with various embodiments, a processor, device, component, circuit, structure, machine, unit, etc., can be configured to perform one or more of the functions described herein. The term “configured to” or “configured for” as used herein with respect to a specified operation or function refers to a processor, device, component, circuit, structure, machine, unit, etc., that is physically constructed, programmed and/or arranged to perform the specified operation or function.
Furthermore, a skilled person would understand that various illustrative logical blocks, units, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, units, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.
Computer-readable media comprises both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
In this document, the term “unit” as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various units are described as discrete units; however, as would be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according embodiments of the present disclosure.
Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present disclosure. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.
Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the implementations shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.
This application claims the benefit of priority under 35 U.S.C. § 120 as a continuation of PCT Patent Application No. PCT/CN2020/073369, filed on Jan. 21, 2020, the disclosure of which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 10924202 | Lin | Feb 2021 | B2 |
| 11166273 | Wang | Nov 2021 | B2 |
| 20170094668 | Tsai | Mar 2017 | A1 |
| 20190158221 | Sarkis | May 2019 | A1 |
| 20210234571 | Wang | Jul 2021 | A1 |
| 20220029737 | Park | Jan 2022 | A1 |
| 20220201711 | Lee | Jun 2022 | A1 |
| 20220232623 | Lee | Jul 2022 | A1 |
| 20230043797 | Myung | Feb 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 102244628 | Nov 2011 | CN |
| 109152017 | Jan 2019 | CN |
| WO-2018126413 | Jul 2018 | WO |
| WO-2019069285 | Apr 2019 | WO |
| WO-2019095315 | May 2019 | WO |
| WO-2019191973 | Oct 2019 | WO |
| Entry |
|---|
| International Search Report and Written Opinion for PCT Appl. No. PCT/CN2020/073369, mailed Oct. 29, 2020 (8 pages). |
| Extended European Search Report for EP Appl. No. 20887844.7, dated Jul. 19, 2023 (12 pages). |
| Mediatek Inc., “On TBS determination procedure”, 3GPP TSG RAN WG1 Meeting AH-1801, R1-1800170, Jan. 26, 2016, Vancouver, Canada (10 pages). |
| Qualcomm Incorporated, “TBS and Base-graph Determination”, 3GPP TSGRAN WG1 Meeting 91, R1-1720699, Dec. 1, 2017, Reno, USA (10 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20230008284 A1 | Jan 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2020/073369 | Jan 2020 | WO |
| Child | 17869683 | US |
