Method and apparatus for downlink shared channel performance enhancement

Abstract

The invention name of the present disclosure is "Method and apparatus for downlink shared channel performance enhancement". A method performed by a wireless device (WD) comprises receiving a control message. The control message indicates at least a modulation and coding scheme (MCS) and a scaling factor for a downlink shared channel. The scaling factor indicates a value less than 1. The method further comprises determining a transport block size (TBS) based on the MCS and the scaling factor indicated in the control message. A method performed by a network node comprises indicating at least a modulation and coding scheme (MCS) and a scaling factor for a downlink shared channel in a control message. The scaling factor indicates a value less than 1. The method further comprises transmitting the control message to a user equipment (UE), the control message enabling determination of a transport block size (TBS) for the shared downlink channel.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications and more specifically to enhancing the performance of downlink shared channels in wireless communication networks. Background Technology

[0002] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant art, unless a different meaning is implied and / or clearly given from the context of their use. Unless otherwise expressly stated, all references to "a / an / element, device, component, part, step, etc." are to be interpreted openly as referring to at least one instance of that element, device, component, part, step, etc. Unless a step is explicitly described as occurring after or before another step, and / or implied therein that a step must occur after or before another step, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment of the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment of the embodiments may be applied to any other embodiment, and vice versa. Further objects, features, and advantages of the appended embodiments will become apparent from the following description.

[0003] resource blocks

[0004] The 3rd Generation Partnership Project (3GPP) is the process of defining the technical specifications for New Radio (NR) (e.g., 5G). In Release 15 (Rel-15) NR, a User Equipment (UE) can be configured with up to four Carrier Bandwidth Parts (BWPs) in the downlink, where a single downlink carrier bandwidth portion is active at any given time. A UE can also be configured with up to four carrier bandwidth portions in the uplink, where a single uplink carrier bandwidth portion is active at any given time. If the UE is configured with a supplementary uplink, it can further configure up to four carrier bandwidth portions in the supplementary uplink, where a single supplementary uplink carrier bandwidth portion is active at any given time.

[0005] For a given parameter set μ i The carrier bandwidth portion defines a contiguous set of Physical Resource Blocks (PRBs), numbered from 0 to... Where i is the index of the carrier bandwidth portion. A resource block (RB) is defined in the frequency domain as 12 consecutive subcarriers.

[0006] Parameter set

[0007] As shown in Table 1, NR supports multiple sets of orthogonal frequency division multiplexing (OFDM) parameters μ, where the subcarrier spacing Δf and the cyclic prefix of the carrier bandwidth are configured by different higher-level parameters of the downlink (DL) and uplink (UL), respectively.

[0008] Table 1: Supported set of transmission parameters.

[0009] μ <![CDATA[Δf=2 μ ·15[kHz]]]> Cyclic prefix 0 15 Normal 1 30 Normal 2 60 Normal, extended 3 120 Normal 4 240 Normal

[0010] physical channel

[0011] A downlink physical channel corresponds to a set of resource elements carrying information originating from higher layers. The following downlink physical channels are defined:

[0012] Physical Downlink Shared Channel (PDSCH)

[0013] Physical Broadcast Channel (PBCH)

[0014] Physical Downlink Control Channel (PDCCH):

[0015] The PDSCH is the primary physical channel for unicast downlink data transmission, but it is also a primary physical channel for transmitting RAR (Random Access Response), certain system information blocks, and paging information. The PBCH carries the basic system information required by the UE to access the network. The PDCCH is used to transmit downlink control information (DCI) (mainly scheduling decisions) required to receive the PDSCH, and is used to enable uplink scheduling permission for transmission on the PUSCH.

[0016] An uplink physical channel corresponds to a set of resource elements that carry information from higher layers. The following uplink physical channels are defined:

[0017] Physical uplink shared channel (PUSCH)

[0018] Physical uplink control channel (PUCCH)

[0019] Physical Random Access Channel (PRACH)

[0020] PUSCH is the uplink counterpart of PDSCH. PUCCH is used by the UE to transmit uplink control information, including HARQ acknowledgments and channel state information reports. PRACH is used for random access preamble transmission.

[0021] Frequency resource allocation for PUSCH and PDSCH

[0022] Typically, the UE should use the resource allocation field in the detected DCI carried in the PDCCH to determine the RB assignment in the frequency domain for the PUSCH or PDSCH. For the PUSCH carrying msg3 during random access, the frequency domain resource assignment is signaled using the UL grant included in the RAR.

[0023] In NR, two frequency resource allocation schemes are supported for PUSCH and PDSCH: Type 0 and Type 1. Which type is used for PUSCH / PDSCH transmission is defined by parameters configured by Radio Resource Control (RRC), or directly indicated in the corresponding DCI or UL approval in the RAR (which Type 1 is used).

[0024] Within the UE's active carrier bandwidth portion, the RB index for uplink / downlink type 0 and type 1 resource allocation is determined. Upon detecting a PDCCH intended for the UE, the UE should first determine the uplink / downlink carrier bandwidth portion, and then determine the resource allocation within that portion. The ULBWP of the PUSCH carrying msg3 is configured by higher-layer parameters.

[0025] Channels and signals related to cell search and initial access

[0026] For cell search and initial access, the following channels are included: synchronization signals and PBCH blocks (SS / PBCH blocks, or in the shorter format "SSB"), PDSCH carrying Residual Minimum System Information (RMSI) / RAR / MSG4 scheduled by the PDCCH channel carrying DCI, PUSCH channel carrying MSG3 and PRACH channel during random access.

[0027] The SSB includes a synchronization signal and a PBCH. The synchronization signal may include, for example, a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH demodulation reference signal (DMRS). Depending on the frequency range, the SSB may have a 15kHz, 30kHz, 120kHz, or 240kHz SSS.

[0028] There are currently one or more challenges. For example, PDSCH may have certain performance challenges. The performance comparison between signal and channel has been performed as follows to find the weakest channel in NR.

[0029] The signals and channels under consideration are SS / PBCH block, PRACH, PDCCH, and PDSCH.

[0030] 1. For SS / PBCH blocks, the cell-id false detection rate, SSB time index detection rate, and PBCH block error rate (BLER) performance have been studied when extending 15kHz SCS, 1TX / 2RX, and low-frequency band under different UE speeds and different TDL-A channel delays.

[0031] Typically, at 10% BLER, PBCH performance is no worse than -4.3dB, and cell-id / SSB index detection performance is 2dB to 3dB better than PBCHBLER. Considering that SSBs repeat in SSB cycles, PBCHBLER can be improved by approximately 2dB to 3dB when two consecutive SSBs are combined. Therefore, at 10% BLER, the overall performance gain of SS / PBCH blocks can reach -6dB.

[0032] 2. For PDSCH, when the number of PRBs is small (e.g., for RAR, 3 PRBs will be allocated based on the current modulation and coding scheme (MCS) table and the RAR payload size), the performance simulated using precoder cyclic TX diversity (TX diversity used in NR) is only about -2.3dB at 10% BLER. This may not be a problem for RMSI, as RMSI can be repeated for an RMSI transmission time interval (TTI) (160ms), depending on how many RMSI are associated with SSB within this TTI. However, for RAR, PDSCH repetition is not supported.

[0033] 3. For PRACH, its performance has been studied using simulation assumptions similar to those of the SS / PBCH block, and the performance is quite good. That is, based on similar simulations, it can achieve -6dB in target false detection rate compared to the SS / PBCH block.

[0034] 4. For PDCCH, with a target BLER of 1%, at which an SNR below -6dB can be achieved based on simulations similar to SS / PBCH, since the aggregation level in NR can now be 16.

[0035] Therefore, based on the above comparisons, broadcast PDSCH is generally the weakest channel, especially when a small payload size and a small number of PRBs are allocated.

[0036] Therefore, some methods are needed to improve the performance of broadcast PDSCH.

[0037] Certain aspects of this disclosure and embodiments thereof may provide solutions to these or other challenges. For example, some embodiments propose solutions for improving receiver performance of broadcast PDSCH channels that limit the overall performance of NR. Some embodiments combine PDSCH performance.

[0038] This document presents various embodiments for solving one or more of the problems disclosed herein.

[0039] Some embodiments may provide one or more of the following technical advantages. For example, some embodiments improve the reception performance of the PDSCH. Summary of the Invention

[0040] According to some embodiments, a method performed by a network node is disclosed. The method includes indicating, at least in a control message, a modulation and coding scheme (MCS) and a scaling factor for a downlink shared channel. The scaling factor indicates a value less than 1. The method also includes sending a control message to a user equipment (UE). This control message enables the determination of the transport block size (TBS) for sharing the downlink channel.

[0041] According to some embodiments, the network node includes a memory and processing circuitry. The memory is operable to store instructions. The processing circuitry is operable to execute the instructions. The network node is operable to indicate, at least in a control message, a modulation and coding scheme (MCS) and a scaling factor for the downlink shared channel. The scaling factor indicates a value less than 1. The network node is also operable to send a control message to a user equipment (UE) that enables the determination of the transport block size (TBS) for the shared downlink channel.

[0042] According to some embodiments, a computer program product includes a non-transitory computer-readable medium storing computer-readable program code. The computer-readable program code includes program code for indicating, in a control message, at least a modulation and coding scheme (MCS) and a scaling factor for a downlink shared channel. The scaling factor indicates a value less than 1. The computer-readable program code also includes program code for sending the control message to a user equipment (UE). This control message enables the determination of the transport block size (TBS) for sharing the downlink channel.

[0043] The methods, network nodes, and / or computer program code described above may include various other features, including any one or more of the following:

[0044] In some embodiments, the control message enables the UE to determine the intermediate number of information bits based at least on the MCS and the scaling factor, and wherein the intermediate number of bits enables the UE to determine the TBS.

[0045] In some embodiments, the scaling factor is one of 1 / 2 and 1 / 4.

[0046] In some embodiments, the control message includes a bit that indicates that a first scaling factor is used when the bit is set to a first value, and a second scaling factor is used when the bit is set to a second value.

[0047] In some embodiments, the control message includes at least one bit indicating that 1 / 2 is used as a scaling factor when the first bit of the at least one bit is set to 0, and 1 / 4 is used as a second scaling factor when the first bit is not set to 0.

[0048] In some embodiments, control messages are sent via the Physical Downlink Control Channel (PDCCH).

[0049] In some embodiments, the scaling factor is indicated in the control message via PDCCH, and the scaling factor includes a value of 1 / 2 or 1 / 4.

[0050] In some embodiments, the shared channel is the Physical Downlink Shared Channel (PDSCH). In some embodiments, the PDSCH is a broadcast channel.

[0051] In some embodiments, control messages are carried on the PDCCH, which has a cyclic redundancy check (CRC) scrambled with a Radio Network Temporary Identifier (RNTI), including System Information RNTI (SI-RNTI), Random Access RNTI (RA-RNTI), or Paging RNTI (P-RNTI).

[0052] In some embodiments, the method / network node / computer program code that enables the UE to determine the TBS also enables the UE to decode the transport block of the shared channel.

[0053] In some embodiments, the control message also indicates time-domain repetition or frequency-domain repetition.

[0054] In some embodiments, the MCS indicated in the control message includes a lower spectral efficiency than a normal MCS. In some embodiments, a normal MCS corresponds to an MCS according to 3GPP Technical Specification (TS) version 38.214 15.2.0 or earlier.

[0055] In some embodiments, the method / network node / computer program code also includes determining the MCS to be indicated in the control message based on a table defined for the enhanced mobile broadband (eMBB) PDSCH.

[0056] In some embodiments, the method / network node / computer program code also includes determining the MCS to be indicated in the control message based on a table or table entry specifically defined for PDSCH.

[0057] In some embodiments, the method / network node / computer program code also includes allocating physical resource blocks (PRBs) at least in part based on TBS.

[0058] According to some embodiments, a method performed by a wireless device is disclosed. The method includes receiving a control message. The control message at least indicates a modulation and coding scheme (MCS) and a scaling factor for a downlink shared channel. The scaling factor indicates a value less than 1. The method further includes determining a transport block size (TBS) based on the MCS and scaling factor indicated in the control message.

[0059] According to some embodiments, the wireless device includes a memory and processing circuitry. The memory is operable to store instructions. The processing circuitry is operable to execute the instructions. The wireless device is operable to receive control messages. The control messages at least indicate a modulation and coding scheme (MCS) and a scaling factor for the downlink shared channel. The scaling factor indicates a value less than 1. The wireless device is also operable to determine a transport block size (TBS) based on the MCS and scaling factor indicated in the control message.

[0060] According to some embodiments, a computer program product includes a non-transitory computer-readable medium storing computer-readable program code. The computer-readable program code includes program code for receiving a control message. The control message at least indicates a modulation and coding scheme (MCS) and a scaling factor for a downlink shared channel. The scaling factor indicates a value less than 1. The computer-readable program code also includes program code for determining a transport block size (TBS) based on the MCS and scaling factor indicated in the control message.

[0061] The methods, wireless devices, and / or computer program code described above may include various other features, including any one or more of the following:

[0062] In some embodiments, the method / wireless device / computer program code for determining TBS based on the MCS and scaling factor indicated in the control message includes determining the median number of information bits based at least on the MCS and scaling factor.

[0063] In some embodiments, the scaling factor is one of 1 / 2 and 1 / 4.

[0064] In some embodiments, the control message includes at least one bit indicating that a first scaling factor is used when the first bit of the at least one bit is set to a first value, and a second scaling factor is used when the first bit is set to a second value.

[0065] In some embodiments, the control message includes at least one bit indicating that 1 / 2 is used as a scaling factor when the first bit of the at least one bit is set to 0, and 1 / 4 is used as a second scaling factor when the first bit is not set to 0.

[0066] In some embodiments, control messages are sent via the Physical Downlink Control Channel (PDCCH).

[0067] In some embodiments, the scaling factor is indicated in the control message via PDCCH, and the scaling factor includes a value of 1 / 2 or 1 / 4.

[0068] In some embodiments, the shared channel is the Physical Downlink Shared Channel (PDSCH). In some embodiments, the PDSCH is a broadcast channel.

[0069] In some embodiments, control messages are carried on the PDCCH, which has a cyclic redundancy check (CRC) scrambled with radio network temporary identifiers (RNTIs), including system information RNTI (SI-RNTI), random access RNTI (RA-RNTI), or paging RNTI (P-RNTI).

