Sign In to Follow Application
View All Documents & Correspondence

Uplink Transmission Scheduling For Wireless Communication Networks

Abstract: A method for uplink scheduling over a communication channel in a communication network (100) including at least one UE (106) and an eNodeB (104), is described. The method comprises determining whether the UE (106) is associated with at least one of Guaranteed Bit Rate (GBR) bearers and non-Guaranteed Bit Rate (non-GBR) bearers. Based on the determining, for each of the GBR-bearers and the non-GBR-bearers, computing a demand for resources for establishing an uplink communication, wherein the demand is computed based physical layer characteristics and transport layer characteristics associated with the communication channel. The demand computed is communicated as a request message to the eNodeB (104). In response to the request message, receiving an allocation of the resources for uplink scheduling from the eNodeB (104).

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
24 July 2013
Publication Number
27/2015
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
iprdel@lakshmisri.com
Parent Application
Patent Number
Legal Status
Grant Date
2021-12-09
Renewal Date

Applicants

TATA CONSULTANCY SERVICES LIMITED
Nirmal Building, 9th Floor, Nariman Point, Mumbai-400021, Maharashtra

Inventors

1. RATH, Hemant Kumar
TATA CONSULTANCY SERVICES ABHILASH BUILDING, PLOT No. 96 EP-IP INDUSTRIAL AREA WHITEFIELD ROAD, BANGALORE-560066
2. SENGUPTA, Munmun
TATA CONSULTANCY SERVICES ABHILASH BUILDING, PLOT No. 96 EP-IP INDUSTRIAL AREA WHITEFIELD ROAD, BANGALORE-560066
3. SIMHA, Anantha
TATA CONSULTANCY SERVICES ABHILASH BUILDING, PLOT No. 96 EP-IP INDUSTRIAL AREA WHITEFIELD ROAD, BANGALORE-560066

Specification

