Source: http://patentsgazette.uspto.gov/week51/OG/html/1469-3/US10512071-20191217.html
Timestamp: 2020-02-24 08:46:01
Document Index: 684931879

Matched Legal Cases: ['application No. 16', 'application No. 15', 'application No. 15', 'application No. 15', 'application No. 14', 'application No. 13', 'application No. 2009', 'application No. 2009']

US 10,512,071 B2
Base station device, terminal device and communication method
Seigo Nakao, Singapore (SG); and Daichi Imamura, Beijing (CN)
Assigned to Godo Kaisha IP Bridge 1, Tokyo (JP)
Filed by Godo Kaisha IP Bridge 1, Tokyo (JP)
Filed on Feb. 27, 2019, as Appl. No. 16/287,346.
Application 16/287,346 is a continuation of application No. 16/011,339, filed on Jun. 18, 2018, granted, now 10,257,822.
Application 16/011,339 is a continuation of application No. 15/667,566, filed on Aug. 2, 2017, granted, now 10,028,268, issued on Jul. 17, 2018.
Application 15/667,566 is a continuation of application No. 15/439,159, filed on Feb. 22, 2017, granted, now 9,756,634, issued on Sep. 5, 2017.
Application 15/439,159 is a continuation of application No. 15/186,129, filed on Jun. 17, 2016, granted, now 9,641,302, issued on May 2, 2017.
Application 15/186,129 is a continuation of application No. 14/818,612, filed on Aug. 5, 2015, granted, now 9,397,809, issued on Jul. 19, 2016.
Application 14/818,612 is a continuation of application No. 13/377,348, granted, now 9,136,985, issued on Sep. 15, 2015, previously published as PCT/JP2010/004099, filed on Jun. 18, 2010.
Claims priority of application No. 2009-146592 (JP), filed on Jun. 19, 2009; and application No. 2009-252051 (JP), filed on Nov. 2, 2009.
Prior Publication US 2019/0200329 A1, Jun. 27, 2019
Int. Cl. H04W 24/04 (2009.01); H04W 72/04 (2009.01); H04W 76/28 (2018.01); H04L 1/16 (2006.01); H04L 1/18 (2006.01); H04L 5/00 (2006.01); H04W 74/00 (2009.01); H04J 13/00 (2011.01); H04W 28/04 (2009.01); H04W 88/08 (2009.01); H04W 84/04 (2009.01)
CPC H04W 72/042 (2013.01) [H04L 1/1621 (2013.01); H04L 1/18 (2013.01); H04L 1/1861 (2013.01); H04L 1/1864 (2013.01); H04L 5/001 (2013.01); H04L 5/0048 (2013.01); H04L 5/0053 (2013.01); H04L 5/0055 (2013.01); H04W 72/0413 (2013.01); H04W 72/0453 (2013.01); H04W 74/004 (2013.01); H04W 76/28 (2018.02); H04J 13/0062 (2013.01); H04W 28/04 (2013.01); H04W 84/042 (2013.01); H04W 88/08 (2013.01)] 8 Claims
1. A terminal apparatus configured to communicate with a base station using a plurality of downlink component carriers, including a primary component carrier and a non-primary component carrier, and an uplink component carrier, the terminal apparatus comprising:
an extractor which, in operation, extracts a downlink control channel signal from a received signal and extracts downlink data from the received signal based on information on downlink data allocation resources;
a decider which, in operation, makes a blind decision as to whether or not control information is control information directed to the terminal apparatus, outputs the information on downlink data allocation resources for the terminal apparatus included in the control information directed to the terminal apparatus to the extractor, and identifies a Control Channel Element (CCE) to which the control information directed to the terminal apparatus is mapped;
a receiver which, in operation, receives the downlink data transmitted through at least one downlink data channel of the plurality of downlink component carriers;
an error detector which, in operation, detects presence or absence of a reception error of the received downlink data; and
a controller which, in operation, determines which Physical Uplink Control Channel (PUCCH) resource is used to transmit a response signal and which constellation point is set for the response signal based on success or failure in reception of a downlink allocation control signal in each downlink component carrier and error detection results from the error detector;
wherein when the error detection result regarding downlink data transmitted in the primary component carrier shows “no error” and a downlink allocation control signal is not detected in the non-primary component carrier, the controller transmits the response signal using a first PUCCH resource corresponding to the CCE identified by the decider.