[0070] In some embodiments, the method / wireless device / computer program code further includes decoding transport blocks of the downlink shared channel based on TBS, wherein the TBS is determined based on the MCS and scaling factor indicated in the control message.

[0071] In some embodiments, the control message also indicates time-domain repetition or frequency-domain repetition.

[0072] In some embodiments, the MCS indicated in the control message includes a lower spectral efficiency than a normal MCS. In some embodiments, a normal MCS corresponds to an MCS according to 3GPP Technical Specification (TS) version 38.214 15.2.0 or earlier.

[0073] In some embodiments, control messages instruct the MCS based on a table defined for the Enhanced Mobile Broadband (eMBB) PDSCH.

[0074] In some embodiments, control messages instruct the MCS based on tables or table entries specifically defined for PDSCH.

[0075] In some embodiments, the method / wireless device / computer program code further includes obtaining (YY330) Physical Resource Block (PRB) allocations based at least in part on the determined TBS.

[0076] Certain embodiments of this disclosure may provide one or more technical advantages. For example, some embodiments allow a wireless device to determine the transport block size based on a modulation and coding scheme and a scaling factor indicated in a control message from a network node. In this way, the transport block size can be adjusted to enhance the performance of the PDSCH. As another example, some embodiments include determining an intermediate number of information bits based at least on the modulation and coding scheme and the scaling factor. Thus, the transport block size can be adjusted by adjusting the intermediate value considered in the determination of the transport block size. As yet another example, some embodiments include indicating an MCS with lower spectral efficiency than a normal MCS in the control message. For example, the indicated MCS may be based on a table defined for enhanced mobile broadband PDSCH, or on a table or table entry specifically defined for PDSCH. By providing a lower spectral efficiency MCS, the transport block size can be adjusted to enhance the performance of the PDSCH. Other advantages may be readily apparent to those skilled in the art. Some embodiments may not have the advantages described above, or may have some or all of the advantages described above. Attached Figure Description

[0077] To gain a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description in conjunction with the accompanying drawings, in which:

[0078] Image QQ1 An example wireless network according to some embodiments is illustrated;

[0079] Image QQ2 An example user equipment according to certain embodiments is illustrated;

[0080] Image QQ3 The illustration depicts an example virtualization environment according to certain embodiments;

[0081] Image QQ4 The illustration shows an example telecommunications network connected to a host computer via an intermediate network according to certain embodiments.

[0082] Image QQ5 The illustration shows an example host computer communicating with a user equipment via a base station through a partial wireless connection, according to some embodiments;

[0083] Image QQ6 This is a flowchart illustrating an example method implemented in a communication system according to certain embodiments;

[0084] Image QQ7 This is a flowchart illustrating a second example method implemented in a communication system according to certain embodiments;

[0085] Image QQ8 This is a flowchart illustrating a third method implemented in a communication system according to certain embodiments;

[0086] Image QQ9 This is a flowchart illustrating a fourth method implemented in a communication system according to certain embodiments;

[0087] Figure VV0 The illustration shows example methods performed by network nodes according to certain embodiments;

[0088] Figure VV1 The illustration depicts example methods performed by a wireless device, such as a user equipment, according to certain embodiments;

[0089] Image WW The illustration shows a schematic block diagram of a device in a wireless network according to certain embodiments;

[0090] Figure YY1 The illustration depicts a second example method performed by a network node according to certain embodiments;

[0091] Figure YY2 The illustration depicts a third example method performed by a network node according to certain embodiments;

[0092] Figure YY3 The illustration depicts a second example method performed by a wireless device according to certain embodiments; and

[0093] Figure YY4 The illustration depicts a third example method performed by a wireless device according to certain embodiments. Detailed Implementation

[0094] Some embodiments of the ideas contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are contained within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0095] Certain embodiments of this disclosure may be provided based on section 5.1.3 of 3GPP TS 38.214 V15.0.0, as follows:

[0096] 5.1.3 Determining the Modulation Order, Target Code Rate, and Transport Block Size

[0097] To determine the modulation order, target code rate, and (one or more) transport block sizes in the physical downlink shared channel, the UE should first...

[0098] - Read the 5-bit "Modulation and Coding Scheme" field from the DCI (I MCS The modulation order (Q) is determined based on the procedure defined in sub-clause 5.1.3.1. m ) and target bit rate (R).

[0099] And secondly

[0100] - The number of layers the UE should use (ν), and the total number of PRBs allocated before rate matching (n) PRB The transport block size is determined based on the procedure defined in sub-clause 5.1.3.2.

[0101] If the effective channel code rate is higher than 0.95, the UE can skip decoding of the transport block in the initial transmission. The effective channel code rate is defined as the number of downlink information bits (including CRC bits) divided by the number of physical channel bits on the PDSCH. If the UE skips decoding, the physical layer indicates to the higher layers that the transport block has not been successfully decoded.

[0102] For PDSCH assigned by PDCCH using DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI.

[0103] If the higher-level parameter MCS-Table-PDSCH is not set to '256QAM', then:

[0104] -UE should use I MCS The modulation order (Q) used in the physical downlink shared channel is determined using Table 5.1.3.1-1. m ) and target bit rate (R).

[0105] otherwise

[0106] -UE should use I MCS The modulation order (Q) used in the physical downlink shared channel is determined using Table 5.1.3.1-2. m ) and target bit rate (R).

[0107] Finish

[0108] Table 5.1.3.1-1: MCS Index Table 1 for PDSCH

[0109]

[0110] Table 5.1.3.1-2: MCS Index Table 2 of PDSCH

[0111]

[0112]

[0113] For a PDSCH assigned by a PDCCH using DCI format 1_0 / 1_1 with a CRC scrambled by C-RNTI, if the higher-layer parameter MCS-Table-PDSCH is set to the configured '256QAM' and 0≤I MCS≤27, or the higher-level parameter MCS-Table-PDSCH is not set to the configured '256QAM' and 0≤I MCS If the value is ≤28, the UE should first determine the TBS as specified below:

[0114] 1) The UE should first determine the number of REs (N) within the time slot. RE ).

[0115] -UE first passes To determine the number of REs (N') allocated to PDSCH within the PRB. RE ),in It is the number of subcarriers in the frequency domain within a physical resource block. It is the number of scheduled OFDM symbols in the time slot. This includes the number of REs per PRB used for DM-RS during the scheduling duration of the DM-RSCDM group overhead, as indicated by DCI format 1_0 / 1_1, and This is the overhead configured by the higher-level parameter Xoh-PDSCH. If Xoh-PDSCH is not configured (a value from 0, 6, 12, or 18), Xoh-PDSCH is set to 0.

[0116] - The UE determines the quantization quantity of REs allocated for PDSCH within the PRB using Table 5.1.3.2-1.

[0117] Table 5.1.3.2-1: Quantization quantity of REs allocated for PDSCH within the PRB

[0118]

[0119] -UE passed To determine the total number (N) of REs allocated to PDSCH. RE ), where n PRB This is the total number of PRBs allocated to the UE.

[0120] 2) Through N info =N RE *R*Q m *υ is used to obtain the median number (N) of the information bits. info ).

[0121] If N info ≤3824

[0122] Then step 3 is used as the next step determined by TBS.

[0123] otherwise

[0124] Use step 4 as the next step determined by TBS.

[0125] Finish

[0126] 3) When N info When ≤3824, TBS is determined as follows:

[0127] - The intermediate number of the quantization of information bits in

[0128] - Use Table 5.1.3.2-2 to find values ​​not less than N' info The closest TBS.

[0129] Table 5.1.3.2-2: For N info ≤3824 TBS

[0130] index TBS index TBS index TBS index TBS 1 24 31 336 61 1288 91 3624 2 32 32 352 62 1320 92 3752 3 40 33 368 63 1352 93 3824 4 48 34 384 64 1416 5 56 35 408 65 1480 6 64 36 432 66 1544 7 72 37 456 67 1608 8 80 38 480 68 1672 9 88 39 504 69 1736 10 96 40 528 70 1800 11 104 41 552 71 1864 12 112 42 576 72 1928 13 120 43 608 73 2024 14 128 44 640 74 2088 15 136 45 672 75 2152 16 144 46 704 76 2216 17 152 47 736 77 2280 18 160 48 768 78 2408 19 168 49 808 79 2472 20 176 50 848 80 2536 21 184 51 888 81 2600 22 192 52 928 82 2664 23 208 53 984 83 2728 24 224 54 1032 84 2792 25 240 55 1064 85 2856 26 256 56 1128 86 2976 27 272 57 1160 87 3104 28 288 58 1192 88 3240 29 304 59 1224 89 3368 30 320 60 1256 90 3496

[0131] 4) When N info When the value is greater than 3824, TBS is determined as follows.

[0132] - The intermediate number of the quantization of information bits in And it breaks the tie in the rounding function toward the next largest integer.

[0133] -If R≤1 / 4

[0134] in

[0135] otherwise

[0136] If N' info >8424

[0137] in

[0138] otherwise

[0139]

[0140] Finish

[0141] Finish

[0142] Otherwise, if the higher-level parameter MCS-Table-PDSCH is set to the configured '256QAM' and 28≤I MCS ≤31,

[0143] -Assuming TBS is based on the use of 0≤I MCS The DCI transmitted in the latest PDCCH of the same transport block ≤27 is determined. If 0≤I is not used... MCSThe PDCCH for the same transport block ≤27, and if the initial PDSCH for the same transport block is semi-persistently scheduled, then the TBS should be determined based on the most recent semi-persistently scheduled PDCCH.

[0144] otherwise

[0145] -Assuming TBS is based on the use of 0≤I MCS The DCI transmitted in the latest PDCCH of the same transport block ≤28 is determined. If 0≤I is not used... MCS The PDCCH for the same transport block is ≤28, and if the initial PDSCH for the same transport block is semi-persistently scheduled, the TBS should be determined based on the most recent semi-persistently scheduled PDCCH.

[0146] The TBS identified above, as well as the NDI and HARQ process IDs signaled on the PDCCH, should be reported to higher levels.

[0147] As shown above, Section 5.1.3 provides certain methods for calculating TBS. Some embodiments disclosed herein may be described or implemented as modifications and / or additions to Section 5.1.3. For example, in the first set of embodiments described below, Section 5.1.3 may be modified to change how TBS is calculated to allow for adjustment, thereby providing a lower bitrate, for example, by providing a scaling factor and / or modifying one or more intermediate values. As another example, the second set of embodiments may modify Section 5.1.3 to allow for the utilization of lower MCS values ​​to provide a lower bitrate, for example, by providing a new entry in an existing MCS table or by providing an additional table with lower MCS values. As yet another example, some embodiments may modify Section 5.1.3 to improve reliability by allowing repetition of time and / or frequency, or to take into account the use of inflated TBS when determining PRB allocation. While some embodiments may be described as modifications to certain parts of the above standard, other embodiments do not need to be based on that standard.

[0148] First set of embodiments: Providing a lower bit rate through adjustments to the TBS determination process.

[0149] The first set of embodiments provides a method for broadcasting PDSCH at a lower coding rate by adjusting the transport block size (TBS) determination process.

[0150] In some embodiments, a slightly different TBS determination procedure is specified for broadcast PDSCHs, based on the unicast TBS determination procedure. That is, the unicast TBS determination procedure applies when a PDSCH is assigned with a PDCCH scrambled with a Cyclic Redundancy Check (CRC) scrambled by C-RNTI, TC-RNTI, or CS-RNTI. The modified procedure applies when a PDSCH is assigned with a PDCCH scrambled with a CRC scrambled by SI-RNTI, RA-RNTI, or P-RNTI. C-RNTI, TC-RNTI, and CS-RNTI refer to Radio Network Temporary Identifiers (RNTIs), specifically Cell-RNTI, Temporary Cell-RNTI, and Configured Scheduling-RNTI, respectively. SI-RNTI, RA-RNTI, and P-RNTI refer to System Information-RNTI, Random Access-RNTI, and Paging-RNTI, respectively.

[0151] The following three methods are based on Section 5.1.3 of 3GPP TS38.214V15.0.0.

[0152] Method A-1. Using scaling factors in intermediate variables of the TBS determination process. α ( α ﹤1)。

[0153] • In one example, the number N' of resource elements allocated for PDSCH within the PRB was scaled. RE .

[0154] • In another example, the scaling factor n PRB , where n PRB This is the total number of PRBs allocated to the UE. Therefore: N RE =min(156, N′) RE )×α×n PRE .

[0155] • In yet another example, the median number (N) of the scaled information bits info Therefore: N info =α*N RE *R*Q m *v

[0156] As shown in the second set of embodiments below, one MCS bit can be saved because only Quadrature Phase Shift Keying (QPSK) is relevant for broadcast PDSCH. This unused bit can be used to indicate two distinct α values. For example, if the unused bit = 0, then α = 1 / 2; otherwise, α = 1 / 4. The α values ​​provided above are examples, and other values ​​can be used. For example, in some embodiments, more than one bit can be used to indicate the scaling factor. For example, if two bits are used, the following α values ​​can be used: bit = 11 α = 1, bit = 01 α = 1 / 2, bit = 10 α = 1 / 4, bit = 00 α = 1 / 8. In some embodiments, different α values ​​can also be associated with different RNTI values. In some embodiments, the reserved DCI bit can be used to select an appropriate α value. Some embodiments configure one or more α values ​​for the UE (and in the case of more than one value, use one or more bits(s) in the DCI to select one of the multiple values).

[0157] Method A-2. In N' RE Using large overhead values ​​in calculations

[0158] current, This is the overhead configured by the higher-level parameter Xoh-PDSCH. If Xoh-PDSCH is not configured (a value from 0, 6, 12, or 18), Xoh-PDSCH is set to 0.

[0159] For broadcast PDSCH, large The value can be used to obtain a lower TBS, thus resulting in a lower bitrate. In one example, Xoh-PDSCH is set to the highest value that RRC can configurable; that is, if the PDSCH carries a broadcast message, Xoh-PDSCH is set to 18. In another example, Xoh-PDSCH is set to a predefined value that is not in the set of values ​​that can be configured by RRC. For example, Xoh-PDSCH is predefined (configured) as a value selected from the set {24, 36, 48, 60, 72} of broadcast PDSCHs.

