Method and apparatus for implementing tracking area update and cell reselection in a long term evolution system
Claim Score by NHIP
Abstract
The invention performs long term evolution (LTE) tracking area updates (TAUs), and tracking area code (TAC) and public land mobile network identification (PLMN-ID) assisted optimized wireless transmit/receive unit (WTRU) cell reselection. An evolved Node-B broadcasts system information including at least one system information block (SIB) based at least in part on an enhanced universal terrestrial radio access network (E-UTRAN) parameter response message sent by an evolved packet core (EPC) network. A WTRU generates a new TAC, which represents a tracking area identification (TA-ID) of a new cell, based on the system information, and compares the new TAC to an existing TAC, which represents a TA-ID of a previous cell. The WTRU transmits to the EPC network a TAU request message including the TA-ID of the new cell. The EPC network sends either a TAU accept message or a TAU reject message to the WTRU.

Term
2.4 yearsto projected expiry
Projected expiry 5 March 2029, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
14 claims: 3 independent, 11 dependent
- 1A method for communicating a tracking area identity, the method comprising:receiving system information comprising a system information block (SIB), wherein the SIB comprises a mobile country code (MCC), a mobile network code (MNC), and a tracking area code (TAC);identifying a tracking area of a new cell using the TAC;detecting, based on the SIB, whether the TAC matches one of a plurality of currently registered tracking areas;determining that the TAC does not match one of a plurality of tracking areas located on a forbidden tracking area list;generating a tracking area update (TAU) request message upon detecting that the TAC does not match one of the plurality of currently registered tracking areas;and transmitting the TAU request message;receiving a TAU Accept Message, wherein the TAU Accept Message comprises a list of accepted tracking areas;and removing at least one tracking area from the forbidden tracking area list based on the at least one tracking area being included in the list of accepted tracking areas.
- 6A wireless transmit/receive unit (WTRU) comprising:at least one antenna;a receiver coupled to the at least one tracking area antenna, the receiver configured to receive system information comprising a system information block (SIB) via the at least one antenna, wherein the SIB comprises a mobile country code (MCC), a mobile network code (MNC), and a tracking area code (TAC);a processor coupled to the receiver, the processor configured to identify a tracking area of a new cell using the TAC, detect, based on the received system information, whether the TAC matches one of a plurality of currently registered tracking areas, determine that the TAC does not match one of a plurality of tracking areas located on a forbidden tracking area list, and generate a tracking area update (TAU) request message when the processor detects that the TAC does not match one of the plurality of currently registered tracking areas;a transmitter configured to transmit the TAU request message to an evolved Node B (eNB) via the at least one antenna;the receiver further configured to receive a TAU Accept Message, wherein the TAU Accept Message comprises a list of accepted tracking areas;and the processor further configured to remove at least one tracking area from the forbidden tracking area list based on the at least one tracking area being included in the list of accepted tracking areas.
- 11Broadest claimClaim Score 52, average(NHIP)An evolved Node-B (eNodeB) comprising:at least one antenna;a processor coupled to a receiver, the processor configured to receive network area partitioning information from an evolved packet core network, generate enhanced universal terrestrial radio access network (E-UTRAN) system information, form a system information block (SIB) based, at least in part, on the network area partitioning information, wherein the SIB comprises a mobile country code (MCC), a mobile network code (MNC), and a tracking area code (TAC), wherein the (TAC) identifies a tracking area of a cell served by the eNodeB;a transmitter coupled to the antenna, the transmitter configured to broadcast the (SIB) via the at least one antenna.
Independent claims3
62 paragraphs in 6 sections, as filed
CROSS REFERENCE TO RELATED APPLICATION
0001This application is a continuation of U.S. patent application Ser. No. 11/923,033, filed Oct. 24, 2007, which claims the benefit of U.S. Provisional Application No. 60/863,528 filed Oct. 30, 2006, which is incorporated by reference as if fully set forth.
FIELD OF INVENTION
0002The invention is related to wireless communication systems.
BACKGROUND
0003The third generation partnership project (3GPP) has recently initiated the long term evolution (LTE) program to bring new technology, new network architecture, new configuration, and new applications and services to the wireless cellular network in order to provide improved spectral efficiency and faster user experiences. One new item adopted by the LTE program is the mobility tracking area concept, which replaces the former third generation (3G) universal mobile telecommunications system (UMTS) system's location area (LA), registration area (RA) and universal terrestrial radio access network (UTRAN) registration area (URA).
0004There is only one common tracking area concept defined for radio access network (RAN) and core network (CN) in LTE/system architecture evolution (SAE). The location of an LTE wireless transmit/receive unit (WTRU) that is in an idle state (LTE_IDLE) is known by the network on a tracking area granularity. The goal is to reduce the mobility area management complexities and to reduce the related signaling overhead for the mobility area update whereby, instead of using both the RA/LA and the URA for UMTS, only a tracking area (TA) is used for LTE.
0005Prior to LTE, due to the second generation (2G) legacy, the 3G UMTS mobility area management has a location area, which includes one or more routing areas. The 3G UMTS also has a URA, which covers one or more UMTS cells.
0006The mobility management involves the URA update, which is administered by a radio resource control (RRC) unit, and the routing area update (RAU) which is administered by the general packet radio service (GPRS) mobility manager (GMM) at the non-access stratum (NAS) protocol stack. The WTRU URA update is triggered by the matching of the current URA identification (URA-ID) with the cell-published URA-ID contents in UMTS system information block (SIB) type 2 (SIB-2). The RAU is triggered by the changing of any one of the public land mobile network identification (PLMN-ID), the location area code (LAC) and the routing area code (RAC). Note that both the LAC and the RAC are published to the cell via SIB-1. The current 3GPP UMTS system information broadcast content is shown in the following Table 1.
0000<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="7"><colspec colname="1" colwidth="42pt" align="left" /><colspec colname="2" colwidth="35pt" align="left" /><colspec colname="3" colwidth="56pt" align="left" /><colspec colname="4" colwidth="56pt" align="left" /><colspec colname="5" colwidth="70pt" align="left" /><colspec colname="6" colwidth="49pt" align="left" /><colspec colname="7" colwidth="56pt" align="left" /><thead><row><entry namest="1" nameend="7" rowsep="1">TABLE 1</entry></row><row><entry namest="1" nameend="7" align="center" rowsep="1" /></row><row><entry>System</entry><entry /><entry>WTRU</entry><entry>WTRU</entry><entry /><entry /><entry /></row><row><entry>Information</entry><entry /><entry>mode/state</entry><entry>mode/state</entry><entry /><entry>Modification</entry></row><row><entry>Block</entry><entry>Area</entry><entry>when block is</entry><entry>when block</entry><entry>Scheduling</entry><entry>of System</entry><entry>Additional</entry></row><row><entry>(SIB)</entry><entry>scope</entry><entry>valid</entry><entry>is read</entry><entry>Information</entry><entry>Information</entry><entry>Comment</entry></row><row><entry namest="1" nameend="7" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Master</entry><entry>Cell</entry><entry>Idle mode,</entry><entry>Idle mode,</entry><entry>SIB_POS = 0</entry><entry>Value tag</entry><entry /></row><row><entry>information</entry><entry /><entry>CELL_FACH,</entry><entry>CELL_FACH,</entry><entry>SIB_REP = 8 (FDD)</entry></row><row><entry>block</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>SIB_REP = 8, 16,</entry></row><row><entry /><entry /><entry>URA_PCH,</entry><entry>URA_PCH,</entry><entry>32 (TDD)</entry></row><row><entry /><entry /><entry>CELL_DCH</entry><entry>CELL_DCH</entry><entry>SIB_OFF = 2</entry></row><row><entry /><entry /><entry>(TDD only)</entry><entry>(TDD only)</entry></row><row><entry>Scheduling</entry><entry>Cell</entry><entry>Idle mode,</entry><entry>Idle mode,</entry><entry>Specified by the IE</entry><entry>Value tag</entry></row><row><entry>block 1</entry><entry /><entry>CELL_FACH,</entry><entry>CELL_FACH,</entry><entry>“Scheduling</entry></row><row><entry /><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>information” in MIB</entry></row><row><entry /><entry /><entry>URA_PCH,</entry><entry>URA_PCH,</entry></row><row><entry /><entry /><entry>CELL_DCH</entry><entry>CELL_DCH</entry></row><row><entry /><entry /><entry>(TDD only)</entry><entry>(TDD only)</entry></row><row><entry>Scheduling</entry><entry>Cell</entry><entry>Idle mode,</entry><entry>Idle mode,</entry><entry>Specified by the IE</entry><entry>Value tag</entry></row><row><entry>block 2</entry><entry /><entry>CELL_FACH,</entry><entry>CELL_FACH,</entry><entry>“Scheduling</entry></row><row><entry /><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>information” in MIB</entry></row><row><entry /><entry /><entry>URA_PCH,</entry><entry>URA_PCH,</entry></row><row><entry /><entry /><entry>CELL_DCH</entry><entry>CELL_DCH</entry></row><row><entry /><entry /><entry>(TDD only)</entry><entry>(TDD only)</entry></row><row><entry>System</entry><entry>PLMN</entry><entry>Idle mode</entry><entry>Idle,</entry><entry>Specified by the IE</entry><entry>Value tag</entry></row><row><entry>information</entry><entry /><entry>CELL_FACH,</entry><entry>CELL_FACH,</entry><entry>“Scheduling</entry></row><row><entry>block type 1</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>information”</entry></row><row><entry /><entry /><entry>URA_PCH,</entry><entry>URA_PCH</entry></row><row><entry /><entry /><entry>CELL_DCH</entry></row><row><entry>System</entry><entry>Cell</entry><entry>URA_PCH</entry><entry>URA_PCH</entry><entry>Specified by the IE</entry><entry>Value tag</entry></row><row><entry>information</entry><entry /><entry /><entry /><entry>“Scheduling</entry></row><row><entry>block type 2</entry><entry /><entry /><entry /><entry>information”</entry></row><row><entry>System</entry><entry>Cell</entry><entry>Idle mode,</entry><entry>Idle mode,</entry><entry>Specified by the IE</entry><entry>Value tag</entry></row><row><entry>information</entry><entry /><entry>(CELL_FACH,</entry><entry>(CELL_FACH,</entry><entry>“Scheduling</entry></row><row><entry>block type 3</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>information”</entry></row><row><entry /><entry /><entry>URA_PCH)</entry><entry>URA_PCH)</entry></row><row><entry>System</entry><entry>Cell</entry><entry>CELL_FACH,</entry><entry>CELL_FACH,</entry><entry>Specified by the IE</entry><entry>Value tag</entry><entry>If System</entry></row><row><entry>information</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>“Scheduling</entry><entry /><entry>information</entry></row><row><entry>block type 4</entry><entry /><entry>URA_PCH</entry><entry>URA_PCH</entry><entry>information”</entry><entry /><entry>block type 4 is</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>not broadcast in</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>a cell, the</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>connected</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>mode WTRU</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>shall apply</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>information in</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>System</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>information</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>block type 3 in</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>connected</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>mode.</entry></row><row><entry>System</entry><entry>Cell</entry><entry>Idle mode,</entry><entry>Idle mode,</entry><entry>Specified by the IE</entry><entry>Value tag</entry><entry>System</entry></row><row><entry>information</entry><entry /><entry>(CELL_FACH,</entry><entry>(CELL_FACH,</entry><entry>“Scheduling</entry><entry /><entry>information</entry></row><row><entry>block type 5</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>information”</entry><entry /><entry>block type 5bis</entry></row><row><entry>and 5bis</entry><entry /><entry>URA_PCH,</entry><entry>URA_PCH,</entry><entry /><entry /><entry>is sent instead</entry></row><row><entry /><entry /><entry>CELL_DCH</entry><entry>CELL_DCH</entry><entry /><entry /><entry>of system</entry></row><row><entry /><entry /><entry>(TDD only))</entry><entry>(TDD only))</entry><entry /><entry /><entry>information</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>block type 5 in</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>networks that</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>use Band IV.</entry></row><row><entry>System</entry><entry>Cell</entry><entry>CELL_FACH,</entry><entry>CELL_FACH,</entry><entry>Specified by the IE</entry><entry>Value tag</entry><entry>If system</entry></row><row><entry>information</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>“Scheduling</entry><entry /><entry>information</entry></row><row><entry>block type 6</entry><entry /><entry>URA_PCH,</entry><entry>URA_PCH,</entry><entry>information”</entry><entry /><entry>block type 6 is</entry></row><row><entry /><entry /><entry>CELL_DCH</entry><entry>CELL_DCH</entry><entry /><entry /><entry>not broadcast in</entry></row><row><entry /><entry /><entry>(TDD only)</entry><entry>(TDD only)</entry><entry /><entry /><entry>a cell, the</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>connected</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>mode WTRU</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>shall read</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>System</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>information</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>block type 5.</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>If some of the</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>optional IEs are</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>not included in</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>System</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>information</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>block type 6,</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>the WTRU shall</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>read the</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>corresponding</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>IEs in System</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>information</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>block type 5</entry></row><row><entry>System</entry><entry>Cell</entry><entry>Idle mode,</entry><entry>Idle mode,</entry><entry>Specified by the IE</entry><entry>Expiration</entry></row><row><entry>information</entry><entry /><entry>CELL_FACH,</entry><entry>CELL_FACH,</entry><entry>“Scheduling</entry><entry>timer =</entry></row><row><entry>block type 7</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>information”</entry><entry>MAX(32,</entry></row><row><entry /><entry /><entry>URA_PCH,</entry><entry>URA_PCH,</entry><entry /><entry>SIB_REP *</entry></row><row><entry /><entry /><entry>CELL_DCH</entry><entry>CELL_DCH</entry><entry /><entry>ExpirationTime</entry></row><row><entry /><entry /><entry>(TDD only)</entry><entry>(TDD only)</entry><entry /><entry>Factor)</entry></row><row><entry>System</entry><entry>Cell</entry><entry>Idle mode</entry><entry>Idle mode</entry><entry>Specified by the IE</entry><entry>Value tag</entry></row><row><entry>information</entry><entry /><entry>(CELL_FACH,</entry><entry>(CELL_FACH,</entry><entry>“Scheduling</entry></row><row><entry>block type</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>information”</entry></row><row><entry>11</entry><entry /><entry>URA_PCH,</entry><entry>URA_PCH)</entry></row><row><entry /><entry /><entry>CELL_DCH)</entry></row><row><entry>System</entry><entry>Cell</entry><entry>CELL_FACH,</entry><entry>Idle mode,</entry><entry>Specified by the IE</entry><entry>Value tag</entry><entry>If system</entry></row><row><entry>information</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_FACH,</entry><entry>“Scheduling</entry><entry /><entry>information</entry></row><row><entry>block type</entry><entry /><entry>URA_PCH,</entry><entry>CELL_PCH,</entry><entry>information”</entry><entry /><entry>block type 12 is</entry></row><row><entry>12</entry><entry /><entry>CELL_DCH</entry><entry>URA_PCH</entry><entry /><entry /><entry>not broadcast in</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>a cell, the</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>connected</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>mode WTRU</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>shall read</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>System</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>information</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>block type 11.</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>If some of the</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>optional IEs are</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>not included in</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>System</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>information</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>block type 12,</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>the WTRU shall</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>read the</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>corresponding</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>IEs in System</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>information</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>block type 11.</entry></row><row><entry>System</entry><entry /><entry /><entry /><entry /><entry /><entry>ANSI-41</entry></row><row><entry>information</entry></row><row><entry>block type</entry></row><row><entry>13</entry></row><row><entry>System</entry><entry /><entry /><entry /><entry /><entry /><entry>This system</entry></row><row><entry>information</entry><entry /><entry /><entry /><entry /><entry /><entry>information</entry></row><row><entry>block type</entry><entry /><entry /><entry /><entry /><entry /><entry>block is used in</entry></row><row><entry>14</entry><entry /><entry /><entry /><entry /><entry /><entry>3.84 Mcps TDD</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>mode only.</entry></row><row><entry>System</entry><entry>Cell</entry><entry>Idle Mode,</entry><entry>Idle Mode,</entry><entry>Specified by the IE</entry><entry>Value tag</entry></row><row><entry>information</entry><entry /><entry>CELL_FACH,</entry><entry>CELL_FACH,</entry><entry>“Scheduling</entry></row><row><entry>block type</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>information”</entry></row><row><entry>15</entry><entry /><entry>URA_PCH</entry><entry>URA_PCH</entry></row><row><entry>System</entry><entry>Equivalent</entry><entry>Idle Mode,</entry><entry>Idle Mode,</entry><entry>Specified by the IE</entry><entry>Value tag</entry><entry>For this system</entry></row><row><entry>information</entry><entry>PLMN</entry><entry>CELL_FACH,</entry><entry>CELL_FACH,</entry><entry>“Scheduling</entry><entry /><entry>information</entry></row><row><entry>block type</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>information”</entry><entry /><entry>block there may</entry></row><row><entry>16</entry><entry /><entry>URA_PCH,</entry><entry>URA_PCH</entry><entry /><entry /><entry>be multiple</entry></row><row><entry /><entry /><entry>CELL_DCH</entry><entry /><entry /><entry /><entry>occurrences.</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>This system</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>information</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>block is also</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>valid while in</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>GSM/GPRS.</entry></row><row><entry>System</entry><entry /><entry /><entry /><entry /><entry /><entry>This system</entry></row><row><entry>information</entry><entry /><entry /><entry /><entry /><entry /><entry>information</entry></row><row><entry>block type</entry><entry /><entry /><entry /><entry /><entry /><entry>block is used in</entry></row><row><entry>17</entry><entry /><entry /><entry /><entry /><entry /><entry>TDD mode</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry>only.</entry></row><row><entry>System</entry><entry>Cell</entry><entry>Idle mode,</entry><entry>Idle mode,</entry><entry>Specified by the IE</entry><entry>Value tag</entry></row><row><entry>Information</entry><entry /><entry>CELL_FACH,</entry><entry>CELL_FACH,</entry><entry>“Scheduling</entry></row><row><entry>Block type</entry><entry /><entry>CELL_PCH,</entry><entry>CELL_PCH,</entry><entry>information”</entry></row><row><entry>18</entry><entry /><entry>URA_PCH,</entry><entry>URA_PCH</entry></row><row><entry /><entry /><entry>CELL_DCH</entry></row><row><entry namest="1" nameend="7" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0007While the previously employed NAS RAU procedure and the RRC URA update procedure will no longer apply, a new LTE tracking area update (TAU) procedure and its related LTE SI, operating procedures and tasks in various protocol levels and system levels will have to be defined.
0008Given the conceptual and architectural change, the LTE system information will have to reflect these changes and also be organized to facilitate the optimization of better WTRU operation and overall system resource utilization.
SUMMARY
0009The invention performs LTE TAUs, and tracking area code (TAC) and PLMN-ID assisted optimized WTRU cell reselection. An evolved Node-B (eNodeB) broadcasts system information including at least one SIB based at least in part on an enhanced universal terrestrial radio access network (E-UTRAN) parameter response message sent by an evolved packet core (EPC) network. A WTRU processes a new TAC, which represents a tracking area identification (TA-ID) of a new cell, based on the system information, and compares the new TAC to an existing TAC, which represents a TA-ID of a previous cell. The WTRU transmits to the EPC network a TAU request message including the TA-ID of the new cell. The EPC network sends either a TAU accept message or a TAU reject message to the WTRU.
0010The invention associates and groups the LTE specific mobility tracking area identifications, cell identifications and the PLMN-IDs together as system information for coverage over the E-UTRAN cells deployed in the neighborhood of a specific LTE cell that broadcasts the system information. The invention also provides an optimized method for LTE WTRUs to perform cell measurement and cell reselection ranking by utilizing the LTE system information for achieving the least possible TAU signaling overhead in the WTRU LTE_IDLE state.
0011Furthermore, new LTE TA-IDs are constructed, and a new LTE SIB is provided that publishes the TA code/IDs to the serving cell, as well as to group neighboring cells, represented by their cell-IDs with PLMN-IDs and TACs for the purpose of WTRU cell reselection optimization.
0012By using WTRU procedures for handling the TA related system information, the GMM unit in the NAS can perform the checking of the TAs broadcast in the system information, which is forwarded to the NAS by the RRC unit, with its current TA allowance, to determine if a TA change triggered TAU is required. Alternatively, for implementation advantage, the RRC unit may also perform the above described TA checking and then notify the NAS protocol stack if a TAU is required.
0013TACs are used as criteria in the cell reselection candidate cell selection, measurement scheduling, and ultimate cell reselection ranking ordering. The purpose is to reselect to the proper cell without causing unnecessary TAU.
0014High level control of tracking areas in the NAS protocol stack (i.e., software) and UMTS subscriber identity module (USIM) device that “list of forbidden TAs” must be implemented for high level WTRU mobility control. Operations on the list of forbidden TAs are described.
BRIEF DESCRIPTION OF THE DRAWINGS
0015The foregoing summary, as well as the following detailed description, will be better understood when read with reference to the appended drawings, wherein:
0016<figref idref="DRAWINGS">FIG. 1</figref> is a signaling diagram of an LTE TAU and cell reselection procedure implemented in a wireless communication system including an eNodeB, an EPC network and a WTRU;
0017<figref idref="DRAWINGS">FIG. 2</figref> is an example of a block diagram of the WTRU used to implement the LTE TAU and cell reselection procedure of <figref idref="DRAWINGS">FIG. 1</figref>;
0018<figref idref="DRAWINGS">FIG. 3</figref> is an example of a block diagram of the eNodeB used to implement the LTE TAU and cell reselection procedure of <figref idref="DRAWINGS">FIG. 1</figref>;
0019<figref idref="DRAWINGS">FIG. 4</figref> shows an example of a TA-ID information element (IE) included in an SIB transmitted by the eNodeB of <figref idref="DRAWINGS">FIG. 3</figref>; and
0020<figref idref="DRAWINGS">FIG. 5</figref> shows an example of an LTE system information block/element transmitted by the eNodeB of <figref idref="DRAWINGS">FIG. 3</figref>.
DETAILED DESCRIPTION
0021When referred to hereafter, the terminology “wireless transmit/receive unit (WTRU)” includes but is not limited to a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a computer, or any other type of user device capable of operating in a wireless environment. When referred to hereafter, the terminology “evolved Node-B (eNodeB)” includes but is not limited to a base station, a site controller, an access point (AP), or any other type of interfacing device capable of operating in a wireless environment.
0022Given the agreement in LTE mobility area tracking that “there is only one common TA concept defined for RAN and CN in LTE/SAE”, the tracking area concept replaces the current 3GPP routing area and UTRAN RA concepts and procedures. As a result, the LTE TAU procedure is a new procedure and therefore requires new mechanisms for support.
0023<figref idref="DRAWINGS">FIG. 1</figref> is a signaling diagram of an LTE TAU and cell reselection procedure <b>100</b> that is implemented in a wireless communication system including a WTRU <b>105</b>, an eNodeB <b>110</b> and an EPC network <b>115</b>.
0024<figref idref="DRAWINGS">FIG. 2</figref> is an example of a block diagram of the WTRU <b>105</b> used to implement the LTE TAU and cell reselection procedure <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>. The WTRU <b>105</b> may include a receiver <b>205</b>, a processor <b>210</b>, a transmitter <b>215</b>, a USIM <b>220</b> and at least one antenna <b>225</b>. The processor <b>210</b> may include a NAS protocol stack <b>120</b> and an access stratum (AS) protocol stack <b>230</b>. The NAS protocol stack <b>120</b> may include a GMM <b>235</b> or its LTE equivalent unit. The GMM <b>235</b> may include a TAU timer <b>240</b>. The AS protocol stack <b>230</b> may include an RRC unit <b>125</b>, a packet data convergence protocol (PDCP) unit <b>245</b>, a radio link control (RLC) unit <b>250</b>, a medium access control unit (MAC) unit <b>255</b> and a physical layer (PHY) <b>260</b>.
0025<figref idref="DRAWINGS">FIG. 3</figref> is an example of a block diagram of the eNodeB <b>110</b> used to implement the LTE TAU and cell reselection procedure <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>. The eNodeB <b>110</b> may include a receiver <b>305</b>, a processor <b>310</b>, a transmitter <b>315</b> and at least one antenna <b>320</b>. The processor <b>310</b> may include a self-configuration control unit <b>325</b> and an AS protocol stack <b>330</b>. The AS protocol stack <b>330</b> may include an RRC unit <b>335</b>, a PDCP unit <b>340</b>, an RLC unit <b>345</b>, a MAC unit <b>350</b> and a PHY <b>355</b>.
0026Referring to <figref idref="DRAWINGS">FIGS. 1 and 3</figref>, when the eNodeB <b>110</b> powers up, the processor <b>310</b> checks the connection/link of the eNodeB <b>310</b> with the EPC network <b>115</b>, identifies the primary serving access gateway (aGW), (not shown), that serves the EPC network <b>115</b>, and generates an E-UTRAN parameter request message <b>130</b> that is transmitted by the transmitter <b>315</b> via the antenna <b>320</b> of the eNodeB <b>110</b> to the EPC network <b>115</b>, via the identified primary serving aGW. The E-UTRAN parameter request message <b>130</b> may contain information associated with other EPC network connections, (other than the primary serving aGW and EPC network <b>115</b> in the so-called network sharing environment), information associated with connections of the eNodeB <b>110</b> with other identified eNodeBs, and the radio and channel load capabilities of the eNodeB <b>110</b>.
0027In response to receiving the E-UTRAN parameter request message <b>130</b>, the EPC network <b>115</b> transmits an E-UTRAN parameter response message <b>135</b>, which is received by the receiver <b>305</b> of the eNodeB <b>110</b>, and is then processed by the self-configuration control unit <b>325</b> in the processor <b>310</b>. The E-UTRAN parameter response message <b>135</b> may contain network area partitioning information, such as the location or tracking area IDs and their operating permissions (forbidden or not), and the policy the eNodeB <b>110</b> has to observe towards the connected EPC network <b>115</b>, (i.e., network sharing or network node relocation), and towards other connected eNodeBs in terms of handover and load balancing operating policies.
0028In step <b>140</b> of <figref idref="DRAWINGS">FIG. 1</figref>, the self-configuration control unit <b>325</b> in the processor <b>310</b> of the eNodeB <b>110</b> commands the signaling actions with the EPC network <b>115</b>, and summarizes information included in the E-UTRAN parameter response message <b>135</b> and other source information to form system information for the cell and the associated E-UTRAN. The self-configuration control unit <b>325</b> will then assemble the system information and format the SIBs, (e.g., combining/associating network/location area/cell-IDs into the proposed SIB and other SIBs). The RRC unit <b>335</b> in the AS protocol stack <b>330</b> of the eNodeB <b>110</b> is responsible for broadcasting the system information to the cell, and is also responsible for configuring each individual WTRU <b>105</b> in the cell for relevant operational RRC.
0029Now referring to <figref idref="DRAWINGS">FIGS. 1-3</figref>, the RRC unit <b>335</b> in AS protocol stack <b>330</b> of the eNodeB <b>110</b> then proceeds to broadcast system information to the whole cell via the PHY <b>355</b> of the AS protocol stack <b>330</b> in the processor <b>310</b>, the transmitter <b>315</b> and the antenna <b>320</b> of the eNodeB <b>110</b> over the cell's broadcast channels (step <b>145</b> of <figref idref="DRAWINGS">FIG. 1</figref>). Each WTRU <b>105</b>, (when powered up or moved to a new cell and having synchronized to a serving cell serviced by the eNodeB <b>110</b>), will automatically tune to the broadcast channel, in fixed frequency location, code and time configuration, of the cell and start reading the system information available to all WTRUs in the cell via the antenna <b>225</b>, the receiver <b>205</b> and the PHY <b>260</b> of the AS protocol stack <b>230</b>.
0030In step <b>150</b> of <figref idref="DRAWINGS">FIG. 1</figref>, the RRC unit <b>125</b> of the WTRU <b>105</b> receives, processes, stores and commands the reading of system information received by the PHY <b>260</b> from the receiver <b>205</b>, provides relevant information or parameter data to the GMM <b>235</b> in the NAS protocol stack <b>120</b> for mobility control, performs LTE cell reselection and configures the PDCP unit <b>245</b>, the RLC unit <b>250</b>, the MAC unit <b>255</b> and the PHY <b>260</b> for LTE E-UTRA data inputs and outputs, and other operations.
0031In step <b>155</b> of <figref idref="DRAWINGS">FIG. 1</figref>, based on the received system information, the RRC unit <b>125</b> then sends a TAC and other information to the GMM <b>235</b> in the NAS protocol stack <b>120</b> via an internal interface <b>265</b> between the AS protocol stack <b>230</b> and the NAS protocol stack <b>120</b>.
0032In step <b>160</b> of <figref idref="DRAWINGS">FIG. 1</figref>, the NAS protocol stack <b>120</b> performs an LTE TAU procedure during which the GMM <b>235</b> in NAS protocol stack <b>120</b> performs a comparison of the TAC provided by the RRC unit <b>125</b>, which represents the TA-ID of a new cell, against an existing TAC, which represents the TA-ID of a previous cell. Note that a single tracking area may cover many cells.
0033Referring to <figref idref="DRAWINGS">FIGS. 1-3</figref>, when the TAC indicates that the WTRU <b>105</b> is in a different tracking area, the NAS protocol stack <b>120</b> in the processor <b>210</b> of the WTRU <b>105</b> generates a TAU request message <b>165</b> including the TA-ID of the new cell, which is transmitted by the transmitter <b>215</b> via the antenna <b>225</b> to the EPC network <b>115</b>. In response to receiving the TAU request message <b>165</b>, the EPC network <b>115</b> sends either a TAU accept message <b>170</b>A or a TAU reject message <b>170</b>B to the WTRU <b>105</b>, which is forwarded via the PHY <b>260</b>, the MAC unit <b>255</b>, the RLC unit <b>250</b>, the PDCP unit <b>245</b> and the RRC unit <b>125</b> to the GMM <b>235</b> in NAS protocol stack <b>120</b> via the internal interface <b>265</b>.
0034The TAU accept message <b>170</b>A may contain the accepted TA-ID and, optionally, other TA-IDs for tracking areas that the WTRU <b>105</b> is allowed to operate in, (to reduce the need for performing additional TAU procedures). Optionally, these accepted TA-IDs may be used to remove a particular TA-ID in a “forbidden TA-ID list” stored in the GMM <b>235</b> if an accepted TA-ID matches the particular TA-ID.
0035The TAU reject message <b>170</b>B may contain a cause/reason for the rejection upon which the operating state of the GMM <b>235</b> may be changed. The TAU reject message <b>170</b>B may contain the rejected TA-ID, and optionally contain a list of other TAs that the WTRU <b>105</b> is not allowed to move into. The rejected TA-IDs may need to be added to the “forbidden TA-ID list” stored in the GMM <b>235</b> so that the WTRU <b>105</b> will not reselect to a cell under the TAs associated with these TA-IDs.
0036The RRC unit <b>125</b> in the WTRU <b>105</b> will then perform a TAC and PLMN-ID assisted optimized LTE WTRU cell reselection procedure <b>175</b> regularly. The cell reselection <b>175</b> shall not attempt to measure and reselect cells under the forbidden tracking areas (TA-IDs) in order to save processing and battery power.
0037In LTE, the RRC unit <b>335</b> in the eNodeB <b>110</b> still provides the mobility area management information, (i.e., the PLMN-IDs, the TACs and the cell-IDs), to one or more WTRUs <b>105</b> by broadcasting system information in a cell. The RRC unit <b>335</b> groups the mobility area IDs and network IDs together with cell IDs of the serving cell and neighboring cells to provide the associations of the LTE networks, TAs, and cells to WTRUs in order to supply the information for the LTE TA update as well as for the optimization of WTRU cell reselection with respect to the PLMN and TA information. Thus, the TA information to the cell and neighboring cells are grouped with PLMN information, to form a new LTE system information block or element for the association of the mobility areas and cells and network identities. The TA-ID, as used in the LTE TA update, needs to be defined and constructed.
0038The RRC unit <b>125</b> in the WTRU <b>105</b> receives system information broadcast by the eNodeB <b>110</b>, relays the system information, (in particular the TAC), to the NAS protocol stack <b>120</b>, utilizes the system information (association of network IDs, TACs and Cell-IDs) for implementing a TAU procedure and assists in performing the WTRU cell reselection process. The NAS protocol stack <b>120</b> utilizes the TAC provided by the RRC unit <b>125</b> for performing an LTE TAU procedure.
0039In LTE, the TAC is broadcast from the LTE system information to the relevant E-UTRAN cell and is used for the cell. Since it is also possible that one cell could belong to a number of TAs, or a WTRU could also be registered with multiple TAs, (where one cell belongs to one TA), one or more TACs may be included in the system information broadcast.
0040<figref idref="DRAWINGS">FIG. 4</figref> shows an example of a TA-ID IE <b>400</b> that may be included in an SIB generated by the self-configuration control unit <b>325</b> in the processor <b>310</b> of the eNodeB <b>110</b>. The TA-ID IE <b>400</b> may also be included in the TAU request message <b>165</b> or the TAU accept/reject messages <b>170</b>A and <b>170</b>B by the NAS protocol stack <b>120</b> in the WTRU <b>105</b>, or its counterpart in the EPC network <b>115</b>, to perform an LTE TAU procedure.
0041As shown in <figref idref="DRAWINGS">FIG. 4</figref>, the TA-ID IE <b>400</b> may include a coded <b>8</b>-bit TA identification IE-ID field <b>405</b>, and TAC fields <b>410</b>, <b>415</b> and <b>420</b> that provide up to <b>24</b> bits of field width (typically the field width used is <b>16</b>-<b>24</b> bits). The octet position field <b>425</b> is the element type and has mandatory presence (MP), as indicated by field <b>430</b>. The fields <b>432</b>, <b>434</b>, <b>436</b>, <b>438</b> , <b>440</b> and <b>442</b> represent the components of a normal PLMN. The labeled fields <b>444</b>, <b>446</b> and <b>448</b> indicate the octet position of the components (<b>432</b>/<b>434</b>, <b>436</b>/<b>438</b> and <b>440</b>/<b>442</b>) in the TA-ID IE <b>400</b>. As indicated by field <b>450</b>, the PLMN fields <b>432</b>-<b>448</b> have optional presence (OP), whereby x=1 when a PLMN is present, and x=0 if a PLMN is not present. Thus, when a PLMN is present, (x=1), fields <b>444</b>, <b>446</b> and <b>448</b> indicate octet positions of 2, 3 and 4. Otherwise, when a PLMN is not present, (x=0), the fields <b>432</b>-<b>442</b> do not exist, and fields <b>444</b>, <b>446</b> and <b>448</b> are ignored, since they would all indicate octet <b>1</b>, which would be the same as field <b>425</b>.
0042For example, if the TAC is globally unique regardless of which PLMN it belongs to, then the TA-ID is the same as the TAC, (see field <b>450</b>, where it is indicated that the PLMN field does not exist when x=0). If the TAC is only assigned by each network operator, (i.e., the TAC is per PLMN), then the TA-ID=PLMN-ID+TAC, (see field <b>450</b>, where it is indicated that the PLMN field is present when x=1), considering the roaming requirement.
0043The fields <b>410</b> and <b>415</b> represent a TAC and have MP, (corresponding to <b>16</b>-bits), as indicated by fields <b>452</b> and <b>454</b>. The field <b>420</b> represents the TAC continuation, (assuming that its width extends up to <b>24</b> bits), and has OP, as indicated by field <b>456</b>. For example, if the TA-ID IE <b>400</b> does not include a PLMN, then it consists of fields <b>405</b>, <b>410</b>, <b>415</b> and <b>420</b>. If the TA-ID includes a PLMN, then it consists of fields <b>405</b>, <b>410</b>, <b>415</b>, <b>420</b>, the mobile country code (MCC) digit fields <b>432</b>, <b>434</b> and <b>436</b>, and the mobile network code (MNC) digit fields <b>440</b>, <b>442</b> and <b>444</b>, which are in binary coded decimal (BCD) representation, (i.e. a 4-bit field with binary coding for digits <b>0</b>-<b>9</b>, e.g., ‘1001’ represents a 9).
0044<figref idref="DRAWINGS">FIG. 5</figref> shows an LTE SIB, (or system information element), <b>500</b> used for E-UTRAN TAU and for E-UTRAN mobility area identification management information. The E-UTRAN SIB <b>500</b> of <figref idref="DRAWINGS">FIG. 5</figref> is formed by the eNodeB <b>115</b> grouping the mobility area IDs and the available network IDs together as a clustered E-UTRAN SIB for broadcast in a cell. The various IDs and their associations provide the static/permanent or long term associations of the networks, the tracking areas with respect to all the cells in the neighborhood that the operations of the WTRU <b>105</b> may encounter. Note that this is independent of the neighboring cell information list, which is affected by the operational status of those neighboring cells, (sometimes available and sometimes not, due to problems with the EPC network <b>115</b> or the eNodeB <b>110</b>), which will also bear other cell reselection information not relevant here.
0045This E-UTRAN SIB first lists the ID associations with respect to the serving cell. The IDs may be the multiple TAs associated with the serving cell in the “overlapping TAs” scheme, or the one TA with the “multiple TAs registration” scheme, as indicated by field <b>505</b>.
0046The neighboring cells are then listed with the PLMN-ID and the associated TA-ID(s) sorted with the TA-IDs shown in the serving cell TA-IDs list first.
0047The information element (IE) list, (E-UTRAN mobility area information with neighboring cells in the system information block), also positions the cells (by cell-IDs) with similar PLMN-IDs together/adjacent for SIB signaling size reduction. Note that in <figref idref="DRAWINGS">FIG. 5</figref>, the PLMN-ID and the TAC are separated to save signaling space. The WTRU <b>105</b> may construct the TA-ID from them if the TA-ID=PLMN-ID+TAC. Otherwise, the TA-ID=TAC.
0048The LTE SIB, (or system IE), <b>500</b> of <figref idref="DRAWINGS">FIG. 5</figref> combines/groups the LTE cell-ID, TA-ID, (shown as the TAC), and the PLMN-ID together to provide convenient guidance for the WTRU <b>105</b> to process, i.e. to evaluate the neighboring cells with this network/tracking-area/cell association information for determining whether a reselection to a certain neighboring cell should be performed.
0049The invention builds maximum flexibility into the table representation of <figref idref="DRAWINGS">FIG. 5</figref> to suit two competing schemes of TA assignment to a cell, (i.e., the “multiple TAs registration” and the “overlapping TAs”), as indicated by field <b>505</b>. For the first “multiple TA” scheme, one serving cell will only be assigned to one TA, but multiple TAs can be assigned to a WTRU at the TAU time. For the second “overlapping TAs” scheme, a serving cell can be assigned to multiple TAs and the “maxTAsToACell” value in <figref idref="DRAWINGS">FIG. 5</figref> will be one, (i.e., one TA is assigned to a cell).
0050Referring to <figref idref="DRAWINGS">FIG. 5</figref>, column <b>510</b> indicates the information element name/group name. The “need” column <b>515</b> indicates the presence code (MP/OP) of the component there when formatting a message using this information block/element. The “multi” column <b>520</b> indicates whether multiple same component/element (but different value) has been put there to have a one-to-many-association. The “type and reference” column <b>525</b> provides further details/decomposition of a component/element in other element place. The “semantics” column <b>530</b> indicates how to format or process the element.
0051The LTE SIB, (or system IE), <b>500</b> shown in <figref idref="DRAWINGS">FIG. 5</figref> has a static or non-primary nature, whereby static means that it is not changing often with time, and non-primary means it is not to be broadcast via the primary broadcast channel (P-BCH) in LTE, and is broadcast through the dynamic broadcast channel (D-BCH) to the serving cell. This LTE SIB or system information element shall be read by the WTRU <b>105</b> in the LTE_IDLE mode and is mainly used while the WTRU <b>105</b> is in LTE_IDLE state The LTE SIB is associated with a particular serving cell.
0052The RRC unit <b>125</b> of the WTRU <b>105</b> reads this system information block (SIB) while in an LTE_IDLE when a new cell is entered. Frequent re-reading of this SIB is not necessary unless the cell indicates changes to this SIB. When the RRC unit <b>125</b> in the WTRU <b>105</b> has received the LTE system information broadcast about the serving cell's TACs, the RRC unit <b>125</b> may either pass the TAC(s) associated with the current serving cell to the NAS protocol stack <b>120</b> via the internal interface <b>265</b> and let the GMM <b>235</b> handle the TAU exclusively, or check the listed TAC(s) in the new serving cell against the currently used TAC(s) via the previous cell. If one of the new TAC(s) matches the currently used one, (or one of the currently registered TAs), the TA boundary is not crossed and a TAU is not required. Thus, the RRC can just hold the information. Otherwise, if there are no TACs matching, then the TAC(s) must be passed up to the NAS protocol stack <b>120</b> and let NAS protocol stack <b>120</b> perform the TAU. The purpose is to reduce the signaling/interaction overhead between the RRC unit <b>125</b> and the NAS protocol stack <b>120</b>.
0053Meanwhile, the RRC unit <b>125</b> of the WTRU <b>105</b> uses the associations of the PLMN-IDs, TACs and Cell-IDs broadcast in the SIB of <figref idref="DRAWINGS">FIG. 5</figref> for optimizing the WTRU cell reselection measurement and cell reselection ranking and decision process.
0054Measurement candidate cells shall be ordered with those cells in the front order: 1) those cells with H-PLMN; and those cells with the favorable TAC(s) (favorable TA(s) are those that the WTRU is currently registered with or those TAs that covers the previous cell from which the WTRU enters the new cell). Cells with favorable TACs (from the current TA's point of view) shall be in the front order for measurement scheduling with respect to the intra-frequency, inter-frequency, or in another radio access technology (RAT) measurements. Cells with favorable TAC(s) shall be ranked higher if the measured signal strength and other evaluation criteria are about the same with respect to those cells not possessing favorable TAC(s). The goal is to avoid the situation that a WTRU LTE cell reselection into a neighboring cell unnecessarily crossing the TA or group TA boundary and then an unnecessary LTE TAU has to be performed.
0055The GMM <b>235</b> of NAS protocol stack <b>120</b> in the WTRU <b>105</b> will perform TAU related operations if the TA entered by the WTRU <b>105</b> does not belong to a list of forbidden TAs. The forbidden TA list identifies one or more TAs that the WTRU <b>105</b> is not allowed to move into. The list may optionally be stored in the USIM <b>220</b> of the WTRU <b>105</b> when the WTRU <b>105</b> is powered off. When the WTRU is powered on, the list is loaded into the GMM <b>235</b>. The list may be modified by the TAU accept message <b>170</b>A or the TAU reject message <b>170</b>B.
0056Tracking Area change detected: If the TAC or TACs forwarded by the RRC do not have any single one matching the current TAC(s) or TA-ID(s) granted by the previous TAU accept message or by the retrieved TA-ID from the USIM <b>220</b> in the beginning of the WTRU power up, the NAS protocol stack <b>120</b> in the WTRU <b>105</b> shall initiate a TAU request or an attach effort in order to report its TA location to the EPC network <b>115</b>.
0057Periodic TAU: If the TAU timer <b>240</b> in the WTRU <b>105</b> indicates that a time period established for performing periodic TAUs has expired, the NAS protocol stack <b>120</b> in the WTRU <b>105</b> triggers a TAU to the EPC network <b>115</b>. When the WTRU <b>105</b> is in an LTE_IDLE state, the TAU timer <b>240</b> may, for example, be set within a range of <b>12</b> to <b>15</b> minutes or other values. If a TAU reject message <b>170</b>B is received, the subsequent TAU request(s) are administered by setting the TAU timer <b>240</b> to a much shorter range of <b>10</b>-<b>15</b> seconds or other values, in order to register with another TA to receive paging.
0058In the TAU, the WTRU <b>105</b> may also update the EPC network <b>115</b> with its radio access and/or security capability. The WTRU <b>105</b> may negotiate discontinuous reception (DRX) or update of connection context (such as the packet data protocol (PDP) context) with the EPC network <b>115</b>. DRX is a parameter which determines how often the WTRU <b>105</b> in idle mode shall wake up to monitor a paging channel for possible incoming calls. Note that the entries in the list of forbidden TAs are from two sources: the USIM device <b>220</b> and the TAU reject message <b>170</b>B. The TAU reject message <b>170</b>B is sent to the WTRU <b>105</b> if the EPC network <b>115</b> does not allow the WTRU <b>105</b> to obtain service from a reported tracking area. The TAU reject message <b>170</b>B may contain one or more IDs of rejecting TAs, if needed to also guide the WTRU <b>105</b> in making cell reselection choices. These rejected TA-IDs are added to the forbidden TA list.
0059Although the features and elements are described in the embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the embodiments or in various combinations with or without other features and elements of the invention. The methods or flow charts provided herein may be implemented in a computer program, software, or firmware tangibly embodied in a computer-readable storage medium for execution by a general purpose computer or a processor. Examples of computer-readable storage mediums include a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
0060Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.
0061A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC), or any host computer. The WTRU may be used in conjunction with modules, implemented in hardware and/or software, such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any wireless local area network (WLAN) module.
Contents6
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10764952B2 | Cited by | United States of America | Search report |
| US11533663B2 | Cited by | United States of America | Applicant |
| US11350345B2 | Cited by | United States of America | Applicant |
| US11394502B2 | Cited by | United States of America | Applicant |
| CN107231615A | Cited by | China | Search report |
| CN111742575A | Cited by | China | Search report |
| TWI705721B | Cited by | Taiwan Province of China | Examiner |
| CN110677890A | Cited by | China | Search report |
| US12302237B2 | Cited by | United States of America | Search report |
| US2023199589A1 | Cited by | United States of America | Search report |
| US12363670B2 | Cited by | United States of America | Applicant |
| US10841745B2 | Cited by | United States of America | Applicant |
| GB2610064A | Cited by | United Kingdom | Search report |
| CN105992286A | Cited by | China | Search report |
| US10587986B2 | Cited by | United States of America | Applicant |
| US8855668B2 | Cited by | United States of America | Search report |
| EP3711308A4 | Cited by | European Patent Office (EPO) | Search report |
| US10492133B2 | Cited by | United States of America | Applicant |
| US10412648B1 | Cited by | United States of America | Applicant |
| US2022022155A1 | Cited by | United States of America | Search report |
| EP3780787A4 | Cited by | European Patent Office (EPO) | Search report |
| US12200650B2 | Cited by | United States of America | Search report |
| US10051408B2 | Cited by | United States of America | Search report |
| US12192946B2 | Cited by | United States of America | Search report |
| US2023300734A1 | Cited by | United States of America | Search report |
| US11764916B2 | Cited by | United States of America | Applicant |
| US2015365789A1 | Cited by | United States of America | Pre-grant |
| CN111543071A | Cited by | China | Search report |
| US12004073B2 | Cited by | United States of America | Applicant |
| US11375426B2 | Cited by | United States of America | Applicant |
| CN108668340A | Cited by | China | Search report |
| US12160375B2 | Cited by | United States of America | Applicant |
| US2012071173A1 | Cited by | United States of America | Pre-grant |
| US10638381B2 | Cited by | United States of America | Applicant |
| US2019223246A1 | Cited by | United States of America | Search report |
| RU2740093C1 | Cited by | Russian Federation | Search report |
| US2022286995A1 | Cited by | United States of America | Search report |
| US12120565B2 | Cited by | United States of America | Search report |
| US2019007791A1 | Cited by | United States of America | Search report |
| US9019881B2 | Cited by | United States of America | Applicant |
| US2019007791A1 | Cited by | United States of America | Search report |
| US2003040314A1 | Cites | United States of America | Pre-grant |
| US2004072578A1 | Cites | United States of America | Pre-grant |
| US2005239461A1 | Cites | United States of America | Pre-grant |
| US2007037577A1 | Cites | United States of America | Pre-grant |
| US2007097983A1 | Cites | United States of America | Pre-grant |
| US2008019320A1 | Cites | United States of America | Pre-grant |
| US2009061878A1 | Cites | United States of America | Pre-grant |
| US7174184B2 | Cites | United States of America | Pre-grant |
34 members in 8 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 86352806 | United States of America | P | |
| 92303307 | United States of America | A |
Members34
| Document | Office | Kind | |
|---|---|---|---|
| US2008102896A1 | United States of America | A1 | |
| WO2008054668A2 | World Intellectual Property Organization (WIPO) | A2 | |
| TW200829045A | Taiwan Province of China | A | |
| WO2008054668A3 | World Intellectual Property Organization (WIPO) | A3 | |
| AR063444A1 | Argentina | A1 | |
| KR20090085640A | Republic of Korea | A | |
| KR20090085684A | Republic of Korea | A | |
| EP2090129A2 | European Patent Office (EPO) | A2 | |
| CN101536560A | China | A | |
| JP2010508761A | Japan | A | |
| TW201145930A | Taiwan Province of China | A | |
| EP2530981A1 | European Patent Office (EPO) | A1 | |
| JP2012253799A | Japan | A | |
| JP2012253800A | Japan | A | |
| KR20130016380A | Republic of Korea | A | |
| KR20130021441A | Republic of Korea | A | |
| CN101536560B | China | B | |
| CN103281775A | China | A | |
| US8649291B2 | United States of America | B2 | |
| KR101368588B1 | Republic of Korea | B1 | |
| JP5432339B2 | Japan | B2 | |
| US2014092871A1 | United States of America | A1 | |
| KR20140094660A | Republic of Korea | A | |
| KR101441227B1 | Republic of Korea | B1 | |
| TWI474697B | Taiwan Province of China | B | |
| TWI514910B | Taiwan Province of China | B | |
| TW201603612A | Taiwan Province of China | A | |
| JP5883741B2 | Japan | B2 | |
| KR101614993B1 | Republic of Korea | B1 | |
| JP2016077022A | Japan | A | |
| CN103281775B | China | B | |
| US9860817B2 | United States of America | B2 | |
| US2018098261A1 | United States of America | A1 | |
| EP2530981B1 | European Patent Office (EPO) | B1 |
55 transactions on the USPTO file
Allowed after 2 RCEs.
- Non-final rejections
- 0
- Final rejections
- 0
- RCEs
- 2
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Reasons for AllowanceEX.R | EX.R | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Preliminary AmendmentA.PE | A.PE | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Terminal Disclaimer FiledDIST | DIST | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| FITF set to NO - revise initial settingFTFI | FTFI | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Application Is Now CompleteCOMP | COMP | |
| Cleared by OIPE CSRL194 | L194 | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Entity status set to undiscounted (initial default setting or status change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 20140092871
- Application
- 14100891
Titles
- English
- METHOD AND APPARATUS FOR IMPLEMENTING TRACKING AREA UPDATE AND CELL RESELECTION IN A LONG TERM EVOLUTION SYSTEM
Patent term adjustment
- A delay
- +601 daysthe office missed an examination deadline
- Applicant delay
- −103 days
- Net adjustment
- 498 days
Classification
- CPC, 7
- H04W36/34
- H04W60/04
- H04W48/20
- H04W8/18
- H04W48/08
- H04W8/02
- H04W48/02
- IPC, 2
- H04W36 34
- H04W48 12