CLIAMS:I/We claim:
1. A method for uplink scheduling over a communication channel in a communication network including at least one User Equipment (UE) (106) and a base station (104), the method comprising:
determining whether the UE (106) is associated with at least one of Guaranteed Bit Rate (GBR) bearers and non-Guaranteed Bit Rate (non-GBR) bearers;
for each of the GBR-bearers and the non-GBR-bearers, computing a demand for resources for establishing an uplink communication, wherein the demand is computed based on physical layer characteristics and transport layer characteristics associated with the communication channel;
communicating the demand as a request message to the base station (104); and
in response to the request message, receiving an allocation of resources for uplink scheduling from the base station (104).
2. The method as claimed in claim 1, wherein the resources are defined by resource blocks.
3. The method as claimed in claim 1, wherein the physical layer characteristics comprise a maximum reported rate.
4. The method as claimed in claim 1, wherein the transport layer characteristics comprise one of Round Trip Time (RTT), congestion window (cwnd) and throughput.
5. The method as claimed in claim 1, wherein the transport layer characteristics are further, based on Transmission Control Protocol (TCP) and User Datagram Protocol (UDP).
6. The method as claimed in claim 1, wherein the request message is communicated to the eNodeB based on one of contention based techniques and polling based techniques.
7. The method as claimed in claim 1, wherein the request message further comprises the computed demand for GBR-bearers, the computed demand for non-GBR-bearers and a quality class indicator (QCI).
8. The method as claimed in claim 2, wherein the receiving an allocation is based on computing the resource blocks to be allocated, the computing further comprising:
for a total number of resource blocks being greater than resource blocks determined in response to the request message, allocating a first number of resource blocks to the GBR-bearers; and
for the remaining number of resource blocks, allocating the resource blocks for non-GBR-bearers based on one of Packet Delay Budget (PDB), priority associated with the UE (106) having the non-GBR-bearers and the number of available resource blocks.
9. An eNodeB (104) for uplink scheduling for a plurality of UEs (106) in communication with the eNodeB (104), the eNodeB (104) comprising:
a processor (202-2); and
a resource allocation module (110) executable by the processor (220-2) to:
based on a demand for resource blocks received from at least one of plurality of UEs (106), determine number of the resource blocks to be allocated for the at least one UE (106);
for Guaranteed Bit Rate (GBR) bearers, allocate resource blocks from a total number of resource blocks;
determine remaining resource blocks from the total number of resource blocks;
allocate remaining resource blocks to non-Guaranteed Bit Rate (non-GBR) based on a Packet Delay Budget (PDB) and a priority associated with the UE (106); and
based on the allocating, assign the resource blocks to the UE (106), for scheduling uplink communication with the at least one UE.
10. The eNodeB (104) as claimed in claim 9, wherein the resource blocks are allocated to the GBR-bearers based on determining whether resource blocks are less than the total number of the resource blocks.
11. The eNodeB (104) as claimed in claim 9, wherein the demand is received in form of request message indicating at least one of a computed demand for resource blocks for GBR-bearers, a computed demand for resource blocks for non-GBR-bearers and a quality class indicator (QCI).
12. The eNodeB (104) as claimed in claim 11, wherein the QCI is further, indicative of the priority associated with the UE (106).
13. The eNodeB (104) as claimed in claim 9, wherein the resource allocation module (110):
for a UE associated with the GBR-bearers and the non-GBR-bearers, determines a proportion of the GBR-bearers; and
on determining resource blocks being greater than the total number of the resource blocks, allocates resource blocks to the GBR-bearers based on the proportion of GBR-bearers.
14. The eNodeB (104) as claimed in claim 9, wherein the allocating further comprises:
determining a PDB value associated with the plurality of UEs (106) in communication with the eNodeB (104);
sorting the UEs (106) based on an ascending order of the PDB value;
allocating the resource blocks for the non-GBR of the UE with the lowest PDB value; and
subsequently, allocating resource blocks for other UEs (106), based on the sorting and based on the available number of resource blocks.
15. The eNodeB (104) as claimed in claim 9, further comprising an assignment module (222) to:
determine the number of resource blocks for which coding efficiency is maximum; and
assign the resource blocks based on the determining.
,TagSPECI:As Attached

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 2464-MUM-2013-RELEVANT DOCUMENTS [26-09-2023(online)].pdf 2023-09-26
1 Sprcification.pdf 2018-08-11
2 PD009516IN-SC_Request+ Form 26.pdf 2018-08-11
2 2464-MUM-2013-IntimationOfGrant09-12-2021.pdf 2021-12-09
3 FORM 5.pdf 2018-08-11
3 2464-MUM-2013-PatentCertificate09-12-2021.pdf 2021-12-09
4 FORM 3.pdf 2018-08-11
4 2464-MUM-2013-US(14)-HearingNotice-(HearingDate-27-11-2020).pdf 2021-10-03
5 Figures.pdf 2018-08-11
5 2464-MUM-2013-Written submissions and relevant documents [07-12-2020(online)].pdf 2020-12-07
6 ABSTRACT.jpg 2018-08-11
6 2464-MUM-2013-Correspondence to notify the Controller [24-11-2020(online)].pdf 2020-11-24
7 2464-MUM-2013-FORM 26(1-1-2014).pdf 2018-08-11
7 2464-MUM-2013-COMPLETE SPECIFICATION [22-08-2019(online)].pdf 2019-08-22
8 2464-MUM-2013-FORM 18.pdf 2018-08-11
8 2464-MUM-2013-FER_SER_REPLY [22-08-2019(online)].pdf 2019-08-22
9 2464-MUM-2013-OTHERS [22-08-2019(online)].pdf 2019-08-22
9 2464-MUM-2013-FORM 1(3-1-2014).pdf 2018-08-11
10 2464-MUM-2013-CORRESPONDENCE(3-1-2014).pdf 2018-08-11
10 2464-MUM-2013-FORM 3 [07-08-2019(online)].pdf 2019-08-07
11 2464-MUM-2013-CORRESPONDENCE(1-1-2014).pdf 2018-08-11
11 2464-MUM-2013-Information under section 8(2) (MANDATORY) [07-08-2019(online)].pdf 2019-08-07
12 2464-MUM-2013-FER.pdf 2019-02-26
13 2464-MUM-2013-CORRESPONDENCE(1-1-2014).pdf 2018-08-11
13 2464-MUM-2013-Information under section 8(2) (MANDATORY) [07-08-2019(online)].pdf 2019-08-07
14 2464-MUM-2013-CORRESPONDENCE(3-1-2014).pdf 2018-08-11
14 2464-MUM-2013-FORM 3 [07-08-2019(online)].pdf 2019-08-07
15 2464-MUM-2013-FORM 1(3-1-2014).pdf 2018-08-11
15 2464-MUM-2013-OTHERS [22-08-2019(online)].pdf 2019-08-22
16 2464-MUM-2013-FER_SER_REPLY [22-08-2019(online)].pdf 2019-08-22
16 2464-MUM-2013-FORM 18.pdf 2018-08-11
17 2464-MUM-2013-COMPLETE SPECIFICATION [22-08-2019(online)].pdf 2019-08-22
17 2464-MUM-2013-FORM 26(1-1-2014).pdf 2018-08-11
18 2464-MUM-2013-Correspondence to notify the Controller [24-11-2020(online)].pdf 2020-11-24
18 ABSTRACT.jpg 2018-08-11
19 2464-MUM-2013-Written submissions and relevant documents [07-12-2020(online)].pdf 2020-12-07
19 Figures.pdf 2018-08-11
20 FORM 3.pdf 2018-08-11
20 2464-MUM-2013-US(14)-HearingNotice-(HearingDate-27-11-2020).pdf 2021-10-03
21 FORM 5.pdf 2018-08-11
21 2464-MUM-2013-PatentCertificate09-12-2021.pdf 2021-12-09
22 PD009516IN-SC_Request+ Form 26.pdf 2018-08-11
22 2464-MUM-2013-IntimationOfGrant09-12-2021.pdf 2021-12-09
23 Sprcification.pdf 2018-08-11
23 2464-MUM-2013-RELEVANT DOCUMENTS [26-09-2023(online)].pdf 2023-09-26

Search Strategy

1 2019-02-2611-44-08_26-02-2019.pdf

ERegister / Renewals

3rd: 15 Dec 2021

From 24/07/2015 - To 24/07/2016

4th: 15 Dec 2021

From 24/07/2016 - To 24/07/2017

5th: 15 Dec 2021

From 24/07/2017 - To 24/07/2018

6th: 15 Dec 2021

From 24/07/2018 - To 24/07/2019

7th: 15 Dec 2021

From 24/07/2019 - To 24/07/2020

8th: 15 Dec 2021

From 24/07/2020 - To 24/07/2021

9th: 15 Dec 2021

From 24/07/2021 - To 24/07/2022

10th: 01 Jul 2022

From 24/07/2022 - To 24/07/2023

11th: 04 Jul 2023

From 24/07/2023 - To 24/07/2024

12th: 12 Jul 2024

From 24/07/2024 - To 24/07/2025

13th: 09 Jul 2025

From 24/07/2025 - To 24/07/2026