[0160] As shown in the second set of embodiments below, one MCS bit can be saved because only QPSK is relevant to the broadcast PDSCH. This unused bit can be used to indicate two different Value. For example, if the unused bit = 0, then otherwise, Different The value can also be associated with different RNTI values. In some embodiments, the reserved DCI bits can be used to select the appropriate value.

[0161] Method A-3 Nonlinear TBS modification

[0162] • In some embodiments, the # of the PRB used in TBS calculation is the # of the assigned PRB modulus X.

[0163] For example, consider X = 5. For RAR, we can allocate 3 PRBs, 8 PRBs, or 13 PRBs, which will all give the same TBS.

[0164] • In some embodiments, this can provide an advantage for broadcast PDSCH by selecting an appropriate parameter X in the specification.

[0165] • Considering the need to avoid limiting the maximum SITBS, System Information (SI) may still present some challenges.

[0166] Additionally, bits in the DCI (e.g., bits in the MCS field, since broadcast PDSCH is limited to QPSK) or another field in the DCI can be used to select one from a plurality of predefined / configured X values. As in other embodiments discussed above, these embodiments may also depend on the RNTI; for example, in some embodiments, the method applies only to a particular broadcast RNTI, such as P-RNTI and RA-RNTI. The RNTI can also be used to select an appropriate X value.

[0167] Method A-4 Enhanced TBS determination

[0168] • In some embodiments, all 28 spectral efficiencies allowed in the 64QAMMCS table can support TBS determination for P / RA / SI, even if the modulation scheme used for the corresponding transport block is restricted to QPSK. That is, the device uses Qm corresponding to I_MCS for TBS determination, and the modulation order applied to the transport block is given by Qm' = min(Qm,2).

[0169] Furthermore, flexible resource block allocation can support TBS reads via non-linear PRB mapping. For example, for the # of the allocated PRB, the TBS is determined via the # of the allocated PRB modulo X.

[0170] For example, if X = 6 => 1 PRB, then 7 PRBs and 13 PRBs will use the same TBS.

[0171] Second set of embodiments: Providing MCS levels with lower spectral efficiency

[0172] The second set of embodiments provides a method for broadcasting a PDSCH with a low coding rate by providing an MCS level with lower spectral efficiency.

[0173] In some embodiments, different MCS tables can be used to broadcast PDSCH. Two methods are given below based on Section 5.1.3 of 3GPP TS 38.214 V15.0.1.

[0174] Method B-1. Use an MCS that includes the lower MCS entry currently defined for Enhanced Mobile Broadband (eMBB) PDSCH. surface.

[0175] Currently, it is desired to define a new MCS table for Rel-15NRURLLC in order to achieve a BLER target lower than that of eMBB, for example, to achieve a BLER target of 10. -5 Instead of 10 -1 The URLLCPDSCHMCS table is expected to contain MCS values ​​lower than MCS0 in the eMBBMCS table.

[0176] In some embodiments, one method specifies that the broadcast PDSCH uses MCS entries from the NURURLLCMCS table. Additionally, it may specify that the broadcast PDSCH uses MCS entries from the NURURLLCMCS table for lower BLER targets.

[0177] As an example, the URLLCMCS table has been provided below. The broadcast PDSCH can be specified to use the MCS entries from the NRURLLCMCS table below for BLER target = 10. -5 .

[0178] Additionally, bits in the DCI (e.g., bits in the MCS field, since broadcast PDSCH is limited to QPSK) or another field in the DCI can be used to select one MCS table from multiple MCS tables. Some embodiments may also depend on the RNTI; for example, in some embodiments, the method is applied only to a specific broadcast RNTI, such as P-RNTI and RA-RNTI. The RNTI can also be used to select the appropriate MCS table.

[0179]

[0180] In some embodiments, the broadcast PDSCH may be specified to use MCS entries corresponding to a portion of the table. As an example, in the table above, the broadcast PDSCH may use MCS entries corresponding to the spectral efficiencies shown underlined.

[0181] Method B-2. Specifically construct the MCS table for broadcast PDSCH.

[0182] In some embodiments, the MCS table, specifically designed for broadcast PDSCH, may contain only QPSK and have a lower bitrate than that available for the eMBB payload. An example is shown below.

[0183] As can be observed, only 16 entries are needed in the MCS table for the eMBB payload, instead of the previous 32 entries. This saves one bit in the DCI's MCS field. The saved bit can be used to provide additional information to the UE.

[0184] Alternatively, this bit can be used to indicate whether to use a table specifically designed for broadcast PDSCH or the default MCS table. As mentioned above, for broadcast PDSCH, only QPSK is typically supported.

[0185]

[0186] Third and fourth sets of embodiments: Improving reliability through repetition in the time domain

[0187] In the third set of embodiments, slot aggregation is used to broadcast a PDSCH similar to a normal PDSCH. Slot aggregation related information can be provided in a cell-specific RRC message, or by using some of the unused / reserved bits in the corresponding DCI.

[0188] In the fourth set of embodiments, time-domain repetition may be introduced. In some embodiments, time-domain repetition may be indicated in the DCI to broadcast the PDSCH.

[0189] In some embodiments, only PDSCH is repeated; for example, only one PDCCH is used to schedule all PDSCH repetitions, where the same redundant version (RV) or some fixed RV pattern may be assumed in all repetitions.

[0190] In some embodiments, a PDSCH repetition bit PDSCHrep may be introduced in the corresponding DCI to indicate the repetition period, wherein the same PDSCH frequency time position may be assumed in each repetition period.

[0191] For example, using two bits, repetition can be defined as follows:

[0192] 00->No repeats

[0193] 01->Repeat with a period of 20ms

[0194] 10 -> Repeats at a period of 40ms

[0195] 11->Repeat with an 80ms period

[0196] In some embodiments, both the PDCCH and PDSCH are repeated, and some unused bits are used for the repetition ID in the DCI so that the UE can perform soft assembly. In some embodiments, the repetition ID can be a single parameter. For example, two bits are used for the repetition ID:

[0197] 00->First Transmission

[0198] 01->Second Transmission

[0199] 10->Third Transmission

[0200] 11->Fourth Transmission

[0201] In some embodiments, the duplicate ID can be bound to other known parameters, such as the RV mode in DCI, where RV0 means the first transmission, RV3 means the last transmission, or a predefined order.

[0202] Fifth set of embodiments: Improving reliability through repetition in the frequency domain

[0203] In the fifth set of embodiments, frequency domain repetition can be introduced to broadcast the PDSCH by indicating it in the DCI. For example, the techniques described above in the third and fourth sets of embodiments regarding time domain repetition can be applied here. In particular, the frequency domain can be considered instead of the time domain, and the required or predefined signaling can be, for example, frequency domain position and RV mode.

[0204] Sixth example: Obtaining a larger PRB allocation using an expanded TBS

[0205] According to the embodiments in the sixth set of examples, a larger number of PRBs can be scheduled to carry a payload size larger than the actual size of the transport block, and the larger payload contains the actual (desired) information bits and padding bits. In this way, gain will be provided from frequency diversity when more PRBs are used in the frequency domain (and in DL, more RBs generally also mean more power). For the special case of random access Msg2, the gNB may include multiple RARs (Random Access Responses). If the gNB has only one real RAR to transmit, it may include one or more virtual RARs to inflate the TBS size.

[0206] For all the above embodiments, the method can be applied to, but is not limited to, broadcast PDSCH. That is, the method can also be used for normal PDSCH in some scenarios where additional PDSCH performance enhancements are required.

[0207] Image QQ1 Wireless network according to some embodiments.

[0208] Although the subjects described herein can be implemented using any suitable components in any appropriate type of system, the embodiments disclosed herein are for wireless networks (such as...). Image QQ1 The example wireless network shown in the diagram is illustrated. For simplicity, Image QQ1The wireless network depicted only includes network QQ106, network nodes QQ160 and QQ160b, and WD QQ110, QQ110b, and QQ110c. In practice, the wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Among the illustrated components, network node QQ160 and wireless device (WD) QQ110 are depicted in additional detail. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0209] Wireless networks may include or interface with any type of communications, telecommunications, data, cellular and / or radio network or other similar system. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of the wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as the IEEE 802.11 standard; and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0210] Network QQ106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0211] Network nodes QQ160 and WDQQ110 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In various embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that facilitate or participate in communication of data and / or signals, whether via wired or wireless connections.

[0212] As used herein, a network node is a device capable of, configured, positioned, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NRNode Bs (gNBs)). Base stations may be classified based on the coverage they provide (or, in other words, their transmit power levels) and may then be referred to as femtobases, picobases, microbases, or macrobases. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) portions of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as a radio device with an integrated antenna. A portion of a distributed radio base station may also be referred to as a node in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (such as MSRBS), network controllers (such as Radio Network Controller (RNC) or Base Station Controller (BSC)), Base Transceiver Stations (BTS), transport points, transport nodes, multi-cell / multicast coordination entities (MCE), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, location nodes (e.g., E-SMLC), and / or MDTs. As another example, a network node can be a virtual network node as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) capable of, configured, arranged, and / or operable to enable and / or provide access to a wireless network for wireless devices or to provide some service to wireless devices already connected to the wireless network.

[0213] exist Image QQ1 In the network node QQ160, there are processing circuitry QQ170, device-readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power supply QQ186, power circuitry QQ187, and antenna QQ162. Although in Image QQ1The network node QQ160 illustrated in the example wireless network may represent an apparatus including the illustrated combination of hardware components, but other embodiments may include network nodes with different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, although the components of network node QQ160 are depicted as a single box within a larger box or nested within multiple boxes, in practice, a network node may include multiple different physical components that make up a single illustrated component (e.g., apparatus-readable medium QQ180 may include multiple separate hard disk drives and multiple RAM modules).

[0214] Similarly, network node QQ160 may consist of multiple physically separate components (e.g., NodeB components and RNC components, as well as BTS components and BSC components, etc.), each of which may have their own corresponding components. In some cases where network node QQ160 includes multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such cases, each unique NodeB and RNC pair may be considered a single, separate network node in some instances. In some embodiments, network node QQ160 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable storage media QQ180 for different RATs), and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of various illustrated components for integrating different wireless technologies (such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) into network node QQ160. These wireless technologies can be integrated into the same or different chips or chipsets and other components within the QQ160 network node.

[0215] The processing circuit QQ170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being provided by a network node. These operations performed by the processing circuit QQ170 may include, for example, processing the information obtained by the processing circuit QQ170 by converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and determining the result of said processing.

[0216] The processing circuitry QQ170 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of coded logic, software, and / or hardware operable alone or in combination with other network node QQ160 components (such as device-readable medium QQ180) to provide the functionality of network node QQ160. For example, the processing circuitry QQ170 may execute instructions stored in memory within the device-readable medium QQ180 or within the processing circuitry QQ170. Such functionality may include any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry QQ170 may include a system-on-a-chip (SoC).

[0217] In some embodiments, the processing circuit QQ170 may include one or more of a radio frequency (RF) transceiver circuit QQ172 and a baseband processing circuit QQ174. In some embodiments, the RF transceiver circuit QQ172 and the baseband processing circuit QQ174 may be on separate chips (or chipsets), boards, or units (such as radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuit QQ172 and the baseband processing circuit QQ174 may be on the same chip or chipset, board, or unit.

[0218] In some embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be executed by processing circuitry QQ170 executing instructions stored in memory or on device-readable medium QQ180 within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 (e.g., hardwired) without executing instructions stored on separate or discrete device-readable media. In any of those embodiments, processing circuitry QQ170 may be configured to perform the described functionality regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and / or generally by end users and wireless networks.

[0219] Device-readable medium QQ180 may include any form of volatile or non-volatile computer-readable storage, including but not limited to permanent storage devices, solid-state storage, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by processing circuitry QQ170. Device-readable medium QQ180 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry QQ170 and usable by network node QQ160. Device-readable medium QQ180 may be used to store any calculations performed by processing circuitry QQ170 and / or any data received via interface QQ190. In some embodiments, the processing circuitry QQ170 and the device-readable medium QQ180 may be considered integrated.

[0220] Interface QQ190 is used in wired or wireless communication of signaling and / or data between network node QQ160, network QQ106, and / or WDQQ110. As illustrated, interface QQ190 includes one or more ports / terminals QQ194 for transmitting and receiving data to and from network QQ106, for example, via a wired connection. Interface QQ190 also includes radio front-end circuitry QQ192, which may be coupled to antenna QQ162 or, in some embodiments, is part of antenna QQ162. Radio front-end circuitry QQ192 includes a filter QQ198 and an amplifier QQ196. Radio front-end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front-end circuitry may be configured to modulate the signal transmitted between antenna QQ162 and processing circuitry QQ170. Radio front-end circuitry QQ192 may receive digital data to be transmitted wirelessly to other network nodes or WDs. The radio front-end circuit QQ192 can use a combination of filter QQ198 and / or amplifier QQ196 to convert digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals can then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 can collect radio signals, which are then converted into digital data by the radio front-end circuit QQ192. The digital data can be passed to processing circuit QQ170. In other embodiments, the interface may include different components and / or different combinations of components.

[0221] In some alternative embodiments, network node QQ160 may not include a separate radio front-end circuit QQ192; instead, processing circuitry QQ170 may include the radio front-end circuitry and may be connected to antenna QQ162 without a separate radio front-end circuitry QQ192. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ172 may be considered part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front-end circuitry QQ192, and RF transceiver circuitry QQ172 as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

[0222] Antenna QQ162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna QQ162 may be coupled to radio front-end circuitry QQ190 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna QQ162 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals from devices within a specific area, and planar antennas may be line-of-sight antennas used to transmit / receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna QQ162 may be separate from network node QQ160 and may be connected to network node QQ160 via an interface or port.

[0223] Antenna QQ162, interface QQ190, and / or processing circuitry QQ170 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from a wireless device, another network node, and / or any other network device. Similarly, antenna QQ162, interface QQ190, and / or processing circuitry QQ170 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to a wireless device, another network node, and / or any other network device.

[0224] Power circuit QQ187 may include or be coupled to power management circuitry and is configured to supply power to the components of network node QQ160 for performing the functionality described herein. Power circuit QQ187 may receive power from power source QQ186. Power source QQ186 and / or power circuit QQ187 may be configured to supply power to the respective components of network node QQ160 in a manner suitable for each component (e.g., at the voltage and current levels required by each respective component). Power source QQ186 may be included in or outside power circuit QQ187 and / or network node QQ160. For example, network node QQ160 may be connected to an external power source (e.g., an electrical outlet) via input circuitry or an interface (such as a cable), thereby supplying power to power circuit QQ187. As another example, power source QQ186 may include a power source in the form of a battery or battery pack, which is connected to or integrated into power circuit QQ187. The battery can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0225] Alternative embodiments of the network node QQ160 may include, in addition to Image QQ1 Additional components beyond those shown may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the topics described herein. For example, the network node QQ160 may include a user interface device to allow information to be input into and output from the network node QQ160. This allows users to perform diagnostic, maintenance, repair, and other management functions on the network node QQ160.

