Source: http://patents.com/us-10129798.html
Timestamp: 2019-04-21 04:21:41
Document Index: 408505329

Matched Legal Cases: ['Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61']

US Patent # 1,012,9798. Carrier configuration in wireless networks - Patents.com
United States Patent 10,129,798
Dinan November 13, 2018
Methods and apparatuses are described for wireless communications. Cells may be grouped into a plurality of cell groups. A handover of a wireless device may be performed, and one or more configuration parameters of a cell associated with the wireless device may be maintained.
Family ID: 1000003649725
15/645,573
US 20170311213 A1 Oct 26, 2017
14929411 Nov 2, 2015 9706454
13920009 Jun 17, 2013 9179457
15645573 Jul 10, 2017
14822628 Aug 10, 2015 9894640
14824132 Aug 12, 2015
13919980 Jun 17, 2013 9113387
15201528 Jul 4, 2016 9843982
14959273 Dec 4, 2015 9386490
13919993 Jun 17, 2013 9210619
61678989 Aug 2, 2012
61679103 Aug 3, 2012
Current CPC Class: H04W 36/0077 (20130101); H04W 72/042 (20130101); H04W 56/0045 (20130101); H04W 36/0072 (20130101)
Current International Class: H04J 3/00 (20060101); H04W 36/00 (20090101); H04W 72/04 (20090101); H04W 56/00 (20090101)
Field of Search: ;370/329,336
8553574 October 2013 Hsu
8761047 June 2014 Kim et al.
8774819 July 2014 Zhang et al.
8804630 August 2014 Ito et al.
8917605 December 2014 Pelletier et al.
8995462 March 2015 Kim et al.
9344985 May 2016 Loehr et al.
9408162 August 2016 Ho et al.
9706454 July 2017 Dinan
9717061 July 2017 Dinan
2012/0026977 February 2012 Kim et al.
2012/0113883 May 2012 Sterling
2014/0161089 June 2014 Ahn et al.
2015/0296542 October 2015 Heo et al.
3GPP TSG-RAN WG2 Meeting #72bis, Tdoc R2-110356 Dublin, Ireland, Jan. 17-21, 2011 Source: ITRI Title: RF Receiver Information in UE Capability Signalling. cited by applicant .
3GPP TSG-RAN WG2 Meeting #77 Tdoc R2-120166 Feb. 6-10, 2012, Dresden, Germany Source: ITRI Title: Deactivation of DL Timing Reference in sTAG. cited by applicant .
3GPP TSG-RAN2 #77 meeting Tdoc R2-120221 Dresden, Germany, Feb. 6-10, 2012 Source: MediaTek Title: Discussion on timing reference in sTAG. cited by applicant .
TSG-RAN WG2 #77 R2-120604 Dresden, Germany, Feb. 6-10, 2012 Title: Pathloss reference for SCell TA group and need of RLM Source: Alcatel-Lucent, Alcatel-Lucent Shanghai Bell. cited by applicant .
TSG-RAN WG2 #77 R2-120605 Feb. 6-10, 2012, Dresden, Germany Title: Timing reference for SCell TA group Source: Alcatel-Lucent, Alcatel-Lucent Shanghai Bell. cited by applicant .
3GPP TSG-RAN WG2 #77 R2-120821 Feb. 6-10, 2012, Dresden, Germany Source: Intel Corporation Title: Remaining pen issues on timing and pathloss reference for sTAG. cited by applicant .
3GPP TSG RAN WG2#77bis R2-121398 Jeju Island, Korea, Mar. 26-30, 2012 Source: Samsung Title: Whether to allow configurable pathloss reference in STAG? cited by applicant .
3GPP TSG-RAN WG2 Meeting #77bis Tdoc R2-121530 Mar. 26-30, 2012, Jeju, Korea Source: ITRI Title: Deactivation of Timing Reference SCell in sTAG. cited by applicant .
3GPP TSG-RAN WG2 #77bis Tdoc R2-121557 Jeju, Korea, Mar. 26-30, 2012 Source: Ericsson Title: Summary of email discussion [77#26] LTE: CA: Timing reference for SCell-only TA groups. cited by applicant .
TSG-RAN WG2 #77bis R2-121690 Mar. 26-30, 2012 Jeju, Korea Title: Timing reference for SCell TA group Source: Alcatel-Lucent, Alcatel-Lucent Shanghai Bell. cited by applicant .
TSG-RAN WG2 #75bis R2-115338 Oct. 10-14, 2011, Zhuhai, China Title: RACH on SCell Source: Alcatel-Lucent, Alcatel-Lucent Shanghai Bell. cited by applicant .
3GPP TSG-RAN WG2 #77bis meeting R2-121712, Jeju, Korea, Mar. 26-30, 2012, Source: Samsung, Title: Timing reference for sTAG. cited by applicant .
3GPP TSG-RAN WG2 #76 Tdoc R2-115743 San Francisco, United States, Nov. 14-18, 2011 Source: Ericsson, ST Ericsson Title: Random Access Response on an SCell. cited by applicant .
3GPP TSG-RAN2 #76 meeting Tdoc R2-116340 San Francisco. USA, Nov. 14-18, 2011, Source: HTC Title: TA group configuration and reconfiguration. cited by applicant .
3GPP TSG-RAN2 #78 meeting Tdoc R2-122240 May 21-25, 2012, Prague, Czech Republic Source: ZTE Corporation Title: UE capability report for MTA. cited by applicant .
3GPP TSG-RAN2 #78 R2-122386 Prague, Czech Republic, May 21-25, 2012 Source: NTT Docomo, Inc. Title: SCell status at TAG change. cited by applicant .
3GPP TSG-RAN WG2 #78 R2-122454 Prague, Czech Republic, May 21-25, 2012 Source: Sharp Title: Remaining issues of TA group handling. cited by applicant .
TSG-RAN WG2 #78 R2-1212738 Prague, Czech Republic, May 21-25, 2012 Title: TAG related signalling Source: Alcatel-Lucent, Alcatel-Lucent Shanghai Bell. cited by applicant .
3GPP TSG RAN WG1 Meeting #66bis R1-113187 Zhuhai, China, Oct. 10-14, 2011 Source: LG Electronics Title: Discussion on Simultaneous Uplink Channel Transmission in Rel-11. cited by applicant .
3GPP TSG RAN WG1 Meeting #66bis R1-113314 Zhuhai, China, Oct. 10-14, 2011 Source: Alcatel-Lucent, Alcatel-Bell Shanghai Bell Title: Multiple Timing Advances for Carrier Aggregation. cited by applicant .
3GPP TSG RAN WG2 Meeting #74 R2-112815 Barcelona, Spain, May 9-13, 2011 Source: CATT Title: RA Procedure or Multi-TA. cited by applicant .
3GPP TSG-RAN WG2 #74 R2-113050 Barcelona, Spain, May 9-13, 2011 Source: Sharp Title: Considerations for RACH initiation on SCell. cited by applicant .
3GPP TSG-RAN WG2 meeting #74 R2-113063 Barcelona, Spain, May 9-13, 2011 'Source: Qualcomm Incorporated Title: Consideration on multiple TA. cited by applicant .
3GPP TSG-RAN2 #73bis meeting Tdoc R2-113101 Barcelona, Spain, May 9-13, 2011 Source: MediaTek Title: Grouping of multi-TA. cited by applicant .
3GPP TSG-RAN2 #74 meeting R2-113124 Barcelona, Spain, May 9-13, 2011 Source: Samsung Title: Further discussions of Issues with Multiple-TA. cited by applicant .
3GPP TSG RAN2 #74 meeting R2-113215 Barcelona, Spain, May 9-13, 2011 Source: Intel Corporation Title: Configuration of multiple TA in Rel-11 CA. cited by applicant .
TSG-RAN WG2 #74 R2-113235 May 9-13, 2011, Barcelona, Spain Title: Initiating timing alignment for SCell in multiple TA Source: Alcatel-Lucent, Alcatel-Lucent Shanghai Bell. cited by applicant .
3GPP TSG-RAN WG2 #74 R2-113241 May 9-13, 2011, Barcelona, Spain Source: Motorola Mobility Title: Considerations for Supporting Multiple Timing Advances. cited by applicant .
3GPP TSG RAN WG1 #68 R1-120918 Dresden, Germany, Feb. 6-10, 2012 Proposal on PUSCH/PUCCH transmission with multiple TA LG Electronics, Panasonic, Ericsson, ST-Ericsson, Pantech, Texas Instruments. cited by applicant .
3GPP TSG-RAN2 #73bis meeting Tdoc R2-113102 Barcelona, Spain, May 9-13, 2011 Source: MediaTek Title: Transmission of SCell RACH. cited by applicant .
3GPP TSG-RAN2 #77bis Meeting Tdoc R2-121347 Jeju, Korea, Mar. 26-30, 2012 Source: MediaTek Inc. Title: Discussions on SCell RA procedure when reaching PREAMBLE_TRAN_MAX. cited by applicant .
3GPP TSG RAN WG2 #77bis R2-121404 Jeju Island, Korea, Mar. 26-30, 2012 Source: Samsung Title: Remaining issue on random access failure for SCell. cited by applicant .
3GPP TSG-RAN WG2 Meeting #77bis R2-121799 Jeju, Korea, Mar. 26-30, 2012 Source: Fujitsu Title: Reaching PREAMBLE_TRANS_MAX. cited by applicant .
Sep. 19, 2017--European Search Report--EP 17153540.4. cited by applicant .
Mar. 28, 2018--European Office Action--EP 13703256.1. cited by applicant .
3GPP TSG RAN WG2 Meeting #80 R2-125578 New Orleans, USA, Nov. 12-Nov. 16, 2012 Source: CATT Title: Multi-TA Capability. cited by applicant .
3GPP TSG RAN WG2 Meeting #77bis R2-124764 Bratislava, Slovakia, Oct. 8-12, 2012 Source: CATT Title: Consideration on Mulit-TA Capability. cited by applicant .
3GPP TSG-RAN WG2 Meeting #77bis R2-121456 Jeju, Korea, Mar. 26-30, 2012 Source: Huawei, HiSilicon Title: Parallel transmission in the same TAG. cited by applicant .
Apr. 20, 2018--European Search Report--EP 17189302.7. cited by applicant.
This application is a continuation of U.S. application Ser. No. 14/929,411, filed Nov. 2, 2015, which is a continuation of U.S. application Ser. No. 13/920,009, filed Jun. 17, 2013 (now U.S. Pat. No. 9,179,457, issued Nov. 3, 2015), which claims the benefit of U.S. Provisional Application No. 61/662,191, filed Jun. 20, 2012, and U.S. Provisional Application No. 61/680,544, filed Aug. 7, 2012; this application is a continuation of U.S. application Ser. No. 14/822,628, filed Aug. 10, 2015, which is a continuation of U.S. application Ser. No. 13/920,012, filed Jun. 17, 2013 (now U.S. Pat. No. 9,107,206, issued Aug. 11, 2015), which claims the benefit of U.S. Provisional Application No. 61/661,329, filed Jun. 18, 2012, and U.S. Provisional Application No. 61,680,544, filed Aug. 7, 2012; this application is a continuation of U.S. application Ser. No. 14/824,132, filed Aug. 12, 2015, which is a continuation of U.S. application Ser.No. 13/919,980, filed Jun. 17, 2013 (now U.S. Pat. No. 9,113,387, issued Aug. 18, 2015), which claims the benefit of U.S. Provisional Application No. 61/662,191, filed Jun. 20, 2012, and U.S. Provisional Application No. 61/678,989, filed Aug. 2, 2012; and this application is a continuation of U.S. application Ser.No. 15/201,528, filed Jul. 4, 2016, which is a continuation of U.S. application Ser. No. 14/959,273, filed Dec. 4, 2015 (now U.S. Pat. No. 9,386,490, issued Jul. 5, 2016), which is a continuation of U.S. application Ser.No. 13/919,993, filed Jun. 17, 2013 (now U.S. Pat. No. 9,210,619, issued Dec. 8, 2015), which claims the benefit of U.S. Provisional Application No. 61/662,191, filed Jun. 20, 2012, and U.S. Provisional Application No. 61/679,103, filed Aug. 3, 2012, all of the above of which are hereby incorporated by reference in their entirety.
1. A base station comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the base station to: transmit, to a wireless device, at least one first control message comprising configuration parameters of a plurality of cells grouped into a plurality of cell groups comprising a first cell group and a second cell group, wherein: transmission timing associated with uplink transmissions in the first cell group is based on a first cell of the first cell group; and transmission timing associated with uplink transmissions in the second cell group is based on a second cell of the second cell group; determine to perform a handover of the wireless device; and transmit a second control message configured to, for a cell associated with the wireless device, cause a cell grouping modification from the first cell group to the second cell group, wherein one or more configuration parameters of the cell are maintained during the cell grouping modification, and wherein the second control message comprises mobility control information.
2. The base station of claim 1, wherein the instructions, when executed by the one or more processors, further cause the base station to initiate the handover of the wireless device from the base station to a second base station.
3. The base station of claim 1, wherein the instructions, when executed by the one or more processors, further cause the base station to initiate the handover of the wireless device from a first sector of the base station to a second sector of the base station.
4. The base station of claim 1, wherein the at least one first control message comprises a timer value for a time alignment timer for each of the plurality of cell groups.
5. The base station of claim 1, wherein the second control message is a radio resource control connection reconfiguration message.
6. The base station of claim 1, wherein the instructions, when executed by the one or more processors, further cause the base station to transmit a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to explicitly release a secondary cell as part of a cell grouping modification, for the secondary cell and from the second cell group to the first cell group.
7. The base station of claim 1, wherein the instructions, when executed by the one or more processors, further cause the base station to transmit a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to cause a cell grouping modification, for a secondary cell and from the second cell group to the first cell group, by: releasing the secondary cell; and associating the secondary cell with a different cell group index.
8. The base station of claim 1, wherein the first cell group comprises a primary cell and at least one secondary cell.
9. The base station of claim 8, wherein the second cell group comprises secondary cells.
10. The base station of claim 1, wherein the second control message does not comprise an information element releasing the cell.
11. The base station of claim 1, wherein the second control message further comprises an indication of a random access preamble.
12. A wireless device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: receive, from a base station, at least one first control message comprising configuration parameters of a plurality of cells grouped into a plurality of cell groups comprising a first cell group and a second cell group, wherein: transmission timing associated with uplink transmissions in the first cell group is based on a first cell of the first cell group; and transmission timing associated with uplink transmissions in the second cell group is based on a second cell of the second cell group; receive a second control message configured to, for a cell associated with the wireless device, cause a cell grouping modification from the first cell group to the second cell group, wherein one or more configuration parameters of the cell are maintained during the cell grouping modification, and wherein the second control message comprises mobility control information; and perform, based on the second control message, a handover.
13. The wireless device of claim 12, wherein the handover is from the base station to a second base station.
14. The wireless device of claim 12, wherein the handover is from a first sector of the base station to a second sector of the base station.
15. The wireless device of claim 12, wherein the at least one first control message comprises a timer value for a time alignment timer for each of the plurality of cell groups.
16. The wireless device of claim 12, wherein the second control message is a radio resource control connection reconfiguration message.
17. The wireless device of claim 12, wherein the instructions, when executed by the one or more processors, further cause the wireless device to receive a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to explicitly release a secondary cell as part of a cell grouping modification, for the secondary cell and from the second cell group to the first cell group.
18. The wireless device of claim 12, wherein the instructions, when executed by the one or more processors, further cause the wireless device to receive a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to cause a cell grouping modification, for a secondary cell and from the second cell group to the first cell group, by: releasing the secondary cell; and associating the secondary cell with a different cell group index.
19. The wireless device of claim 12, wherein the first cell group comprises a primary cell and at least one secondary cell.
20. The wireless device of claim 19, wherein the second cell group comprises secondary cells.
21. The wireless device of claim 12, wherein the second control message does not comprise an information element releasing the cell.
22. The wireless device of claim 12, wherein the second control message further comprises an indication of a random access preamble.
23. The wireless device of claim 12, wherein the instructions, when executed by the one or more processors, further cause the wireless device to perform a synchronization process with a target cell.
24. A system comprising: a wireless device; and a base station comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors of the base station, cause the base station to: transmit at least one first control message comprising configuration parameters of a plurality of cells grouped into a plurality of cell groups comprising a first cell group and a second cell group, wherein: transmission timing associated with uplink transmissions in the first cell group is based on a first cell of the first cell group; and transmission timing associated with uplink transmissions in the second cell group is based on a second cell of the second cell group; and transmit a second control message configured to, for a cell associated with the wireless device, cause a cell grouping modification from the first cell group to the second cell group, wherein one or more configuration parameters of the cell are maintained during the cell grouping modification, and wherein the second control message comprises mobility control information; and wherein the wireless device comprises: one or more processors; and memory storing instructions that, when executed by the one or more processors of the wireless device, cause the wireless device to: receive the at least one first control message; receive the second control message; and perform, based on the second control message, a handover.
25. The system of claim 24, wherein the handover is from the base station to a second base station.
26. The system of claim 24, wherein the handover is from a first sector of the base station to a second sector of the base station.
27. The system of claim 24, wherein the at least one first control message comprises a timer value for a time alignment timer for each of the plurality of cell groups.
28. The system of claim 24, wherein the second control message is a radio resource control connection reconfiguration message.
29. The system of claim 24, wherein the instructions, when executed by the one or more processors of the base station, further cause the base station to transmit a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to explicitly release a secondary cell as part of a cell grouping modification, for the secondary cell and from the second cell group to the first cell group.
30. The system of claim 24, wherein the instructions, when executed by the one or more processors of the base station, further cause the base station to transmit a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to cause a cell grouping modification, for a secondary cell and from the second cell group to the first cell group, by: releasing the secondary cell; and associating the secondary cell with a different cell group index.
31. The system of claim 24, wherein the first cell group comprises a primary cell and at least one secondary cell.
32. The system of claim 31, wherein the second cell group comprises secondary cells.
33. The system of claim 24, wherein the second control message does not comprise an information element releasing the cell.
34. The system of claim 24, wherein the second control message further comprises an indication of a random access preamble.
35. The system of claim 24, wherein the instructions, when executed by the one or more processors of the wireless device, further cause the wireless device to perform a synchronization process with a target cell.
36. A method comprising: transmitting, by a base station to a wireless device, at least one first control message comprising configuration parameters of a plurality of cells grouped into a plurality of cell groups comprising a first cell group and a second cell group, wherein: transmission timing associated with uplink transmissions in the first cell group is based on a first cell of the first cell group; and transmission timing associated with uplink transmissions in the second cell group is based on a second cell of the second cell group; determining to perform a handover of the wireless device; and transmitting a second control message configured to, for a cell associated with the wireless device, cause a cell grouping modification from the first cell group to the second cell group, wherein one or more configuration parameters of the cell are maintained during the cell grouping modification, and wherein the second control message comprises mobility control information.
37. The method of claim 36, further comprising initiating the handover of the wireless device from the base station to a second base station.
38. The method of claim 36, further comprising initiating the handover of the wireless device from a first sector of the base station to a second sector of the base station.
39. The method of claim 36, wherein the at least one first control message comprises a timer value for a time alignment timer for each of the plurality of cell groups.
40. The method of claim 36, wherein the second control message is a radio resource control connection reconfiguration message.
41. The method of claim 36, further comprising transmitting a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to explicitly release a secondary cell as part of a cell grouping modification, for the secondary cell and from the second cell group to the first cell group.
42. The method of claim 36, further comprising transmitting a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to cause a cell grouping modification, for a secondary cell and from the second cell group to the first cell group, by: releasing the secondary cell; and associating the secondary cell with a different cell group index.
43. The method of claim 36, wherein the first cell group comprises a primary cell and at least one secondary cell.
44. The method of claim 43, wherein the second cell group comprises secondary cells.
45. The method of claim 36, wherein the second control message does not comprise an information element releasing the cell.
46. The method of claim 36, wherein the second control message further comprises an indication of a random access preamble.
47. A method comprising: receiving, by a wireless device from a base station, at least one first control message comprising configuration parameters of a plurality of cells grouped into a plurality of cell groups comprising a first cell group and a second cell group, wherein: transmission timing associated with uplink transmissions in the first cell group is based on a first cell of the first cell group; and transmission timing associated with uplink transmission in the second cell group is based on a second cell of the second cell group; receiving a second control message configured to, for a cell associated with the wireless device, cause a cell grouping modification from the first cell group to the second cell group, wherein one or more configuration parameters of the cell are maintained during the cell grouping modification, and wherein the second control message comprises mobility control information; and performing, based on the second control message, a handover.
48. The method of claim 47, wherein the handover is from the base station to a second base station.
49. The method of claim 47, wherein the handover is from a first sector of the base station to a second sector of the base station.
50. The method of claim 47, wherein the at least one first control message comprises a timer value for a time alignment timer for each of the plurality of cell groups.
51. The method of claim 47, wherein the second control message is a radio resource control connection reconfiguration message.
52. The method of claim 47, further comprising receiving a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to explicitly release a secondary cell as part of a cell grouping modification, for the secondary cell and from the second cell group to the first cell group.
53. The method of claim 47, further comprising receiving a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to cause a cell grouping modification, for a secondary cell and from the second cell group to the first cell group, by: releasing the secondary cell; and associating the secondary cell with a different cell group index.
54. The method of claim 47, wherein the first cell group comprises a primary cell and at least one secondary cell.
55. The method of claim 54, wherein the second cell group comprises secondary cells.
56. The method of claim 47, wherein the second control message does not comprise an information element releasing the cell.
57. The method of claim 47, wherein the second control message further comprises an indication of a random access preamble.
58. The method of claim 47, further comprising performing a synchronization process with a target cell.
59. A method comprising: transmitting, by a base station to a wireless device, at least one first control message comprising configuration parameters of a plurality of cells grouped into a plurality of cell groups comprising a first cell group and a second cell group, wherein: transmission timing associated with uplink transmissions in the first cell group is based on a first cell of the first cell group; and transmission timing associated with uplink transmissions in the second cell group is based on a second cell of the second cell group; transmitting, by the base station to the wireless device, a second control message configured to, for a cell associated with the wireless device, cause a cell grouping modification from the first cell group to the second cell group, wherein one or more configuration parameters of the cell are maintained during the cell grouping modification, and wherein the second control message comprises mobility control information; receiving, by the wireless device, the at least one first control message; receiving, by the wireless device, the second control message; and performing, based on the second control message, a handover of the wireless device.
60. The method of claim 59, wherein the handover is from the base station to a second base station.
61. The method of claim 59, wherein the handover is from a first sector of the base station to a second sector of the base station.
62. The method of claim 59, wherein the at least one first control message comprises a timer value for a time alignment timer for each of the plurality of cell groups.
63. The method of claim 59, wherein the second control message is a radio resource control connection reconfiguration message.
64. The method of claim 59, further comprising transmitting a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to explicitly release a secondary cell as part of a cell grouping modification, for the secondary cell and from the second cell group to the first cell group.
65. The method of claim 59, further comprising transmitting a third control message, wherein the third control message does not comprise mobility control information, and wherein the third control message is configured to cause a cell grouping modification, for a secondary cell and from the second cell group to the first cell group, by: releasing the secondary cell; and associating the secondary cell with a different cell group index.
66. The method of claim 59, wherein the first cell group comprises a primary cell and at least one secondary cell.
67. The method of claim 66, wherein the second cell group comprises secondary cells.
68. The method of claim 59, wherein the second control message does not comprise an information element releasing the cell.
69. The method of claim 59, wherein the second control message further comprises an indication of a random access preamble.
70. The method of claim 59, further comprising performing a synchronization process with a target cell.
FIG. 2 is a diagram depicting an example transmission time and reception time for two carriers as per an aspect of an embodiment of the present invention. A multicarrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 10 carriers. Carrier A 204 and carrier B 205 may have the same or different timing structures. Although FIG. 2 shows two synchronized carriers, carrier A 204 and carrier B 205 may or may not be synchronized with each other. Different radio frame structures may be supported for FDD (frequency division duplex) and TDD (time division duplex) duplex mechanisms. FIG. 2 shows an example FDD frame timing. Downlink and uplink transmissions may be organized into radio frames 201. In this example, radio frame duration is 10 msec. Other frame durations, for example, in the range of 1 to 100 msec may also be supported. In this example, each 10 msec radio frame 201 may be divided into ten equally sized sub-frames 202. Other subframe durations such as including 0.5 msec, 1 msec, 2 msec, and 5 msec may also be supported. Sub-frame(s) may consist of two or more slots 206. For the example of FDD, 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmissions in each 10 msec interval. Uplink and downlink transmissions may be separated in the frequency domain. Slot(s) may include a plurality of OFDM symbols 203. The number of OFDM symbols 203 in a slot 206 may depend on the cyclic prefix length and subcarrier spacing.
FIG. 4 is an example block diagram of a base station 401 and a wireless device 406, as per an aspect of an embodiment of the present invention. A communication network 400 may include at least one base station 401 and at least one wireless device 406. The base station 401 may include at least one communication interface 402, at least one processor 403, and at least one set of program code instructions 405 stored in non-transitory memory 404 and executable by the at least one processor 403. The wireless device 406 may include at least one communication interface 407, at least one processor 408, and at least one set of program code instructions 410 stored in non-transitory memory 409 and executable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communication with communication interface 407 in wireless device 406 via a communication path that includes at least one wireless link 411. Wireless link 411 may be a bi-directional link. Communication interface 407 in wireless device 406 may also be configured to engage in a communication with communication interface 402 in base station 401. Base station 401 and wireless device 406 may be configured to send and receive data over wireless link 411 using multiple frequency carriers. According to some of the various aspects of embodiments, transceiver(s) may be employed. A transceiver is a device that includes both a transmitter and receiver. Transceivers may be employed in devices such as wireless devices, base stations, relay nodes, and/or the like. Example embodiments for radio technology implemented in communication interface 402, 407 and wireless link 411 are illustrated in FIG. 1, FIG. 2, and FIG. 3, and associated text.
According to some of the various aspects of embodiments, an LTE network may include many base stations, providing a user plane (PDCP: packet data convergence protocol/RLC: radio link control/MAC: media access control/PHY: physical) and control plane (RRC: radio resource control) protocol terminations towards the wireless device. The base station(s) may be interconnected with other base station(s) by means of an X2 interface. The base stations may also be connected by means of an S1 interface to an EPC (Evolved Packet Core). For example, the base stations may be interconnected to the MME (Mobility Management Entity) by means of the S1-MME interface and to the Serving Gateway (S-GW) by means of the S1-U interface. The S1 interface may support a many-to-many relation between MMES/Serving Gateways and base stations. A base station may include many sectors for example: 1, 2, 3, 4, or 6 sectors. A base station may include many cells, for example, ranging from 1 to 50 cells or more. A cell may be categorized, for example, as a primary cell or secondary cell. When carrier aggregation is configured, a wireless device may have one RRC connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell may provide the NAS (non-access stratum) mobility information (e.g. TAI--tracking area identifier), and at RRC connection re-establishment/handover, one serving cell may provide the security input. This cell may be referred to as the Primary Cell (PCell). In the downlink, the carrier corresponding to the PCell may be the Downlink Primary Component Carrier (DL PCC), while in the uplink, it may be the Uplink Primary Component Carrier (UL PCC). Depending on wireless device capabilities, Secondary Cells (SCells) may be configured to form together with the PCell a set of serving cells. In the downlink, the carrier corresponding to an SCell may be a Downlink Secondary Component Carrier (DL SCC), while in the uplink, it may be an Uplink Secondary Component Carrier (UL SCC). An SCell may or may not have an uplink carrier.
According to some of the various aspects of embodiments, TA maintenance, pathloss reference handling and the timing reference for pTAG may follow LTE release 10 principles. The UE may need to measure downlinkpathloss to calculate the uplink transmit power. The pathloss reference may be used for uplink power control and/or transmission of random access preamble(s). A UE may measure downlink pathloss using the signals received on the pathloss reference cell. For SCell(s) in a pTAG, the choice of pathloss reference for cells may be selected from and be limited to the following two options: a) the downlink Scell linked to an uplink SCell using the system information block 2 (SIB2), and b) the downlink PCell. The pathloss reference for SCells in pTAG may be configurable using RRC message(s) as a part of SCell initial configuration and/or reconfiguration. According to some of the various aspects of embodiments, PhysicalConfigDedicatedSCell information element (IE) of an Scell configuration may include the pathloss reference SCell (downlink carrier) for an SCell in pTAG. The downlink SCell linked to an uplink SCell using the system information block 2 (SIB2) may be referred to as the SIB2 linked downlink of the SCell. Different TAGs may operate in different bands. For an uplink carrier in an sTAG, the pathloss reference may be only configurable to the downlink Scell linked to an uplink SCell using the system information block 2 (SIB2) of the SCell.
FIG. 8 is an example flow diagram illustrating signaling messages during a handover as per an aspect of an embodiment of the present invention. An important issue with respect to TAG configuration is how TAG configuration may be maintained or updated during a handover. A UE may be configured with a first TAG configuration with a serving eNB. A target eNB may maintain the same TAG configuration, or may update the UE TAG configuration. The target eNB may have a different cell configuration and may require a different TAG configuration. In another example embodiment, the target eNB may employ cells with the same frequencies as the serving cell and may require maintaining the same TAG configuration. The target eNB may configure TAG configuration after the handover is completed or may configure TAG configuration during the handover process. Release 10 of LTE does not support multiple TAG configuration, and addressing the TAG configuration changes during handover is not addressed in release 10 LTE technology. There is a need for developing a signaling flow, UE processes, and eNB processes to address TAG configuration and TAG configuration parameter handling during the handover to reduce the handover overhead and delay, and increase handover efficiency. Furthermore, there is a need to develop handover signaling and handover message parameters to address TAG configuration during a handover process.
According to some of the various aspects of embodiments, after the successful completion of handover, PDCP SDUs may be re-transmitted in the target cell(s). This may apply for dedicated radio bearers using RLC-AM mode and/or for handovers not involving full configuration option. After the successful completion of handover not involving full configuration option, the SN (sequence number) and/or the HFN (hyper frame number) may be reset for some radio bearers. For the dedicated radio bearers using RLC-AM mode both SN and HFN may continue. For reconfigurations involving the full configuration option, the PDCP entities may be newly established (SN and HFN may not continue) for dedicated radio bearers irrespective of the RLC mode. UE behaviour to be performed upon handover may be the same regardless of the handover procedures used within the network (e.g. whether the handover includes X2 or S1 signaling procedures).
According to some of the various aspects of embodiments, the mapping of a serving cell to a TA group may be configured by the serving eNB with RRC signaling. The mechanism for TAG configuration and reconfiguration may be based on RRC signaling. When needed, the mapping between an SCell and a TA group may be reconfigured with RRC signaling. The mapping between an SCell and a TAG may not be reconfigured with RRC while the SCell is configured. For example if there is a need to move an SCell from an sTAG to a pTAG, at least one RRC message, for example at least one RRC reconfiguration message, may be send to the UE to reconfigure TAG configurations. PCell may not change TA group and may always be a member of the pTAG.
FIG. 8 is an example flow diagram illustrating signaling messages during a handover as per an aspect of an embodiment of the present invention. According to some of the various aspects of embodiments, a serving base station may receive a first message from a wireless device on a primary cell in a plurality of cells at block 800. The first message may be an RRC UE capability message. The plurality of cells may comprise the primary cell and at least one secondary cell. The first message may comprise at least one parameter indicating whether the wireless device supports configuration of a plurality of time alignment groups (TAGs). The base station may receive a plurality of radio capability parameters from the wireless device.
In an example embodiment, the capability may be received on a first signaling bearer on the primary cell. The plurality of radio capability parameters may comprise a first sequence of one or more radio configuration parameters. A first radio configuration parameter in the first sequence may comprise a first parameter indicating whether multiple timing advance groups may be supported for a first band combination. The first band combination may be in a second sequence of one or more band combinations. The index of the first radio configuration parameter in the first sequence may determine the index of the first band combination in the second sequence.
The serving base station may selectively transmit at least one second message to the wireless device if the at least one parameter indicates support for configuration of the plurality of TAGs at block 802. The at least one second message may configure a first plurality of TAGs in the wireless device. If the at least one parameter does not indicate support for configuration of the plurality of TAGs, the base station may not configure a plurality of TAGs in the wireless device. If the at least one parameter indicates support for configuration of the plurality of TAGs, the base station may or may not configure the first plurality of TAGs in the wireless device depending on the required wireless device configuration and many other parameters. Transmission or not transmission (selective transmission) of at least one second message to configure the first plurality of TAGs is determined by the base station based on many criteria described in this specification.
FIG. 9 is an example flow diagram illustrating signaling messages during a handover as per an aspect of an embodiment of the present invention. According to some of the various aspects of embodiments, a serving base station, in response to making a handover decision by the serving base station for a wireless device, may transmit at least one third message to at least one target base station at block 900. The third message(s) in block 900 of FIG. 9 is the same as the third message(s) in block 804 of FIG. 8. The at least one third message may comprise the at least one parameter indicating whether the wireless device supports configuration of a plurality of time alignment groups. The format of the parameter (information element) indicating whether the wireless device supports configuration of a plurality of time alignment groups is the same format as the UE capability message transmitted by the wireless device to the base station in the first message as described in the specification. The at least one third message may further comprise a plurality of parameters of the configuration at least indicating association between at least one cell and a corresponding cell group index (configuration information of said first plurality TAGs). The parameters included in the configuration information of said first plurality TAGs may be the same as the ones included in the at least one second message as described in this specification. The at least one third message may be a handover request message transmitted to at least one target base station to prepare the target base stations for the handover of the wireless device. The UE capability parameters may be included in the at least one third message. Furthermore, UE dedicated radio parameters comprising UE multiple TAG configuration may also be included in the handover request message. UE dedicated radio parameters may comprise MACMainconfig information element. UE dedicated radio parameters may comprise TAG configuration including TAG indices and associated cell indices, and time alignment timer value for each cell group.
The base station may require changing TAG configuration due to various reasons as described in the specifications. Examples comprise UE mobility, changes in channel conditions, traffic and load, and/or the like. The base station may transmit an RRC Connection Reconfiguration message to a wireless device. The RRC connection reconfiguration message may be employed to change TAG configuration in the wireless device at block 1102. The base station may transmit at least one RRC Connection Reconfiguration message to modify some of the associations among the plurality of cells and the plurality of cell groups. In order to change a first cell group index associated with the first cell, the at least one RRC Connection Reconfiguration message: a) may add the first cell with an updated first cell group index different from the first cell group index; and b) may be transmitted with MobilityControlInfo Information Element. This method may work if the first cell is a primary cell or a secondary cell. In example embodiments, this method is advantageous from signaling perspective if the first cell is a primary cell. In other words, if the first cell is the primary cell, the at least one second RRC message may be configured to cause the wireless device to reconfigure the primary cell as a secondary cell with an updated first cell group index different from the first cell group index. And the at least one second RRC message may comprise mobility control information
According to some of the various aspects of embodiments, the Random Access Resource selection procedure may be performed as follows. If ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) have been explicitly signaled and ra-PreambleIndex is not zero, then the Random Access Preamble and the PRACH Mask Index may be those explicitly signaled. Otherwise, the Random Access Preamble may be selected by the UE.
The UE may determine the next available subframe containing PRACH permitted by the restrictions given by the prach-ConfigIndex, the PRACH Mask Index and physical layer timing requirements (a UE may take into account the possible occurrence of measurement gaps when determining the next available PRACH subframe). If the transmission mode is TDD and the PRACH Mask Index is equal to zero, then if ra-PreambleIndex was explicitly signaled and it was not 0 (i.e., not selected by MAC), then randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe. Else, the UE may randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe and the next two consecutive subframes. If the transmission mode is not TDD or the PRACH Mask Index is not equal to zero, a UE may determine a PRACH within the determined subframe in accordance with the requirements of the PRACH Mask Index. Then the UE may proceed to the transmission of the Random Access Preamble.
PRACH mask index values may range for example from 0 to 16. PRACH mask index value may determine the allowed PRACH resource index that may be used for transmission. For example, PRACH mask index 0 may mean that all PRACH resource indexes are allowed; or PRACH mask index 1 may mean that PRACH resource index 0 may be used. PRACH mask index may have different meaning in TDD and FDD systems.
According to some of the various aspects of embodiments, if a downlink assignment for this TTI (transmission time interval) has been received on the PDCCH for the RA-RNTI and the received TB (transport block) is successfully decoded, the UE may regardless of the possible occurrence of a measurement gap: if the RAR contains a backoff indicator (BI) subheader, set the backoff parameter value in the UE employing the BI field of the backoff indicator subheader, else, set the backoff parameter value in the UE to zero ms. If the RAR contains a random access preamble identifier corresponding to the transmitted random access preamble, the UE may consider this RAR reception successful and apply the following actions for the serving cell where the random access preamble was transmitted: process the received riming advance command for the cell group in which the preamble was transmitted, indicate the preambleInitialReceivedTargetPower and the amount of power ramping applied to the latest preamble transmission to lower layers (i.e., (PREAMBLE_TRANSMISSION_COUNTER-1)*powerRampingStep); process the received uplink grant value and indicate it to the lower layers; the uplink grant is applicable to uplink of the cell in which the preamble was transmitted. If ra-PreambleIndex was explicitly signaled and it was not zero (e.g., not selected by MAC), consider the random access procedure successfully completed. Otherwise, if the Random Access Preamble was selected by UE MAC, set the Temporary C-RNTI to the value received in the RAR message. When an uplink transmission is required, e.g., for contention resolution, the eNB may not provide a grant smaller than 56 bits in the Random Access Response.
According to some of the various aspects of embodiments, if no RAR is received within the RAR window, or if none of all received RAR contains a random access preamble identifier corresponding to the transmitted random access preamble, the random access response reception may considered not successful. If RAR is not received, UE may increment PREAMBLE_TRANSMISSION_COUNTER by 1. If PREAMBLE_TRANSMISSION_COUNTER=preambleTransMax+1 and random access preamble is transmitted on the PCell, then UE may indicate a random access problem to upper layers (RRC). This may result in radio link failure. If PREAMBLE_TRANSMISSION_COUNTER=preambleTransMax+1 and the random access preamble is transmitted on an SCell, then UE may consider the random access procedure unsuccessfully completed. UE may stay in RRC connected mode and keep the RRC connection active even though a random access procedure unsuccessfully completed on a secondary TAG. According to some of the various aspects of embodiments, at completion of the random access procedure, the UE may discard explicitly signaled ra-PreambleIndex and ra-PRACH-MaskIndex, if any; and flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer. In addition, the RN may resume the suspended RN subframe configuration, if any.
According to some of the various aspects of embodiments, a UE may have a configurable timer timeAlignmentTimer per TAG. The timeAlignmentTimer is used to control how long the UE considers the Serving Cells belonging to the associated TAG to be uplink time aligned (in-sync). When a Timing Advance Command MAC control element is received, the UE may apply the riming advance command for the indicated TAG, and start or restart the timeAlignmentTimer associated with the indicated TAG. When a timing advance command is received in a RAR message for a serving cell belonging to a TAG and if the random access preamble was not selected by UE MAC, the UE may apply the timing advance command for this TAG, and may start or restart the timeAlignmentTimer associated with this TAG. When a timeAlignmentTimer associated with the pTAG expires, the UE may: flush all HARQ buffers for all serving cells; notify RRC to release PUCCH/SRS for all serving cells; clear any configured downlink assignments and uplink grants; and consider all running timeAlignmentTimers as expired. When a timeAlignmentTimer associated with an sTAG expires, then for all Serving Cells belonging to this TAG, the UE may flush all HARQ buffers; and notify RRC to release SRS. The UE may not perform any uplink transmission on a serving Cell except the random access preamble transmission when the timeAlignmentTimer associated with the TAG to which this serving cell belongs is not running. When the timeAlignmentTimer associated with the pTAG is not running, the UE may not perform any uplink transmission on any serving cell except the random access preamble transmission on the PCell. A UE stores or maintains N_TA (current timing advance value of an sTAG) upon expiry of associated timeAlignmentTimer. The UE may apply a received timing advance command MAC control element and starts associated timeAlignmentTimer. Transmission of the uplink radio frame number i from the UE may start (N.sub.TA+N.sub.TA offset).times.T.sub.s seconds before the start of the corresponding downlink radio frame at the UE, where 0.ltoreq.N.sub.TA.ltoreq.20512. In an example implementation, N.sub.TA offset=0 for frame structure type 1 (FDD) and N.sub.TA offset=624 for frame structure type 2 (TDD).
The timing advance command for a TAG may indicate the change of the uplink timing relative to the current uplink timing for the TAG as multiples of 16T.sub.s (T.sub.s: sampling time unit). The start timing of the random access preamble may obtained employing a downlink synchronization time in the same TAG. In case of random access response, an 11-bit timing advance command, TA, for a TAG may indicate N.sub.TA values by index values of TA=0, 1, 2, . . . , 1282, where an amount of the time alignment for the TAG may be given by N.sub.TA=TA.times.16. In other cases, a 6-bit timing advance command, TA, for a TAG may indicate adjustment of the current N.sub.TA value, N.sub.TA,old, to the new N.sub.TA value, N.sub.TA,new, by index values of TA=0, 1, 2, . . . , 63, where N.sub.TA,new=N.sub.TA,old+(TA-31).times.16. Here, adjustment of N.sub.TA value by a positive or a negative amount indicates advancing or delaying the uplink transmission timing for the TAG by a given amount respectively. For a timing advance command received on subframe n, the corresponding adjustment of the uplink transmission timing may apply from the beginning of subframe n+6. For serving cells in the same TAG, when the UE's uplink PUCCH/PUSCH/SRS transmissions in subframe n and subframe n+1 are overlapped due to the timing adjustment, the UE may complete transmission of subframe n and not transmit the overlapped part of subframe n+1. If the received downlink timing changes and is not compensated or is only partly compensated by the uplink timing adjustment without timing advance command, the UE may change N.sub.TA accordingly.
Downlink frames and subframes of downlink carriers may be time aligned (by the base station) in carrier aggregation and multiple TAG configuration. Time alignment errors may be tolerated to some extent. For example, for intra-band contiguous carrier aggregation, time alignment error may not exceed 130 ns. In another example, for intra-band non-contiguous carrier aggregation, time alignment error may not exceed 260 ns. In another example, for inter-band carrier aggregation, time alignment error may not exceed 1.3 .mu.s.
Previous Patent US 10,129,797 | Next Patent US 10,129,799