Abstract: Examples include techniques for using a modulation and coding scheme (MCS) for downlink transmissions. In some examples information elements (IEs) for either a physical multicast channel (PMCH) or a physical multicast control channel (PMCCH) include information to indicate an MCS for downlink transmission over a PMCH or PMCCH between an evolved Node B (eNB) and user equipment (UE). For these examples the information in the IEs include indications of whether higher order modulation for quadrature amplitude modulation (QAM) have or have not been enabled. Both the UE and the eNB may operate in compliance with one or more 3 Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards.
CLAIMS
What is claimed is:
1. An apparatus comprising:
a processor circuit for an evolved Node B (eNB);
an enable component for execution by the processor circuit to generate a physical multicast channel-InfoList (PMCH-InfoList) information element (IE) that includes a field indicating whether 256 quadrature amplitude modulation (256QAM) is enabled for downlink transmissions to one or more user equipment (UEs) over a PMCH;
a send component for execution by the processor circuit to cause the PMCH-InfoList IE to be sent to the one or more UEs; and
a select component for execution by the processor circuit to select a value for a dataMCS field of the PMCH-InfoList IE that indicates a first modulation coding scheme (MCS) to use for the downlink transmissions to the one or more UEs over the PMCH, the value based on whether 256QAM is enabled.
2. The apparatus of claim 3, comprising:
a control information component for execution by the processor circuit to generate a multi-broadcast multicast service-ArealnfoList (MBMS-ArealnfoList) IE that includes information in a signallingMCS field to indicate a second MCS to use for downlink transmissions to the one or more UEs over a physical multicast control channel (PMCCH); and
the send component to cause the MBMSArealnfoList IE to be sent to the one or more UEs.
3. The apparatus of claim 4, the second MCS is the same as the first MCS.
4. The apparatus of claim 1, the enable component to generate the PMCH-InfoList IE according to a first 3GPP technical specification (TS) to include TS 36.331, the value selected for the dataMCS field by the select component to indicate the first MCS to use comprises an MCS index value for a first modulation and transport block size (TBS) index table for physical downlink shared channel (PDSCH) included in a second 3GPP TS to include TS 36.213 or for a second modulation and TBS index table for PDSCH also included in TS 36.213.
5. The apparatus of claim 4, the enable component to cause the field indicating whether
256QAM is enabled to indicate that 256QAM is not enabled, the one or more UEs arranged to determine the first MCS to use for the downlink transmissions that includes a modulation order of less than or equal to 6 based on the first modulation and TBS index table and the MCS index value.
6. The apparatus of claim 4, the enable component to cause the field indicating whether 256QAM is enabled to indicate that 256QAM is enabled, the one or more UEs arranged to determine the first MCS to use for the downlink transmissions that includes a modulation order of at least 8 based on the second modulation and TBS index table and the MCS index value.
7. The apparatus of claim 1, comprising:
a control information component for execution by the processor circuit to generate a multi-broadcast multicast service-ArealnfoList (MBMS-ArealnfoList) IE that includes information in a signallingMCS field to indicate a second MCS to use for downlink transmissions to the one or more UEs over a physical multicast control channel (PMCCH); and
the send component to cause the MBMSArealnfoList IE to be sent to the one or more UEs.
8. The apparatus of claim 7, the second MCS is the same as the first MCS.
9. A method comprising:
generating, at an evolved Node B (eNB) capable of operating in compliance with one or more 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards including LTE-Advanced (LTE-A), a physical multicast channel-InfoList (PMCH-InfoList) information element (IE) that includes a field indicating whether 256 quadrature amplitude modulation (256QAM) is enabled for downlink transmissions to one or more user equipment (UEs) over a PMCH;
selecting a value for a dataMCS field of the PMCH-InfoList IE that indicates a first modulation coding scheme (MCS) to use for the downlink transmissions to the one or more UEs over the PMCH, the value based on whether 256QAM is enabled; and
sending the PMCH-InfoList IE to the one or more UEs.
10. The method of claim 9, comprising:
generating, at the eNB, a multi-broadcast multicast service-ArealnfoList (MBMS-
ArealnfoList) IE that includes information in a signallingMCS field to indicate a second MCS to use for downlink transmissions to the one or more UEs over a physical multicast control channel (PMCCH); and
sending the MBMSArealnfoList IE to the one or more UEs.
11. The method of claim 10, the second MCS is the same as the first MCS.
12. The method of claim 9, generating the PMCH-InfoList IE according to a first 3GPP technical specification (TS) to include TS 36.33 1, the value selected for the dataMCS field that indicates the first MCS to use comprises an MCS index value for a first modulation and transport block size (TBS) index table for physical downlink shared channel (PDSCH) included in a second 3GPP TS to include TS 36.213 or for a second modulation and TBS index table for PDSCH also included in TS 36.213.
13. The method of claim 12, comprising:
the field indicating whether 256QAM is enabled indicates that 256QAM is not enabled; and
using the first modulation and TBS index table and the MCS index value to determine the first MCS to use for the downlink transmissions that includes a TBS index of less than or equal to 26.
14. The method of claim 12, comprising:
the field indicating whether 256QAM is enabled indicates that 256QAM is enabled; and using the second modulation and TBS index table and the MCS index value to determine the first MCS to use for the downlink transmissions that includes a TBS index of at least 25.
15. At least one machine readable medium comprising a plurality of instructions that in response to being executed on a system at an evolved Node B (eNB) cause the system to carry out a method according to any one of claims 9 to 14.
16. At least one machine readable medium comprising a plurality of instructions that in response to being executed on a system for an evolved Node B (eNB) capable of operating in compliance with one or more or more 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards including LTE-Advanced (LTE-A), causes the system to:
generate a physical multicast channel-InfoList (PMCH-InfoList) information element (IE) that includes a field indicating whether 256 quadrature amplitude modulation (256QAM) is enabled for downlink transmissions to one or more user equipment (UEs) over a PMCH;
select a value for a dataMCS field of the PMCH-InfoList IE that indicates a first modulation coding scheme (MCS) to use for the downlink transmissions to the one or more UEs over the PMCH, the value based on whether 256QAM is enabled; and
send the PMCH-InfoList IE to the one or more UEs.
17. The at least one machine readable medium of claim 16, the instructions to further cause
the system to:
generate a multi-broadcast multicast service-ArealnfoList (MBMS-ArealnfoList) IE that includes information in a signallingMCS field to indicate a second MCS to use for downlink transmissions to the one or more UEs over a physical multicast control channel (PMCCH); and
send the MBMSArealnfoList IE to the one or more UEs.
18. The at least one machine readable medium of claim 16, the instructions to cause the system to generate the PMCH-InfoList IE according to a first 3GPP technical specification (TS) to include TS 36.33 1, the value selected for the dataMCS field that indicates the first MCS to use comprises an MCS index value for a first modulation and transport block size (TBS) index table for physical downlink shared channel (PDSCH) included in a second 3GPP TS to include TS 36.213 or for a second modulation and TBS index table for PDSCH also included in TS 36.213.
19. The at least one machine readable medium of claim 18, comprising the instructions to cause the system to cause the field indicating whether 256QAM is enabled to indicate that 256QAM is not enabled, the one or more UEs arranged to determine the first MCS to use for the downlink transmissions a modulation order of less than or equal to 6 based on the first modulation and TBS index table and the MCS index value.
20. The at least one machine readable medium of claim 18, comprising the instructions to cause the system to cause the field indicating whether 256QAM is enabled to indicate that 256QAM is enabled, the one or more UEs arranged to determine the first MCS to use for the downlink transmissions a modulation order of at least 8 based on the first modulation and TBS index table and the MCS index value.
21. An apparatus comprising:
a processor circuit for user equipment (UE) capable of operating in compliance with one or more 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards including LTE-Advanced (LTE-A);
a receive component for execution by the processor circuit to receive a physical multicast channel-InfoList (PMCH-InfoList) information element (IE) from one or more evolved Node B (eNBs) that includes a field indicating whether 256 quadrature amplitude modulation (256QAM) is enabled for receiving downlink transmissions over a PMCH from the one or more eNBs;
an enable component for execution by the processor circuit to determine whether 256QAM is enabled;
a determine component for execution by the processor circuit to determine a first modulation coding scheme (MCS) to use for receiving downlink transmissions over the PMCH based on a value indicated in a dataMCS field of the PMCH-InfoList IE and based on whether 256QAM is determined to be enabled; and
an MCS component for execution by the processor circuit to use the first MCS to receive the downlink transmissions over the PMCH from the one or more eNBs.
22. The apparatus of claim 21, comprising:
the receive component to receive a multi-broadcast multicast service-ArealnfoList (MBMS-ArealnfoList) IE that includes information in a signallingMCS field that indicates a second MCS to use for receiving downlink transmissions from the one or more eNBs over a physical multicast control channel (PMCCH); and
the MCS component to use the second MCS to receive the downlink transmissions over the PMCCH from the one or more eNBs.
23. The apparatus of claim 21, the PMCH-InfoList IE generated by the one or more eNBs according to a first 3GPP technical specification (TS) to include TS 36.33 1, the value indicated in the dataMCS field comprises an MCS index value for a first modulation and transport block size (TBS) index table for physical downlink shared channel (PDSCH) included in a second 3GPP TS to include TS 36.213 or for a second modulation and TBS index table for PDSCH also included in TS 36.213.
24. The apparatus of claim 23, comprising:
the field indicating whether 256QAM is enabled indicates that 256QAM is not enabled;
and
the determine component to use the first modulation and TBS index table and the MCS index value to determine the first MCS to use for receiving the downlink transmissions over the PMCH, the first MCS including a modulation order of less than or equal to 6.
25. The apparatus of claim 23, comprising:
the field indicating whether 256QAM is enabled indicates that 256QAM is enabled; and the determine component to use the second modulation and TBS index table and the MCS index value to determine the first MCS to use for receiving the downlink transmissions over the PMCH, the first MCS including a modulation order of at least 8.
| Section | Controller | Decision Date |
|---|---|---|
| U/S 15 & 43(1) | Jeetendra Singh | 2023-09-15 |
| U/S 15 & 43(1) | Jeetendra Singh | 2023-09-15 |
| # | Name | Date |
|---|---|---|
| 1 | 201647034560-IntimationOfGrant15-09-2023.pdf | 2023-09-15 |
| 1 | Priority Document [08-10-2016(online)].pdf | 2016-10-08 |
| 2 | 201647034560-PatentCertificate15-09-2023.pdf | 2023-09-15 |
| 2 | Form 5 [08-10-2016(online)].pdf | 2016-10-08 |
| 3 | Drawing [08-10-2016(online)].pdf | 2016-10-08 |
| 3 | 201647034560-FORM 3 [23-08-2023(online)].pdf | 2023-08-23 |
| 4 | Description(Complete) [08-10-2016(online)].pdf | 2016-10-08 |
| 4 | 201647034560-Written submissions and relevant documents [23-08-2023(online)].pdf | 2023-08-23 |
| 5 | Form 18 [14-10-2016(online)].pdf | 2016-10-14 |
| 5 | 201647034560-Correspondence to notify the Controller [24-07-2023(online)].pdf | 2023-07-24 |
| 6 | 201647034560.pdf | 2016-10-14 |
| 6 | 201647034560-US(14)-HearingNotice-(HearingDate-14-08-2023).pdf | 2023-07-13 |
| 7 | Form-18(Online).pdf | 2016-10-17 |
| 7 | 201647034560-Annexure [27-09-2019(online)].pdf | 2019-09-27 |
| 8 | Form 26 [26-10-2016(online)].pdf | 2016-10-26 |
| 8 | 201647034560-CLAIMS [27-09-2019(online)].pdf | 2019-09-27 |
| 9 | 201647034560-FER_SER_REPLY [27-09-2019(online)].pdf | 2019-09-27 |
| 9 | Form 3 [04-11-2016(online)].pdf | 2016-11-04 |
| 10 | 201647034560 - Form 3 - 04-11-16.pdf | 2016-11-11 |
| 10 | 201647034560-Information under section 8(2) (MANDATORY) [27-09-2019(online)].pdf | 2019-09-27 |
| 11 | 201647034560 - Form 2 (TItle Page) - 08-10-16.pdf | 2016-11-11 |
| 11 | 201647034560-OTHERS [27-09-2019(online)].pdf | 2019-09-27 |
| 12 | 201647034560 - Discription Complete - 08-10-16.pdf | 2016-11-11 |
| 12 | 201647034560-PETITION UNDER RULE 137 [27-09-2019(online)].pdf | 2019-09-27 |
| 13 | 201647034560 - Claims - 08-10-16.pdf | 2016-11-11 |
| 13 | Correspondence by Agent_Proof of Right_27-09-2019.pdf | 2019-09-27 |
| 14 | 201647034560-Proof of Right (MANDATORY) [25-09-2019(online)].pdf | 2019-09-25 |
| 14 | Other Document [20-12-2016(online)].pdf | 2016-12-20 |
| 15 | 201647034560-FORM 3 [04-09-2019(online)].pdf | 2019-09-04 |
| 15 | Marked Copy [20-12-2016(online)].pdf | 2016-12-20 |
| 16 | 201647034560-FER.pdf | 2019-03-29 |
| 16 | Form 13 [20-12-2016(online)].pdf | 2016-12-20 |
| 17 | Form 13 [20-12-2016(online)].pdf | 2016-12-20 |
| 17 | 201647034560-FER.pdf | 2019-03-29 |
| 18 | 201647034560-FORM 3 [04-09-2019(online)].pdf | 2019-09-04 |
| 18 | Marked Copy [20-12-2016(online)].pdf | 2016-12-20 |
| 19 | 201647034560-Proof of Right (MANDATORY) [25-09-2019(online)].pdf | 2019-09-25 |
| 19 | Other Document [20-12-2016(online)].pdf | 2016-12-20 |
| 20 | 201647034560 - Claims - 08-10-16.pdf | 2016-11-11 |
| 20 | Correspondence by Agent_Proof of Right_27-09-2019.pdf | 2019-09-27 |
| 21 | 201647034560 - Discription Complete - 08-10-16.pdf | 2016-11-11 |
| 21 | 201647034560-PETITION UNDER RULE 137 [27-09-2019(online)].pdf | 2019-09-27 |
| 22 | 201647034560 - Form 2 (TItle Page) - 08-10-16.pdf | 2016-11-11 |
| 22 | 201647034560-OTHERS [27-09-2019(online)].pdf | 2019-09-27 |
| 23 | 201647034560 - Form 3 - 04-11-16.pdf | 2016-11-11 |
| 23 | 201647034560-Information under section 8(2) (MANDATORY) [27-09-2019(online)].pdf | 2019-09-27 |
| 24 | Form 3 [04-11-2016(online)].pdf | 2016-11-04 |
| 24 | 201647034560-FER_SER_REPLY [27-09-2019(online)].pdf | 2019-09-27 |
| 25 | Form 26 [26-10-2016(online)].pdf | 2016-10-26 |
| 25 | 201647034560-CLAIMS [27-09-2019(online)].pdf | 2019-09-27 |
| 26 | Form-18(Online).pdf | 2016-10-17 |
| 26 | 201647034560-Annexure [27-09-2019(online)].pdf | 2019-09-27 |
| 27 | 201647034560.pdf | 2016-10-14 |
| 27 | 201647034560-US(14)-HearingNotice-(HearingDate-14-08-2023).pdf | 2023-07-13 |
| 28 | Form 18 [14-10-2016(online)].pdf | 2016-10-14 |
| 28 | 201647034560-Correspondence to notify the Controller [24-07-2023(online)].pdf | 2023-07-24 |
| 29 | Description(Complete) [08-10-2016(online)].pdf | 2016-10-08 |
| 29 | 201647034560-Written submissions and relevant documents [23-08-2023(online)].pdf | 2023-08-23 |
| 30 | Drawing [08-10-2016(online)].pdf | 2016-10-08 |
| 30 | 201647034560-FORM 3 [23-08-2023(online)].pdf | 2023-08-23 |
| 31 | 201647034560-PatentCertificate15-09-2023.pdf | 2023-09-15 |
| 31 | Form 5 [08-10-2016(online)].pdf | 2016-10-08 |
| 32 | 201647034560-IntimationOfGrant15-09-2023.pdf | 2023-09-15 |
| 32 | Priority Document [08-10-2016(online)].pdf | 2016-10-08 |
| 1 | Search_201647034560_PIPII_4_06-02-2019.pdf |