[0226] As used herein, a wireless device (WD) means a means capable of, configured to, arranged to, and / or operable to wirelessly communicate with network nodes and / or other wireless devices. Unless otherwise indicated, the term WD may be used interchangeably with User Equipment (UE) herein. Wireless communication may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information over the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to the network according to a predetermined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), and wireless terminal devices mounted on vehicles. A WD may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case, may be referred to as a D2D communication device. As yet another specific example, in the context of the Internet of Things (IoT), a WD may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this context, a WD can be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a WD can be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery or household or personal appliances (e.g., refrigerators, televisions, etc.), and personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, a WD can refer to a vehicle or other equipment capable of monitoring and / or reporting its operational status or other functions associated with its operation. A WD as described above can represent a wirelessly connected endpoint, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above can be mobile, in which case it may also be referred to as a mobile device or mobile terminal.

[0227] As shown in the figure, the wireless device QQ110 includes an antenna QQ111, an interface QQ114, processing circuitry QQ120, a device-readable medium QQ130, a user interface device QQ132, auxiliary devices QQ134, a power supply QQ136, and a power circuit QQ137. WDQQ110 may include multiple sets of illustrated components for one or more of the different wireless technologies supported by WDQQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMax, or Bluetooth wireless technologies, to name just a few examples. These wireless technologies may be integrated into chips or chipsets that are the same as or different from the other components within WDQQ110.

[0228] Antenna QQ111 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to interface QQ114. In some alternative embodiments, antenna QQ111 may be separate from WDQQ110 and may be connected to WDQQ110 via an interface or port. Antenna QQ111, interface QQ114, and / or processing circuitry QQ120 may be configured to perform any receive or transmit operations described herein as performed by a WD. Any information, data, and / or signals may be received from network nodes and / or another WD. In some embodiments, radio front-end circuitry and / or antenna QQ111 may be considered as an interface.

[0229] As shown in the figure, interface QQ114 includes radio front-end circuitry QQ112 and antenna QQ111. Radio front-end circuitry QQ112 includes one or more filters QQ118 and amplifiers QQ116. Radio front-end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120 and is configured to modulate the signal transmitted between antenna QQ111 and processing circuitry QQ120. Radio front-end circuitry QQ112 may be coupled to or is part of antenna QQ111. In some embodiments, WD QQ110 may not include separate radio front-end circuitry QQ112; instead, processing circuitry QQ120 may include radio front-end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered part of interface QQ114. Radio front-end circuitry QQ112 may receive digital data to be transmitted wirelessly to other network nodes or WD. Radio front-end circuitry QQ112 may use a combination of filters QQ118 and / or amplifiers QQ116 to convert digital data into radio signals with appropriate channel and bandwidth parameters. Radio signals can then be transmitted via antenna QQ111. Similarly, when data is received, antenna QQ111 can collect radio signals, which are then converted into digital data by radio front-end circuitry QQ112. The digital data can be transmitted to processing circuitry QQ120. In other embodiments, the interface may include different components and / or different combinations of components.

[0230] The processing circuitry QQ120 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of coded logic, software, and / or hardware operable alone or in combination with other WDQQ110 components (such as device-readable medium QQ130) to provide WDQQ110 functionality. Such functionality may include any of the various wireless features or benefits discussed herein. For example, the processing circuitry QQ120 may execute instructions stored in the device-readable medium QQ130 or in memory within the processing circuitry QQ120 to provide the functionality disclosed herein.

[0231] As shown in the figure, the processing circuit QQ120 includes one or more of the following: an RF transceiver circuit QQ122, a baseband processing circuit QQ124, and an application processing circuit QQ126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit QQ120 of WDQQ110 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126 may be on a separate chip or chipset. In an alternative embodiment, some or all of the baseband processing circuit QQ124 and the application processing circuit QQ126 may be combined into a single chip or chipset, and the RF transceiver circuit QQ122 may be on a separate chip or chipset. In another alternative embodiment, some or all of the RF transceiver circuit QQ122 and the baseband processing circuit QQ124 may be on the same chip or chipset, and the application processing circuit QQ126 may be on a separate chip or chipset. In other alternative embodiments, some or all of the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126 may be combined on the same chip or chipset. In some embodiments, the RF transceiver circuit QQ122 may be part of the interface QQ114. The RF transceiver circuit QQ122 can regulate the RF signal of the processing circuit QQ120.

[0232] In some embodiments, some or all of the functionality described herein as being performed by WD may be provided by processing circuitry QQ120 executing instructions stored on device-readable medium QQ130, which in some embodiments may be computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120 (e.g., hardwired) without executing instructions stored on separate or discrete device-readable storage media. In any of those particular embodiments, processing circuitry QQ120 may be configured to perform the described functionality regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or other components of WDQQ110, but are enjoyed by WDQQ110 as a whole, and / or generally by the end user and wireless network.

[0233] The processing circuit QQ120 can be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. Such operations performed by the processing circuit QQ120 may include, for example, processing the information obtained by the processing circuit QQ120 by converting the acquired information into other information, comparing the acquired or converted information with information stored in WDQQ110, and / or performing one or more operations based on the acquired or converted information, and determining the result of said processing.

[0234] Device-readable medium QQ130 may be operable to store computer programs, software, applications including logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry QQ120. Device-readable medium QQ130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., CD or DVD) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory means that stores information, data, and / or instructions usable by processing circuitry QQ120. In some embodiments, processing circuitry QQ120 and device-readable medium QQ130 may be considered integrated.

[0235] User interface device QQ132 provides components that consider human user interaction with WDQQ110. Such interaction can take many forms, such as visual, auditory, and tactile. User interface device QQ132 is operable to produce output to the user and allow the user to provide input to WDQQ110. The type of interaction may vary depending on the type of user interface device QQ132 installed in WDQQ110. For example, if WDQQ110 is a smartphone, interaction may be via a touchscreen; if WDQQ110 is a smart meter, interaction may be via a screen providing usage information (e.g., gallons used) or a speaker providing audible alarms (e.g., if smoke is detected). User interface device QQ132 may include input interfaces, means, and circuitry, as well as output interfaces, means, and circuitry. User interface device QQ132 is configured to allow information input to WDQQ110 and is connected to processing circuitry QQ120 to allow processing of the input information. User interface device QQ132 may include, for example, a microphone, proximity sensor or other sensor, buttons / buttons, touch display, one or more cameras, USB port, or other input circuitry. User interface device QQ132 is also configured to allow information output from WDQQ110 and to allow processing circuitry QQ120 to output information from WDQQ110. User interface device QQ132 may include, for example, a speaker, display, vibration circuitry, USB port, headphone jack, or other output circuitry. Using one or more input and output interfaces, devices, and circuitry of user interface device QQ132, WDQQ110 can communicate with end users and / or wireless networks, allowing them to benefit from the functionality described herein.

[0236] The auxiliary device QQ134 is operable to provide more specific functionality that is not typically performed by the WD. This may include dedicated sensors for measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and type of components of the auxiliary device QQ134 may vary depending on the embodiment and / or circumstances.

[0237] In some embodiments, the power supply QQ136 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a power battery. The WDQQ110 may also include power circuitry QQ137 for delivering power from the power supply QQ136 to various portions of the WDQQ110 that require power from the power supply QQ136 to perform any functionality described or indicated herein. In some embodiments, power circuitry QQ137 may include power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in this case, the WDQQ110 may be connected to an external power source (e.g., an electrical outlet) via input circuitry or an interface (e.g., a power cable). In some embodiments, power circuitry QQ137 may also be operable to deliver power from an external power source to the power supply QQ136. This can be used, for example, for charging the power supply QQ136. Power circuitry QQ137 may perform any formatting, conversion, or other modifications on the power from the power supply QQ136 to suit the power for the respective components of the WD QQ110 to which it supplies power.

[0238] Image QQ2 User equipment according to some embodiments

[0239] Image QQ2 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device intended to be sold to or operated by a human user, but the device may not or may not initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device not intended to be sold to or operated by an end user, but which may be associated with or operated for the benefit of a user (e.g., a smart meter). UEQQ2200 can be any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs, Machine-Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. Image QQ2 The UEQQ200 illustrated is an example of a WD configured for communication according to one or more communication standards (such as 3GPP's GSM, UMTS, LTE, and / or 5G standards) issued by the 3rd Generation Partnership Project (3GPP). As previously mentioned, the terms WD and UE can be used interchangeably. Therefore, although... Image QQ2 It is a UE, but the components discussed in this article also apply to WD, and vice versa.

[0240] exist Image QQ2In this UE QQ200, processing circuitry QQ201 is operatively coupled to an input / output interface QQ205, a radio frequency (RF) interface QQ209, a network connectivity interface QQ211, a memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and a storage medium QQ221, a communication subsystem QQ231, a power supply QQ233, and / or any other components or any combination thereof. Storage medium QQ221 includes an operating system QQ223, application programs QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Some UEs may utilize... Image QQ2 All components shown, or only a subset of components, can be used. The degree of integration between components can vary from one UE to another. Additionally, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0241] exist Image QQ2 In this embodiment, the processing circuit QQ201 can be configured to process computer instructions and data. The processing circuit QQ201 can be configured to implement any sequential state machine that operates to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic along with appropriate firmware; one or more stored programs; a general-purpose processor (such as a microprocessor or digital signal processor (DSP)) along with appropriate software; or any combination of the foregoing. For example, the processing circuit QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for computer use.

[0242] In the depicted embodiments, the input / output interface QQ205 can be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UEQQ200 can be configured to use an output device via the input / output interface QQ205. The output device can use an interface port of the same type as the input device. For example, a USB port can be used to provide input to and output from the UEQQ200. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UEQQ200 can be configured to use an input device via the input / output interface QQ205 to allow a user to capture information into the UEQQ200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital camcorder, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. Sensors can be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, another similar sensor, or any combination thereof. For example, input devices can be accelerometers, magnetometers, digital cameras, microphones, and light sensors.

[0243] exist Image QQ2 In this configuration, the RF interface QQ209 can be configured to provide a communication interface to RF components (such as transmitters, receivers, and antennas). The network connectivity interface QQ211 can be configured to provide a communication interface to the network QQ243a. The network QQ243a may include wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, the network QQ243a may include a Wi-Fi network. The network connectivity interface QQ211 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connectivity interface QQ211 can implement receiver and transmitter functionality suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functionality may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0244] RAMQQ217 can be configured to interface with processing circuitry QQ201 via bus QQ202 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROMQQ219 can be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 can be configured to store invariant low-level system code or data for basic system functions (such as basic input and output (I / O), startup, or reception of keystrokes from a keyboard) stored in non-volatile memory. Storage medium QQ221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable magnetic tape, or flash memory drive. In one example, storage medium QQ221 can be configured to include an operating system QQ223, an application QQ225 (such as a web browser application, a widget or gadget engine, or another application), and a data file QQ227. Storage medium QQ221 can store any of various operating systems or combinations of operating systems for use by UEQQ200.

[0245] Storage medium QQ221 can be configured to include multiple physical drive units, such as a Redundant Array of Independent Disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital multifunction disc (HD-DVD) drive, an internal hard disk drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM / MSDRAM, smart card memory (such as a subscriber identity module or a removable subscriber identity (SIM / RUIM) module), other memory, or any combination thereof. Storage medium QQ221 allows UEQQ200 to access computer-executable instructions, applications, etc., stored on transient or non-transient storage media to unload or upload data. Articles of manufacture (such as an article utilizing a communication system) can be tangibly embodied in storage medium QQ221, which may include device-readable media.

[0246] exist Image QQ2In this embodiment, the processing circuit QQ201 can be configured to communicate with network QQ243b using the communication subsystem QQ231. Networks QQ243a and QQ243b can be the same one or more networks or different one or more networks. The communication subsystem QQ231 can be configured to include one or more transceivers for communicating with network QQ243b. For example, the communication subsystem QQ231 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (such as another WD, UE, or radio access network (RAN) base station) capable of wireless communication according to one or more communication protocols (such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include a transmitter QQ233 and / or a receiver QQ235 to respectively implement transmitter or receiver functionality suitable for the RAN link (e.g., frequency allocation, etc.). Additionally, the transmitter QQ233 and receiver QQ235 of each transceiver can share circuit components, software, or firmware, or alternatively, can be implemented separately.

[0247] In the illustrated embodiment, the communication functions of the communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. For example, the communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network QQ243b may include wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network QQ243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UEQQ200.

[0248] The features, benefits, and / or functions described herein may be implemented in one of the components of UEQQ200, or divided across multiple components of UEQQ200. Alternatively, the features, benefits, and / or functions described herein may be implemented using any combination of hardware, software, or firmware. In one example, the communication subsystem QQ231 may be configured to include any of the components described herein. Additionally, the processing circuitry QQ201 may be configured to communicate with any of these components via bus QQ202. In another example, any of these components may be represented by program instructions stored in memory that, when executed by the processing circuitry QQ201, perform the corresponding functions described herein. In another example, the functionality of any such component may be divided between the processing circuitry QQ201 and the communication subsystem QQ231. In yet another example, the non-computationally intensive functions of any such component may be implemented using software or firmware, and the computationally intensive functions may be implemented using hardware.

[0249] Image QQ3 Virtualization environment according to some embodiments

[0250] Image QQ3 This is a schematic block diagram illustrating a virtualized environment QQ300 in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating virtual versions of devices or apparatuses, which may include virtualized hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or apparatuses (e.g., UEs, wireless devices, or any other type of communication apparatus) or components thereof, and involves at least a portion of their functionality being implemented as an implementation of one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0251] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines, which are implemented in one or more virtual environments QQ300 hosted by one or more hardware nodes in hardware node QQ330. Additionally, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may be fully virtualized.

[0252] These functionalities can be implemented by one or more applications QQ320 (alternatively referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.) that operate to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications QQ320 run in a virtualization environment QQ300, which provides hardware QQ330 including processing circuitry QQ360 and memory QQ390. The memory QQ390 contains instructions QQ395 executable by the processing circuitry QQ360, thereby enabling the applications QQ320 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0253] The virtualization environment QQ300 includes general-purpose or special-purpose network hardware devices QQ330. Device QQ330 includes an assembly of one or more processors or processing circuitry QQ360. The processors or processing circuitry QQ360 can be commercial off-the-shelf (COTS) processors, specialized application-specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or a special-purpose processor. Each hardware device may include memory QQ390-1, which may be non-permanent memory for temporarily storing software or instructions QQ395 executed by the processing circuitry QQ360. Each hardware device may include one or more network interface controllers (NICs) QQ370 (also called network interface cards), which include physical network interfaces QQ380. Each hardware device may also include a non-transitory, permanent, machine-readable storage medium QQ390-2 in which instructions and / or software QQ395 executable by the processing circuitry QQ360 are stored. Software QQ395 may include any type of software, including software for instantiating one or more virtualization layers QQ350 (also known as hypervisors), software for executing virtual machine QQ340, and software that allows it to perform the functions, features, and / or benefits described in conjunction with some of the embodiments described herein.

[0254] Virtual machine QQ340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by a corresponding virtualization layer QQ350 or a hypervisor. Different embodiments of virtual device QQ320 can be implemented on one or more of virtual machines QQ340, and this implementation can be carried out in different ways.

[0255] During operation, the processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which is sometimes referred to as the Virtual Machine Monitor (VMM). The virtualization layer QQ350 presents a virtual operating platform to the virtual machine QQ340, which appears to be networked hardware.

[0256] like Image QQ3As shown, the hardware QQ330 can be a standalone network node with general or specific components. The hardware QQ330 may include the antenna QQ3225 and may implement some functions via virtualization. Alternatively, the hardware QQ330 may be part of a larger hardware cluster (e.g., in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which also oversees the lifecycle management of the application QQ320.

[0257] Hardware virtualization is sometimes referred to as Network Functions Virtualization (NFV). NFV can be used to integrate many types of network devices onto industry-standard high-capacity server hardware, physical switches, and physical storage devices, which can reside in data centers and customer premises.

[0258] In the context of NFV, a virtual machine QQ340 can be a software implementation of a physical machine that executes programs as if they were running on a physical, non-virtualized machine. Each virtual machine in QQ340, along with the portion of the hardware QQ330 that executes that virtual machine (whether it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine and other virtual machines in QQ340), forms a separate virtual network element (VNE).

[0259] Within the context of NFV, Virtual Network Functions (VNFs) are responsible for handling specific network functions running in one or more virtual machines (QQ340) on top of the hardware networking infrastructure (QQ330), and correspond to... Image QQ3 The application QQ320.

[0260] In some embodiments, one or more radio units QQ3200, each including one or more transmitters QQ3220 and one or more receivers QQ3210, may be coupled to one or more antennas QQ3225. The radio unit QQ3200 may communicate directly with the hardware node QQ330 via one or more suitable network interfaces and may be used in combination with virtual components to provide radio capabilities to the virtual node, such as a radio access node or base station.

[0261] In some embodiments, some signaling may be implemented using a control system QQ3230, which may alternatively be used for communication between hardware node QQ330 and radio unit QQ3200.

[0262] QQ4: A telecommunications network connected to a host computer via an intermediate network according to some embodiments.

[0263] refer to Image QQ4According to an embodiment, the communication system includes a telecommunications network QQ410, such as a 3GPP-type cellular network, which includes an access network QQ411, such as a radio access network, and a core network QQ414. The access network QQ411 includes multiple base stations QQ412a, QQ412b, and QQ412c, such as NBs, eNBs, gNBs, or other types of wireless access points, each base station defining a corresponding coverage area QQ413a, QQ413b, or QQ413c. Each base station QQ412a, QQ412b, or QQ412c can be connected to the core network QQ414 via a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to or be paged by the corresponding base station QQ412c. A second UE QQ492 located in coverage area QQ413a can wirelessly connect to the corresponding base station QQ412a. Although multiple UEs QQ491 and QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or where only one UE is connected to the corresponding base station QQ412.

[0264] Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430, or via optional intermediate network QQ420. Intermediate network QQ420 may be one or more of public, private, or hosted networks; intermediate network QQ420 (if any) may be a backbone network or the Internet; in particular, intermediate network QQ420 may include two or more subnetworks (not shown).

[0265] Image QQ4The communication system as a whole enables connectivity between connected UEs QQ491 and QQ492 and the host computer QQ430. This connectivity can be described as an over-the-top (OTT) connection QQ450. The host computer QQ430 and the connected UEs QQ491 and QQ492 are configured to use access network QQ411, core network QQ414, any intermediate network QQ420, and possibly other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection QQ450. The OTT connection QQ450 can be transparent in the sense that the participating communication devices traversed by the OTT connection QQ450 are unaware of the routes of uplink and downlink communications. For example, it may not be necessary or required to notify the base station QQ412 of the past routes of incoming downlink communications containing data originating from the host computer QQ430 to be forwarded (e.g., handed over) to the connected UE QQ491. Similarly, base station QQ412 does not need to know the future route of outgoing uplink communication from UEQQ491 to host computer QQ430.

[0266] Image QQ5 A host computer that communicates with a user equipment via a base station through a partial wireless connection, according to some embodiments.

[0267] Now refer to Image QQ5 Example implementations of the UE, base station, and host computer discussed in the preceding paragraphs are described. In the communication system QQ500, the host computer QQ510 includes hardware QQ515, which includes a communication interface QQ516 configured to establish and maintain a wired or wireless connection to an interface with different communication devices of the communication system QQ500. The host computer QQ510 also includes processing circuitry QQ518, which may have storage and / or processing capabilities. In particular, the processing circuitry QQ518 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The host computer QQ510 also includes software QQ511, which is stored in or accessible by the host computer QQ510 and executable by the processing circuitry QQ518. The software QQ511 includes a host application QQ512. The host application QQ512 may be operable to provide services to remote users, such as UEQQ530 connected via an OTT connection QQ550 terminated at UEQQ530 and host computer QQ510. When providing services to remote users, the host application QQ512 can provide user data transmitted via OTT connection QQ550.

[0268] The communication system QQ500 also includes a base station QQ520, which is provided in the telecommunications system and includes hardware QQ525 enabling it to communicate with a host computer QQ510 and with a UE QQ530. Hardware QQ525 may include a communication interface QQ526 for establishing and maintaining wired or wireless connections to different communication devices of the communication system QQ500, and for establishing and maintaining at least one connection with the coverage area served by the base station QQ520. Image QQ5 (Not shown in the image) The UE QQ530's wireless connection to the radio interface QQ570 is via the radio interface QQ527. The communication interface QQ526 can be configured to facilitate connection to the host computer QQ510 QQ560. The connection to QQ560 can be direct, or it can be via the core network of the telecommunications system (…). Image QQ5 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware QQ525 of the base station QQ520 also includes processing circuitry QQ528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station QQ520 also has software QQ521 stored internally or accessible via an external connection.

[0269] The communication system QQ500 also includes the previously mentioned UEQQ530. Its hardware QQ535 may include a radio interface QQ537 configured to establish and maintain a radio connection QQ570 with a base station serving the coverage area currently in which the UEQQ530 is located. The hardware QQ535 of the UEQQ530 also includes processing circuitry QQ538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The UE QQ530 also includes software QQ531, which is stored in or accessible to the UEQQ530 and executable by the processing circuitry QQ538. Software QQ531 includes a client application QQ532. The client application QQ532 may be operable to provide services to human or non-human users via the UEQQ530 with the support of a host computer QQ510. In the host computer QQ510, the executing host application QQ512 may communicate with the executing client application QQ532 via an OTT connection QQ550 terminated between the UEQQ530 and the host computer QQ510. In providing services to users, the client application QQ532 can receive request data from the host application QQ512 and provide user data in response to the request data. The OTT connection QQ550 can transmit both request data and user data. The client application QQ532 can interact with the user to generate the user data it provides.

[0270] Notice, Image QQ5The host computer QQ510, base station QQ520, and UEQQ530 shown in the diagram can respectively connect with... Image QQ4 The host computer QQ430, base station QQ412a, QQ412b, QQ412c, and UE QQ491, QQ492 are similar to or identical to each other. That is to say, the internal workings of these entities can be as follows: Image QQ5 As shown, and independently, the surrounding network topology can be Image QQ4 The network topology.

[0271] exist Image QQ5 In this diagram, the OTT connection QQ550 is abstractly depicted to illustrate communication between the host computer QQ510 and the UE QQ530 via the base station QQ520, without explicitly referencing any intermediary devices and the precise routing of messages via these devices. The network infrastructure can determine the route, which can be configured to hide it from the UE QQ530 or the service provider operating the host computer QQ510, or both. The network infrastructure can also make decisions when the OTT connection QQ550 is active, through which it dynamically changes the route (e.g., based on network reconfiguration or load balancing considerations).

[0272] The wireless connection QQ570 between UEQQ530 and base station QQ520 is based on the teachings of the embodiments described throughout this disclosure. One or more embodiments in the various embodiments improve the performance of OTT services provided to UEQQ530 using OTT connection QQ550, wherein wireless connection QQ570 forms the final segment. More specifically, the teachings of these embodiments can improve data rates or reduce latency, and thereby provide benefits such as reduced user wait times and better responsiveness.

[0273] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors improved in one or more embodiments. Optional network functionality may also be available for reconfiguring the OTT connection QQ550 between the host computer QQ510 and the UE QQ530 in response to changes in measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection QQ550 may be implemented using software QQ511 and hardware QQ515 of the host computer QQ510, or software QQ531 and hardware QQ535 of the UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices traversed by the OTT connection QQ550; the sensors may participate in the measurement procedure by providing values ​​of the monitored quantities illustrated above, or by providing values ​​of other physical quantities from which software QQ511 and QQ531 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection QQ550 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect the base station QQ520, and it may be unknown or imperceptible to the base station QQ520. Such processes and functionality can be known and practiced in the art. In some embodiments, measurements may involve proprietary UE signaling, which facilitates the host computer QQ510 to measure throughput, propagation time, latency, etc. Measurements are possible because software QQ511 and QQ531 use the OTT connection QQ550 to transmit messages (especially empty or "pseudo" messages) while monitoring propagation time, errors, etc.

[0274] Image QQ6 Methods implemented in a communication system including a host computer, a base station, and user equipment according to some embodiments

[0275] Image QQ6 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Image QQ4 and QQ5 The host computers, base stations, and UEs described herein. For the sake of simplicity in this disclosure, this section will only include descriptions of... Image QQ6Referring to the accompanying drawings. In step QQ610, the host computer provides user data. In sub-step QQ611 of step QQ610 (which may be optional), the host computer provides user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying user data to the UE. In step QQ630 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0276] Image QQ7 Methods implemented in a communication system including a host computer, a base station, and user equipment according to some embodiments

[0277] Image QQ7 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Image QQ4 and QQ5 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include descriptions of... Image QQ7 Refer to the accompanying drawings. In step QQ710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step QQ720, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission may be carried out via a base station. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.

[0278] Image QQ8 Methods implemented in a communication system including a host computer, a base station, and user equipment according to some embodiments

[0279] Image QQ8 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Image QQ4 and QQ5 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include descriptions of... Image QQ8Referring to the accompanying drawings. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In sub-step QQ821 of step QQ820 (which may be optional), the UE provides user data by executing a client application. In sub-step QQ811 of step QQ810 (which may be optional), the UE executes a client application that provides user data as a response to the received input data provided by the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific method used to provide user data, in sub-step QQ830 (which may be optional), the UE initiates the transmission of user data to the host computer. In step QQ840 of the method, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0280] Image QQ9 Methods implemented in a communication system including a host computer, a base station, and user equipment according to some embodiments

[0281] Image QQ9 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Image QQ4 and QQ5 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include descriptions of... Image QQ9 Refer to the accompanying drawings. In step QQ910 (which may be optional), the base station receives user data from the UE according to the teachings of the embodiments described throughout this disclosure. In step QQ920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0282] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions according to one or more embodiments of this disclosure.

[0283] Figure VV0 Methods according to some embodiments

[0284] Figure VV0 A method according to certain embodiments is described. In some embodiments, the method may be performed by a network node, such as the base station described above (e.g., gNB). The method begins at step VV02, where the broadcast PDSCH is configured according to a performance enhancement configuration. For example, the performance enhancement configuration may include any one or more of the embodiments 1-6 described above (e.g., providing a lower code rate via adjustments to the TBS determination process, providing an MCS level with lower spectral efficiency, improving reliability via repetition in the time domain, improving reliability via repetition in the frequency domain, and / or using an expanded TBS to obtain a larger PRB allocation). The method proceeds to step VV04, where transmissions are sent via the broadcast PDSCH.

[0285] Figure VV1 Methods according to some embodiments

[0286] Figure VV1A method according to a specific embodiment is described. In some embodiments, the method may be performed by a radio device (WD) (such as a user equipment (UE)), an example of which is described above. The method begins at step VV12, where control information is received from a network node. As an example, the control information may be received in DCI or RRC signaling. The control information indicates one or more attributes associated with a performance enhancement configuration for broadcasting PDSCH. Any suitable attribute may be indicated in the control information. As an example, the attribute may indicate whether PDSCH repetition is configured in the frequency domain and / or time domain. The attribute may also indicate how repetition is configured (e.g., periodicity, repetition ID, etc.). The method proceeds to step VV14, where the radio device is configured to receive transmissions via a broadcast PDSCH configured according to the performance enhancement configuration, and step VV16, where transmissions are received from the network node via the broadcast PDSCH configured according to the performance enhancement configuration.

[0287] Image WW Virtualization devices according to some embodiments

[0288] Image WW The diagram illustrates a wireless network (e.g., Image QQ1 A schematic block diagram of device WW00 in a wireless network (as shown). This device can be a wireless device or a network node (e.g., Image QQ1 This is implemented in the wireless device QQ110 or network node QQ160 shown. Device WW00 is operable to implement the example methods described with reference to Figure VV, and possibly any other processes or methods disclosed herein. It should also be understood that the methods in Figure VV are not necessarily implemented solely by device WW00. At least some operations of the method may be implemented by one or more other entities.

[0289] The virtual device WW00 may include processing circuitry and other digital hardware. The processing circuitry may include one or more microprocessors or microcontrollers, and the digital hardware may include digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In some embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the PDSCH configuration unit WW02, the PDSCH transmission unit WW04, and any other suitable units of the device WW00 to perform corresponding functions according to one or more embodiments of this disclosure.

[0290] like Image WWAs shown, device WW00 includes a PDSCH configuration unit WW02 and a PDSCH transmission unit WW04. The PDSCH configuration unit WW02 is configured to configure broadcast PDSCH according to a performance enhancement configuration. The performance enhancement configuration may include any one or more of the embodiments 1-6 described above. For example, in some embodiments, the PDSCH configuration unit WW02 may include a TBS module [A] that adjusts the TBS determination process to provide a lower code rate (e.g., embodiment 1) and / or inflates the TBS to obtain a larger PRB allocation (e.g., embodiment 6). In some embodiments, the PDSCH configuration unit WW02 may include an MCS module [B] to provide an MCS level with lower spectral efficiency (e.g., embodiment 2). In some embodiments, the PDSCH configuration unit WW02 may include a repetition scheme module [C] to configure repetition in the time domain (e.g., embodiments 3 or 4) and / or in the frequency domain (e.g., embodiment 5). The PDSCH transmission unit WW04 transmits on the broadcast PDSCH according to the performance enhancement configuration.

[0291] The term “unit” may have a conventional meaning in the fields of electronics, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, outputs and / or display functions, such as those described herein.

[0292] In some embodiments, a computer program, computer program product, or computer-readable storage medium includes instructions that, when executed on a computer, perform any of the embodiments disclosed herein. In other examples, the instructions are carried on a signal or carrier and are executable on a computer, wherein, when executed, the instructions perform any of the embodiments disclosed herein.

[0293] Example Implementation

[0294] Group A Examples

[0295] 1. A method performed by a wireless device, the method comprising:

[0296] Transmissions are received from network nodes via a broadcast physical downlink shared channel (PDSCH) configured according to performance enhancement configuration.

[0297] 2. The method of claim 1, further comprising configuring the wireless device to receive the transmission via a broadcast PDSCH configured according to the performance enhancement.

[0298] 3. The method of any one of the preceding claims further includes receiving control information indicating one or more attributes associated with the performance enhancement configuration.

[0299] 4. The method described in any of the foregoing embodiments further includes:

[0300] -Provide user data; and

[0301] - User data is forwarded to the host computer via transmission to the base station.

[0302] Group B Implementation Examples

[0303] 5. A method performed by a base station, the method comprising:

[0304] - Configure the broadcast physical downlink shared channel (PDSCH) according to the performance enhancement configuration; and

[0305] Transmissions are sent via the broadcast PDSCH.

[0306] 6. The method of the preceding claims further includes sending downlink control information (DCI) indicating one or more attributes associated with the performance enhancement configuration.

[0307] 7. The method of any of the preceding claims, wherein the performance enhancement configuration provides a lower bitrate for the broadcast PDSCH than the bitrate associated with the normal configuration.

[0308] 8. The method of any of the preceding claims, wherein the bit rate is reduced by adjusting the transport block size (TBS).

[0309] 9. The method of any one of the preceding claims, wherein adjusting the transport block size comprises: using a first TBS determination process when the broadcast PDSCH is assigned by a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) scrambled by a first type of radio network temporary identifier (RNTI), and using a second TBS determination process when the broadcast PDSCH is assigned by the PDCCH having a CRC scrambled by a second type of RNTI.

[0310] 10. The method of any of the preceding claims, wherein adjusting the transport block size includes using a scaling factor in the TBS determination.

[0311] 11. The method of any of the preceding claims, wherein adjusting the transport block size includes performing nonlinear TBS adjustment.

[0312] 12. The method of any of the preceding claims, wherein the code rate is reduced by using a modulation and coding scheme (MCS) level with lower spectral efficiency.

[0313] 13. The method of any of the preceding claims, wherein the MCS level is determined based on a table defined for enhanced mobile broadband (eMBB) PDSCH.

[0314] 14. The method of any of the preceding claims, wherein the MCS level is determined based on a table specifically defined for the broadcast PDSCH.

[0315] 15. The method of any of the preceding claims, wherein the performance enhancement configuration is configured to repeat in the time domain.

[0316] 16. The method of any of the preceding claims, wherein the performance enhancement configuration configures frequency domain repetition.

[0317] 17. The method of any of the preceding claims, wherein the performance enhancement configuration configures an expanded TBS to obtain a larger Physical Resource Block (PRB) allocation.

[0318] 18. The method of any of the foregoing embodiments further includes:

[0319] - Obtaining user data; and

[0320] - Forward user data to the host computer or wireless device.

[0321] Group C Implementation Examples

[0322] 19. A wireless device, the wireless device comprising:

[0323] - Processing circuitry configured to perform any step of any embodiment in Group A; and

[0324] - A power supply circuit configured to supply power to wireless devices.

[0325] 20. A base station, the base station comprising:

[0326] - Processing circuitry configured to perform any step of any embodiment in any of the Group B embodiments;

[0327] - A power supply circuit configured to supply power to wireless devices.

[0328] 21. A user equipment (UE), the UE comprising:

[0329] - An antenna configured to transmit and receive wireless signals;

[0330] - A radio front-end circuit that is connected to the antenna and processing circuitry and configured to regulate the signal transmitted between the antenna and processing circuitry;

[0331] - The processing circuitry is configured to perform any step of any of the steps in any of the embodiments in Group A;

[0332] - An input interface connected to the processing circuitry and configured to allow information to be input into the UE for processing by the processing circuitry;

[0333] - An output interface connected to the processing circuit and configured to output information already processed by the processing circuit from the UE; and

[0334] - A battery connected to the processing circuitry and configured to supply power to the UE.

[0335] 22. A computer program comprising instructions that, when executed on a computer, perform any step of any embodiment in the Group A embodiments.

[0336] 23. A computer program product comprising a computer program, the computer program including instructions that, when executed on a computer, perform any step of any embodiment in the Group A embodiments.

[0337] 24. A non-transitory computer-readable storage medium or carrier comprising a computer program, said computer program comprising instructions that, when executed on a computer, perform any step of any embodiment in the Group A embodiments.

[0338] 25. A computer program comprising instructions that, when executed on a computer, perform any step of any embodiment in the Group B embodiments.

[0339] 26. A computer program product comprising a computer program, the computer program including instructions that, when executed on a computer, perform any step of any embodiment in the Group B embodiments.

[0340] 27. A non-transitory computer-readable storage medium or carrier comprising a computer program, said computer program comprising instructions that, when executed on a computer, perform any step of any embodiment in the Group B embodiments.

[0341] 28. A communication system including a host computer, the host computer comprising:

[0342] - Configured to provide user data processing circuitry; and

[0343] - A communication interface configured to forward user data to the cellular network for transmission to the user equipment (UE).

[0344] -The cellular network includes a base station having a radio interface and processing circuitry, the processing circuitry of which is configured to perform any step of any embodiment in the Group B embodiments.

[0345] 29. The communication system of the foregoing embodiments also includes a base station.

[0346] 30. The communication system of the two embodiments described above further includes a UE, wherein the UE is configured to communicate with a base station.

[0347] 31. The communication system of the foregoing three embodiments, wherein:

[0348] - The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and

[0349] - The UE includes processing circuitry configured to execute client applications associated with the host application.

[0350] 32. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0351] - Provide user data at the host computer; and

[0352] - At the host computer, a transmission carrying user data to the UE is initiated via a cellular network including a base station, wherein the base station performs any step in any of the embodiments in Group B.

[0353] 33. The method of the foregoing embodiments further includes: transmitting user data at a base station.

[0354] 34. The method of the foregoing two embodiments, wherein user data is provided at a host computer by executing a host application, the method further includes: at the UE, executing a client application associated with the host application.

[0355] 35. A user equipment (UE) configured to communicate with a base station, the UE including a radio interface and processing circuitry configured to perform any of the three embodiments described above.

[0356] 36. A communication system including a host computer, the host computer comprising:

[0357] - Configured to provide user data processing circuitry; and

[0358] - A communication interface configured to forward user data to the cellular network for transmission to the user equipment (UE).

[0359] -The UE includes a radio interface and processing circuitry, and the components of the UE are configured to perform any step of any embodiment in the Group A embodiments.

[0360] 37. The communication system of the foregoing embodiments, wherein the cellular network further includes a base station configured to communicate with the UE.

[0361] 38. The communication system of the two embodiments described above, wherein:

[0362] - The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and

[0363] - The UE's processing circuitry is configured to execute client applications associated with the host application.

[0364] 39. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0365] - Provide user data at the host computer; and

[0366] - At the host computer, a transmission carrying user data to the UE via a cellular network including a base station is initiated, wherein the UE performs any step of any embodiment in any of the Group A embodiments.

[0367] 40. The method described in the foregoing embodiments further includes: receiving user data from the base station at the UE.

[0368] 41. A communication system including a host computer, the host computer comprising:

[0369] - A communication interface configured to receive user data transmitted from a user equipment (UE) to a base station.

[0370] -The UE includes a radio interface and processing circuitry, the processing circuitry of which is configured to perform any step of any embodiment in the Group A embodiments.

[0371] 42. The communication system described in the foregoing embodiments further includes a UE.

[0372] 43. The communication system described in the two preceding embodiments further includes a base station, wherein the base station includes a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by the transmission from the UE to the base station to a host computer.

[0373] 44. The communication system of the three embodiments described above, wherein:

[0374] - The host computer's processing circuitry is configured to execute host applications; and

[0375] - The UE's processing circuitry is configured to execute client applications associated with the host application, thereby providing user data.

[0376] 45. The communication system of the foregoing four embodiments, wherein:

[0377] - The host computer's processing circuitry is configured to execute host applications, thereby providing requested data; and

[0378] - The UE's processing circuitry is configured to execute client applications associated with the host application, thereby providing user data in response to requested data.

[0379] 46. ​​A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0380] - At the host computer, user data transmitted from the UE to the base station is received, wherein the UE performs any step in any of the embodiments in Group A.

[0381] 47. The method described in the foregoing embodiments further includes: providing user data to the base station at the UE.

[0382] 48. The methods of the foregoing two embodiments further include:

[0383] - At the UE, the client application is executed, thereby providing the user data to be transmitted; and

[0384] - On the host computer, execute the host application associated with the client application.

[0385] 49. The methods of the foregoing three embodiments further include:

[0386] - At the UE (User Equipment) level, execute the client application; and

[0387] - At the UE, data input to the client application is received; at the host computer, the input data is provided by executing the host application associated with the client application.

[0388] - The user data to be transmitted is provided by the client application in response to the input data.

[0389] 50. A communication system including a host computer, the host computer comprising: a communication interface configured to receive user data transmitted from a user equipment (UE) to a base station; wherein the base station includes a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any step of any embodiment in the Group B embodiments.

[0390] 51. The communication system of the foregoing embodiments also includes a base station.

[0391] 52. The communication system of the two embodiments described above further includes a UE, wherein the UE is configured to communicate with a base station.

[0392] 53. The communication system of the foregoing three embodiments, wherein:

[0393] - The host computer's processing circuitry is configured to execute host applications;

[0394] - The UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0395] 54. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0396] - At the host computer, user data originating from a transmission already received by the base station from the UE is received from the base station, wherein the UE performs any step in any of the embodiments in Group A embodiments.

[0397] 55. The method described in the foregoing embodiments further includes: receiving user data from the UE at the base station.

[0398] 56. The method described in the two embodiments above further includes: at the base station, initiating the transmission of received user data to the host computer.

[0399] Figure YY1 The illustration shows a second example method YY100 performed by a network node according to certain embodiments. Method YY100 may begin at step YY110, wherein the network node indicates at least a modulation and coding scheme (MCS) and a scaling factor for the downlink shared channel in a control message. The scaling factor indicates a value less than 1. For example, the control message may indicate an MCS and a scaling factor of 1 / 2 or 1 / 4. In some embodiments, the control message includes at least one bit indicating that a first scaling factor, such as 1 / 2, is used when one of the at least one bit is set to a first value; and a second scaling factor, such as 1 / 4, is used when one of the at least one bit is set to a second value. In some embodiments, the scaling factor indicated in the control message is carried on the PDCCH. For example, the control message may be a DCI transmitted via the PDCCH.

[0400] In some embodiments, the control message may indicate further indications that could enhance shared downlink channel transmission. For example, in some embodiments, the control message indicates time-domain and / or frequency-domain repetition.

[0401] In step YY120, a control message is sent to the user equipment (UE). The control message enables the determination of the transport block size (TBS) for sharing the downlink channel. In some embodiments, the control message enables the UE to determine the median number of information bits, at least based on the MCS and a scaling factor. Based on the median number of bits, the UE can determine the TBS.

[0402] Method YY100 may include additional steps. In some embodiments, the network node may allocate physical resource blocks (PRBs) at least in part based on the TBS, as shown in step YY130. For example, the network node may determine the TBS and then allocate PRBs based on the TBS. Thus, the PRB may reflect any performance enhancements to the physical downlink channel resulting from adjusting the TBS.

[0403] Figure YY2 The illustration shows a third example method YY200 performed by a network node according to certain embodiments. Method YY200 may begin at one of steps YY205 and YY210. In some embodiments, method YY200 begins at step YY205, where the MCS indicated in the control message is determined based on a table or table entries specifically defined for PDSCH. For example, the table of MCS may be specifically constructed and / or used for PDSCH, having entries that have lower spectral efficiency compared to tables used for other channels. As another example, the table of MCS may have entries only used for PDSCH with lower spectral efficiency. The specially defined table or table entries can be used, for example, to enhance transmission through PDSCH by changing the TBS determined by the wireless device communicating with the network node via PDSCH.

[0404] Alternatively, in some embodiments, method YY200 begins at step YY210, which determines the MCS to be indicated in the control message based on a table defined for enhanced mobile broadband (eMBB) PDSCH. For example, the MCS may be selected from a portion of a table defined for eMBB associated with lower spectral efficiency. In this way, the network node can determine the MCS to be used in the control message, which the radio device can use to determine the TBS on the PDSCH.

[0405] Steps YY220 and YY230 can occur in a similar manner to steps YY110 and YY120 of the referenced method YY100 described above. For example, the MCS indicated in the control message can be an MCS determined from the eMBB table or a specially defined table or table entry for PDSCH. Similarly, the UE can use the MCS along with a scaling factor to determine the TBS. In the example of selecting an MCS with lower spectral efficiency, a larger TBS can be selected to improve transmission on the shared downlink channel.

[0406] Figure YY3 The illustration depicts a second example method YY300 performed by a wireless device according to certain embodiments. Method YY300 may begin at step YY310, where the wireless device receives a control message. This control message indicates at least the MCS and scaling factor for the downlink shared channel. The scaling factor indicates a value less than 1. For example, a network node may determine the MCS and scaling factor and broadcast the control message to the wireless device.

[0407] Upon receiving the control message, in step YY320, the wireless device may determine the Transport Block Size (TBS) based on the MCS and scaling factor indicated in the control message. For example, the wireless device may determine the number of resource elements allocated within the PRB for the downlink shared channel. This determination can be adjusted by multiplying one of the values ​​used in the calculation by a scaling factor (e.g., the median number of information bits). Additionally, the wireless device may use the MCS (and / or its index) to further determine the MCS. In some embodiments, a scaling factor less than one inflates the TBS compared to determining the TBS without any scaling factor (or with a scaling factor of one). Increasing the TBS enhances downlink shared channel communication.

[0408] In some embodiments, method YY300 includes additional optional steps. In some embodiments, in step YY330, the wireless device obtains a Physical Resource Block (PRB) allocation based at least in part on the determined TBS. The wireless device can then obtain a PRB allocation. In some embodiments, the TBS is inflated, thereby causing a larger PRB allocation at the network nodes. A larger PRB allocation can be used to communicate on the downlink shared channel at a lower code rate or with higher redundancy. Thus, the downlink shared channel can be enhanced.

[0409] Figure YY4 A third example method YY400, performed by a wireless device according to certain embodiments, is illustrated. Method YY400 may begin similarly to method YY300 at steps YY410 and YY420, corresponding to YY310 and YY320, respectively. In some embodiments, YY400 further includes an optional step YY430: namely, decoding a transport block of the downlink shared channel based on a TBS, which is determined based on an MCS and scaling factor indicated in a control message. For example, a network node may transmit data or control messages on the downlink shared channel based on resource blocks allocated to the wireless device. The wireless device may receive the transmission and decode it based on a TBS determined by the wireless device. In this way, the wireless device may receive higher quality transmissions on the downlink shared channel based on a TBS determined based on an MCS and scaling factor.

[0410] Can be Figure YY1Any of the methods YY100, YY200, YY300, and YY400 described in section -4 can be modified, added to, or omitted. Any steps may be performed in parallel or in any suitable order. For example, in some embodiments, one or more steps of methods YY100, YY200, YY300, and YY400 may be repeated for coatings and / or individual fluorescent layers with different performance characteristics. Furthermore, methods YY100, YY200, YY300, and YY400 may include more, fewer, or other steps. Additionally, one or more steps of methods YY100, YY200, YY300, and YY400 or embodiments thereof may be performed by any suitable component or combination of components of the wireless devices QQ110, QQ200, QQ330, QQ491, QQ492, QQ530 or network nodes QQ160, QQ330, QQ412, QQ520, or any other components described herein.

[0411] As described above, certain embodiments of this disclosure can be implemented by modifying Section 5.1.3 of 3GPP TS 38.214. The following paragraphs provide examples of how certain aspects of this disclosure can be included in Section 5.1.3, for example, as shown below in the more recent version V15.2.0.

[0412] 5.1.3 Determining the modulation order, target code rate, redundancy version, and transport block size

[0413] To determine the modulation order, target code rate, and (one or more) transport block sizes in the physical downlink shared channel, the UE should first...

[0414] - Read the 5-bit modulation and coding scheme field (I) from the DCI. MCS The modulation order (Q) is determined based on the procedure defined in sub-clause 5.1.3.1. m and target bitrate (R), and

[0415] - Read the redundant version field (rv) in the DCI to determine the redundant version.

[0416] And secondly

[0417] - The number of layers the UE should use (ν), and the total number of PRBs allocated before rate matching (n) PRB The transport block size is determined based on the procedure defined in sub-clause 5.1.3.2.

[0418] If the effective channel code rate is higher than 0.95, the UE can skip decoding of the transport block in the initial transmission. The effective channel code rate is defined as the number of downlink information bits (including CRC bits) divided by the number of physical channel bits on the PDSCH. If the UE skips decoding, the physical layer indicates to the higher layers that the transport block has not been successfully decoded.

[0419] 5.1.3.1 Determination of Modulation Order and Target Code Rate

[0420] For PDSCH scheduled using DCI format 1_0 or format 1_1, which has a CRC scrambled by C-RNTI, new-RNTI, TC-RNTI, CS-RNTI, SI-RNTI, RA-RNTI or P-RNTI,

[0421] If the higher-layer parameter mcs-Table given by PDSCH-config is set to 'qam256', and PDSCH is scheduled by PDCCH using DCI format 1_1, and CRC is scrambled by C-RNTI or CS-RNTI, the UE should use I MCS The modulation order (Q) used in the physical downlink shared channel is determined using Table 5.1.3.1-2. m ) and target bit rate (R).

[0422] Otherwise, if the UE is not configured with new-RNTI, the higher-layer parameter mcs-Table given by PDSCH-Config is set to 'qam64LowSE', and PDSCH is scheduled with C-RNTI. The PDSCH is then assigned by PDCCH within the UE-specific search space.

[0423] -UE should use I MCS The modulation order (Q) used in the physical downlink shared channel is determined using Table 5.1.3.1-3. m ) and target bit rate (R).

[0424] Otherwise, if the UE is configured with a new-RNTI and PDSCH is scheduled with the new RNTI...

[0425] -Then the UE should use I MCS The modulation order (Q) used in the physical downlink shared channel is determined using Table 5.1.3.1-3. m ) and target bit rate (R).

[0426] Otherwise, if the UE is not configured with the higher-layer parameter mcs-Table given by SPS-config, the higher-layer parameter mcs-Table given by PDSCH-config is set to 'qam256', PDSCH is scheduled with CS-RNTI, and PDSCH is assigned by PDCCH with DCI format 1_1.

[0427] -UE should use I MCS The modulation order (Q) used in the physical downlink shared channel is determined using Table 5.1.3.1-2. m ) and target bit rate (R).

[0428] Otherwise, if the UE is configured with the higher-layer parameter mcs-Table set to 'qam64LowSE' by SPS-config, and PDSCH is scheduled using CS-RNTI.

[0429] -UE should use I MCS The modulation order (Q) used in the physical downlink shared channel is determined using Table 5.1.3.1-3. m ) and target bit rate (R).

[0430] otherwise

[0431] -UE should use I MCS The modulation order (Q) used in the physical downlink shared channel is determined using Table 5.1.3.1-1. m ) and target bit rate (R).

[0432] Finish.

[0433] It is not expected that the UE will use P-RNTI, RA-RNTI, SI-RNTI and Q m Decoding of PDSCH with >2 scheduling

[0434] Table 5.1.3.1-1: MCS Index Table 1 for PDSCH

[0435]

[0436] Table 5.1.3.1-2: MCS Index Table 2 of PDSCH

[0437]

[0438]

[0439] Table 5.1.3.1-3: PDSCH MCS Index Table 3

[0440]

[0441] 5.1.3.2 Determining the Transport Block Size

[0442] When the higher-level parameter maxNrofCodeWordsScheduledByDCI indicates that two codeword transmissions are enabled, if I MCS =26 and if for the corresponding transport block rv id =1, then the transport block is disabled by DCI format 1_1; otherwise, the transport block is enabled. If both transport blocks are enabled, transport blocks 1 and 2 are mapped to codewords 0 and 1, respectively. If only one transport block is enabled, the enabled transport block is always mapped to the first codeword.

[0443] For a PDSCH assigned by a PDCCH using DCI format 1_0 or format 1_1 with a CRC scrambled by C-RNTI, new-RNTI, TC-RNTI, CS-RNTI or SI-RNTI, if Table 5.1.3.1-2 is used and 0≤I MCS ≤27, or use a table other than Table 5.1.3.1-2 and 0≤I MCS If the value is ≤28, then the UE should first determine the TBS, as specified below, unless the transport block is disabled in DCI format 1_1:

[0444] 1) The UE should first determine the number of REs (N) within the time slot. RE ).

[0445] -UE first passes To determine the number of REs (N') allocated to PDSCH within the PRB. RE ),in It is the number of subcarriers in a physical resource block. It is the number of symbols allocated by PDSCH within a time slot. This refers to the number of REs per PRB DM-RS during the scheduling duration of the DM-RSCDM group overhead in the absence of data, as indicated by DCI format 1_1 or as described in sub-clause 5.1.6.2 for format 1_0, and This is the overhead configured by the higher-level parameter xOverhead in PDSCH-ServingCellConf. If xOverhead (a value from 0, 6, 12, or 18) is not configured in PDSCH-ServingCellConf, then... Set to 0. If the PDCCH schedules the PDSCH with a CRC scrambled by SI-RNTI, RA-RNTI, or P-RNTI, then it is assumed that... It is 0.

[0446] -UE via N RE =min(156,N') RE )·n PRB To determine the total number (N) of REs allocated to PDSCH. RE ), where n PRB This is the total number of PRBs allocated to the UE.

[0447] 2) Through N info =N RE ·R·Q m ·υ to obtain the median number (N) of the information bits info ).

[0448] If N info ≤3824

[0449] Then step 3 is used as the next step determined by TBS.

[0450] otherwise

[0451] Use step 4 as the next step determined by TBS.

[0452] Finish

[0453] 3) When N info When ≤3824, TBS is determined as follows:

[0454] - The intermediate number of the quantization of information bits in

[0455] - Use Table 5.1.3.2-2 to find values ​​not less than N' info The closest TBS.

[0456] Table 5.1.3.2-2: N info ≤3824 TBS

[0457] index TBS index TBS index TBS index TBS 1 24 31 336 61 1288 91 3624 2 32 32 352 62 1320 92 3752 3 40 33 368 63 1352 93 3824 4 48 34 384 64 1416 5 56 35 408 65 1480 6 64 36 432 66 1544 7 72 37 456 67 1608 8 80 38 480 68 1672 9 88 39 504 69 1736 10 96 40 528 70 1800 11 104 41 552 71 1864 12 112 42 576 72 1928 13 120 43 608 73 2024 14 128 44 640 74 2088 15 136 45 672 75 2152 16 144 46 704 76 2216 17 152 47 736 77 2280 18 160 48 768 78 2408 19 168 49 808 79 2472 20 176 50 848 80 2536 21 184 51 888 81 2600 22 192 52 928 82 2664 23 208 53 984 83 2728 24 224 54 1032 84 2792 25 240 55 1064 85 2856 26 256 56 1128 86 2976 27 272 57 1160 87 3104 28 288 58 1192 88 3240 29 304 59 1224 89 3368 30 320 60 1256 90 3496

[0458] 4) When N info When the value is greater than 3824, TBS is determined as follows.

[0459] - The intermediate number of the quantization of information bits in And it breaks the constraints of the rounding function toward the next largest integer.

[0460] -If R≤1 / 4, then:

[0461] in

[0462] otherwise

[0463] If N' info If the value is greater than 8424, then:

[0464] in

[0465] otherwise

[0466]

[0467] Finish

[0468] Finish

[0469] Otherwise, if Table 5.1.3.1-2 is used and 28 ≤ I MCS ≤31,

[0470] Assume TBS is based on the use of 0≤I MCS The DCI transmitted in the latest PDCCH of the same transport block ≤27 is determined. If 0≤I is not used... MCS The PDCCH for the same transport block ≤27, and if the initial PDSCH for the same transport block is semi-persistently scheduled, then the TBS should be determined based on the most recent semi-persistently scheduled PDCCH.

[0471] otherwise

[0472] -Assuming TBS is based on the use of 0≤I MCS The DCI transmitted in the latest PDCCH of the same transport block ≤28 is determined. If 0≤I is not used... MCS The PDCCH for the same transport block is ≤28, and if the initial PDSCH for the same transport block is semi-persistently scheduled, the TBS should be determined based on the most recent semi-persistently scheduled PDCCH.

[0473] For a PDSCH assigned using a DCI format 1_0 PDCCH with a CRC scrambled by P-RNTI or RA-RNTI, the TBS determines that steps 1-4 are followed, with the following modification in step 2: In N info Scaling N is applied in the calculation info =S·N RE ·R·Q m ·υ, where the scaling factor is determined based on the TB scaling field in the DCI as shown in Table 5.1.3.2-3.

[0474] Table 5.1.3.2-3: N of P-RNTI and RA-RNTI info scaling factor

[0475] TB scaling field Scaling factor S 00 1 01 0.5 10 0.25 11

[0476] The TBS identified above, as well as the NDI and HARQ process IDs signaled on the PDCCH, should be reported to higher levels.

[0477] The preceding paragraphs provide examples of how certain aspects of this disclosure can be included in Section 5.1.3 of 3GPP TS 38.214 V15.0.1. In the examples above, the DCI includes I that can be read to determine the modulation and coding scheme. MCS The fields include the TB scaling field, which can be read to determine the scaling factor S (e.g., according to Tables 5.1.3.2-3). In some embodiments, when performing the methods disclosed herein, the I from the above examples based on Section 5.1.3 of the 3GPP technical specification can be used. MCS And the TB scaling field. For example, the scaling factor “S” from the example based on Section 5.1.3 of the 3GPP technical specification can be used as the scaling factor “α” described in other examples in this document (such as example method A-1).

[0478] As another example, the above refers to Figure YY1 and YY2 The described method may at least indicate the MCS used for downlink shared channel in the control message (which may use the I in Section 5.1.3). MCS The field indicates the scaling factor (which can be indicated using the TB scaling field in Section 5.1.3) (see steps YY110 and YY220 discussed above, for example). The above addresses... Figure YY1 and YY2 The described method may send I, including section 5.1.3, to the UE. MCS Control messages for the fields and TB scaling fields enable the UE to determine the TBS used for sharing the downlink channel (see, for example, steps YY120 and YY230 discussed above).

[0479] As another example, the above refers to Figure YY3 and YY4 The described method can receive an MCS indicating the use of a downlink shared channel (which can use the I in Section 5.1.3). MCS Control messages for the scaling factor (which can be indicated using the TB scaling field in Section 5.1.3) and scaling factors (see, for example, steps YY310 and YY410). The above refers to... Figure YY3 and YY4 The described method may be based on the I indicated in the control message. MCS The TBS is determined by the field and the TB scaling field (see, for example, steps YY320 and YY420). For example, a wireless device can determine the TBS by calculating N. infoSimultaneously, a scaling factor S is applied to scale the TBS, which is determined based on the TB scaling field in the DCI as shown in Table 5.1.3.2-3. The wireless device can also be based on I... MCS To determine the MCS.

[0480] Although this disclosure has been described with reference to several embodiments, numerous changes, variations, alterations, modifications and alterations may be suggested to those skilled in the art, and this disclosure is intended to cover such changes, variations, alterations, modifications and alterations that fall within the scope of the appended claims.

Claims

1. A method performed by a network node, the method comprising: indicating (YY110, YY220) at least a modulation and coding scheme, MCS, and a scaling factor for a downlink shared channel in a control message, the scaling factor indicating a value less than 1; and transmitting (YY120, YY230) the control message to a user equipment, UE, the control message enabling determination of a transport block size, TBS, for the downlink shared channel, wherein the control message enables the UE to determine an intermediate number of information bits based at least on the MCS and scaling factor, and wherein the intermediate number of information bits enables the UE to determine the TBS, wherein the UE is enabled to determine the intermediate number of information bits using the following equation: ， wherein N info is the intermediate number of information bits, α is the scaling factor, N RE is the number of resource elements within a time slot, R is the target code rate, Q m is the modulation order, and υ is the number of layers.

2. The method of claim 1, wherein the scaling factor is one of 1 / 2 and 1 / 4.

3. The method of any preceding claim, wherein the control message comprises at least one bit indicating: a first scaling factor is used when a first bit in the at least one bit is set to a first value, and a second scaling factor is used when the first bit is set to a second value.

4. The method of claim 3, wherein the control message comprises at least one bit indicating: 1 / 2 is used as the scaling factor when a first bit in the at least one bit is set to 0, and 1 / 4 is used as the second scaling factor when the first bit is not set to 0.

5. The method of any of claims 1-2, wherein the control message is transmitted via a physical downlink control channel, PDCCH.

6. The method of any of claims 1-2, wherein the scaling factor is indicated in the control message via a PDCCH, and the scaling factor comprises a value of 1 / 2 or 1 / 4.

7. The method of any of claims 1-2, wherein the shared channel is a physical downlink shared channel, PDSCH.

8. The method of claim 7, wherein the PDSCH is a broadcast channel.

9. The method of any of claims 1-2, wherein the control message is carried by a PDCCH having a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier, RNTI, comprising a system information-RNTI (SI-RNTI), a random access-RNTI (RA-RNTI), or a paging-RNTI (P-RNTI).

10. The method of any of claims 1-2, wherein the UE being enabled to determine the TBS further enables the UE to decode a transport block of the shared channel.

11. The method of any of claims 1-2, wherein the control message further indicates a time domain repetition or a frequency domain repetition.

12. The method of any of claims 1-2, wherein the MCS indicated in the control message comprises a lower spectral efficiency than a normal MCS.

13. The method of claim 12, wherein the normal MCS corresponds to an MCS according to Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.214 version 15.2.0 or earlier.

14. The method of any of claims 1-2, further comprising: determining (YY210) the MCS to be indicated in the control message based on a table defined for an enhanced mobile broadband (eMBB) PDSCH.

15. The method of claim 7, further comprising: determining (YY205) the MCS to be indicated in the control message based on a table or table entry defined specifically for the PDSCH.

16. The method of any one of claims 1-2, further comprising: allocating (YY130) physical resource blocks (PRBs) based at least in part on the TBS.

17. A method performed by a wireless device (WD), the method comprising: receiving (YY310, YY410) a control message, the control message indicating at least a modulation and coding scheme, MCS, and a scaling factor for a downlink shared channel, wherein the scaling factor indicates a value less than 1; determining (YY320, YY420) a transport block size, TBS, based on the MCS and the scaling factor indicated in the control message, wherein determining the TBS based on the MCS and the scaling factor indicated in the control message comprises determining an intermediate number of information bits based at least on the MCS and the scaling factor, wherein the WD is enabled to determine the intermediate number of information bits using the following equation: ， wherein Ninfo is the intermediate number of information bits, α is the scaling factor, N RE is the number of resource elements within a slot, R is the target code rate, Q m is the modulation order, and υ is the number of layers.

18. The method of claim 17, wherein the scaling factor is one of 1 / 2 and 1 / 4.

19. The method of any one of claims 17-18, wherein the control message comprises at least one bit indicating: a first scaling factor is used when a first bit in the at least one bit is set to a first value, and a second scaling factor is used when the first bit is set to a second value.

20. The method of claim 19, wherein the control message comprises at least one bit indicating: 1 / 2 is used as the scaling factor when a first bit in the at least one bit is set to 0, and 1 / 4 is used as the second scaling factor when the first bit is not set to 0.

21. The method of any one of claims 17-18, wherein the control message is transmitted via a physical downlink control channel, PDCCH.

22. The method of any one of claims 17-18, wherein the scaling factor is indicated in the control message via a PDCCH, and the scaling factor comprises a value of 1 / 2 or 1 / 4.

23. The method of any one of claims 17-18, wherein the shared channel is a physical downlink shared channel, PDSCH.

24. The method of claim 23, wherein the PDSCH is a broadcast channel.

25. The method of any of claims 17-18, wherein the control message is carried on a PDCCH having a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI), the RNTI comprising a system information-RNTI (SI-RNTI), a random access-RNTI (RA-RNTI), or a paging-RNTI (P-RNTI).

26. The method of any of claims 17-18, further comprising decoding (YY430) a transport block of the downlink shared channel based on the TBS, the TBS being determined based on the MCS and the scaling factor indicated in the control message.

27. The method of any of claims 17-18, wherein the control message further indicates a time domain repetition or a frequency domain repetition.

28. The method of any of claims 17-18, wherein the MCS indicated in the control message comprises a lower spectral efficiency than a normal MCS.

29. The method of claim 28, wherein the normal MCS corresponds to an MCS according to Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.214 version 15.2.0 or earlier.

30. The method of any of claims 17-18, wherein the control message indicates the MCS based on a table defined for an enhanced mobile broadband (eMBB) PDSCH.

31. The method of claim 23, wherein the control message indicates the MCS based on a table or table entry defined specifically for the PDSCH.

32. The method of any of claims 17-18, further comprising obtaining (YY330) a physical resource block (PRB) allocation based at least in part on the determined TBS.

33. A network node (QQ160, QQ330, QQ412, QQ520) comprising a memory (QQ180, QQ390-1, QQ390-2) operable to store instructions and a processing circuitry (QQ170, QQ360, QQ528) operable to execute the instructions, whereby the network node is operable to: indicate in a control message at least a modulation and coding scheme, MCS, and a scaling factor for a downlink shared channel, the scaling factor indicating a value less than 1; and transmit the control message to a user equipment, UE (QQ110, QQ200, QQ330, QQ491, QQ492, QQ530), the control message enabling determination of a transport block size, TBS, for the downlink shared channel, wherein the control message enables the UE to determine an intermediate number of information bits based at least on the MCS and scaling factor, and wherein the intermediate number of information bits enables the UE to determine the TBS, wherein the intermediate number of information bits is enabled to be determined by the UE using the following equation: ， wherein Ninfo is the intermediate number of information bits, α is the scaling factor, N RE is the number of resource elements within a slot, R is the target code rate, Q m is the modulation order, and υ is the number of layers.

34. The network node of claim 33, wherein the scaling factor is one of ½ and ¼.

35. The network node of any one of claims 33-34, wherein the control message comprises at least one bit indicating that a first scaling factor is used when a first bit of the at least one bit is set to a first value and a second scaling factor is used when the first bit is set to a second value.

36. The network node of claim 35, wherein the control message comprises at least one bit indicating that ½ is used as the scaling factor when a first bit of the at least one bit is set to 0 and ¼ is used as the second scaling factor when the first bit is not set to 0.

37. The network node of any one of claims 33-34, wherein the control message is transmitted via a physical downlink control channel (PDCCH).

38. The network node of any one of claims 33-34, wherein the scaling factor is indicated in the control message via a PDCCH and comprises a value of ½ or ¼.

39. The network node of any one of claims 33-34, wherein the shared channel is a physical downlink shared channel (PDSCH).

40. The network node of claim 39, wherein the PDSCH is a broadcast channel.

41. The network node of any one of claims 33-34, wherein the control message is carried on a PDCCH having a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI) comprising a system information-RNTI (SI-RNTI), a random access-RNTI (RA-RNTI), or a paging-RNTI (P-RNTI).

42. The network node of any one of claims 33-34, wherein enabling the UE to determine the TBS further enables the UE to decode a transport block of the shared channel.

43. The network node of any one of claims 33-34, wherein the control message further indicates a time domain repetition or a frequency domain repetition.

44. The network node of any one of claims 33-34, wherein the MCS indicated in the control message comprises a lower spectral efficiency than a normal MCS.

45. The network node of claim 44, wherein the normal MCS corresponds to an MCS according to Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.214 version 15.2.0 or earlier.

46. The network node of any one of claims 33-34, wherein the network node is further operable to determine the MCS to indicate in the control message based on a table defined for an enhanced mobile broadband (eMBB) PDSCH.

47. The network node of claim 39, wherein the network node is further operable to determine the MCS to be indicated in the control message based on a table or table entry defined specifically for the PDSCH.

48. The network node of any one of claims 33-34, wherein the network node is further operable to allocate physical resource blocks (PRBs) based at least in part on the TBS.

49. A wireless device (QQl 10, QQ200, QQ330, QQ491, QQ492, QQ530) comprising a memory (QQ130, QQ215, QQ390-1, QQ390-2) operable to store instructions and a processing circuit (QQ120, QQ201, QQ360, QQ538) operable to execute the instructions, whereby the wireless device is operable to: receive a control message, the control message indicating at least a modulation and coding scheme, MCS, and a scaling factor for a downlink shared channel, wherein the scaling factor indicates a value less than 1; determine a transport block size, TBS, based on the MCS and the scaling factor indicated in the control message, wherein determining the TBS based on the MCS indicated in the control message and the scaling factor comprises: determine an intermediate number of information bits based at least on the MCS and the scaling factor, wherein the intermediate number of information bits is determined using the following equation: ， wherein Ninfo is the intermediate number of information bits, α is the scaling factor, N RE is the number of resource elements within a slot, R is the target code rate, Q m is the modulation order, and υ is the number of layers.

50. The wireless device of claim 49, wherein the scaling factor is one of ½ and ¼.

51. The wireless device of any one of claims 49-50, wherein the control message comprises at least one bit indicating: a first scaling factor is used when a first bit in the at least one bit is set to a first value, and a second scaling factor is used when the first bit is set to a second value.

52. The wireless device of any one of claims 49-50, wherein the control message comprises at least one bit indicating: ½ is used as the scaling factor when a first bit in the at least one bit is set to 0, and ¼ is used as the scaling factor when the first bit is not set to 0.

53. The wireless device of any one of claims 49-50, wherein the control message is transmitted via a physical downlink control channel, PDCCH.

54. The wireless device of any one of claims 49-50, wherein the scaling factor is indicated in the control message via a PDCCH, and the scaling factor comprises a value of ½ or ¼.

55. The wireless device of any one of claims 49-50, wherein the shared channel is a physical downlink shared channel, PDSCH.

56. The wireless device of claim 55, wherein the PDSCH is a broadcast channel.

57. The wireless device of any of claims 49-50, wherein the control message is carried on a PDCCH having a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI), the RNTI comprising a system information-RNTI (SI-RNTI), a random access-RNTI (RA-RNTI), or a paging-RNTI (P-RNTI).

58. The wireless device of any of claims 49-50, further operable to decode a transport block of the downlink shared channel based on the TBS, the TBS determined based on the MCS and the scaling factor indicated in the control message.

59. The wireless device of any of claims 49-50, wherein the control message further indicates a time domain repetition or a frequency domain repetition.

60. The wireless device of any of claims 49-50, wherein the MCS indicated in the control message comprises a lower spectral efficiency than a normal MCS.

61. The wireless device of claim 60, wherein the normal MCS corresponds to an MCS according to Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.214 version 15.2.0 or earlier.

62. The wireless device of any of claims 49-50, wherein the control message indicates the MCS based on a table defined for enhanced mobile broadband (eMBB) PDSCH.

63. The wireless device of any of claims 49-50, wherein the control message indicates the MCS based on a table or table entry defined specifically for the PDSCH.

64. The wireless device of any of claims 49-50, wherein the wireless device is further operable to obtain a physical resource block (PRB) allocation based at least in part on the determined TBS.

65. A computer program product comprising a non-transitory computer- readable medium (QQ180, QQ390-1, QQ390-2) storing computer readable program code that, when executed by processing circuitry of a network node, causes the network node to perform the method of any of claims 1-16.

66. A computer program product comprising a non-transitory computer- readable medium (QQ130, QQ215, QQ390-1, QQ390-2) storing computer readable program code that, when executed by processing circuitry of a wireless device, causes the wireless device to perform the method of any of claims 17-32.

Images