USRE48671E1 - Handling tracking area update reject without extended delay - Google Patents

Handling tracking area update reject without extended delay Download PDF

Info

Publication number
USRE48671E1
USRE48671E1 US15/978,054 US201315978054A USRE48671E US RE48671 E1 USRE48671 E1 US RE48671E1 US 201315978054 A US201315978054 A US 201315978054A US RE48671 E USRE48671 E US RE48671E
Authority
US
United States
Prior art keywords
attach procedure
notification
radio resource
resource control
procedure
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US15/978,054
Other languages
English (en)
Inventor
Jarkko Koskela
Hannu Bergius
Jorma Kaikkonen
Ari Laukkanen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to US15/978,054 priority Critical patent/USRE48671E1/en
Assigned to NOKIA TECHNOLOGIES OY reassignment NOKIA TECHNOLOGIES OY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NOKIA CORPORATION
Assigned to NOKIA CORPORATION reassignment NOKIA CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KOSKELA, JARKKO, BERGIUS, Hannu, LAUKKANEN, ARI, KAIKKONEN, JORMA
Application granted granted Critical
Publication of USRE48671E1 publication Critical patent/USRE48671E1/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • An example embodiment of the present invention relates to the field of mobile wireless communication, particularly to signaling procedures involved in handling of tracking area update (TAU) reject without extended delay.
  • TAU tracking area update
  • UE When multi-radio user equipment (UE) moves to long term evolution (LTE) (e.g. due to reselection procedure), and does not have Packet Data Protocol (PDP) context but has made a circuit-switched (CS) location update and optionally packet switched (PS) attachment to the operator network (NW), a problematic sequence follows.
  • UE establishes a radio resource control (RRC) connection in order to do a tracking area update (TAU).
  • TAU tracking area update
  • NW rejects TAU due to the missing PDP context. Then an RRC connection release message is sent to UE.
  • RRC radio resource control
  • the UE RRC layer will start handling it but it will delay processing the message for 60 ms in order to send a confirmation of the message reception to the NW (via radio link control acknowledgement (RLC ACK)). That is when the NW knows that it can release UE contexts in the evolved Node B (eNB) handling the NW to UE link.
  • RLC ACK radio link control acknowledgement
  • UE Immediately upon receiving the RRC release message, UE starts an ATTACH procedure in order to obtain PDP context, but because the RRC connection is being released, ATTACH fails. The failure is reported to the non-access stratum (NAS) layer.
  • NAS non-access stratum
  • an ATTACH retry timer (T3411, 10 seconds) is started.
  • the fixed 10 second retry timer causes a greater than 10 second delay in getting service in evolved universal mobile telecommunications service (UMTS) terrestrial radio access network (E-UTRAN).
  • UMTS evolved universal mobile telecommunications service
  • E-UTRAN evolved universal mobile telecommunications service
  • a method comprises receiving a downlink signal from a network entity indicating that a tracking area update (TAU) was rejected, receiving a downlink signal from a network entity commanding radio resource control (RRC) release, and beginning RRC release.
  • the method may further comprise notifying non access stratum (NAS) that RRC release is ongoing, placing NAS into hold status while RRC release is ongoing, notifying NAS that RRC release is complete, issuing an Attach request from NAS when RRC release is complete, and beginning random access signaling to establish a communications link with a network entity.
  • NAS non access stratum
  • an apparatus comprises at least a processor, a memory containing computer code instructions, said instructions when executed by the processor cause the apparatus to: process a downlink signal from a network entity indicating that a tracking area update (TAU) was rejected, process a downlink signal from a network entity commanding radio resource control (RRC) release, and beginning RRC release.
  • the instructions when executed by the processor, may further cause the apparatus to notify non access stratum (NAS) that RRC release is ongoing, place NAS into hold status while RRC release is ongoing, notify NAS that RRC release is complete, issue an Attach request from NAS when RRC release is complete, and begin random access signaling to establish a communications link with a network entity.
  • NAS non access stratum
  • a computer program product comprises a non-transitory computer-readable medium with program code instructions stored therein, said instructions, with a processor, causing a mobile terminal to execute the steps: receiving a downlink signal from a network entity indicating that a tracking area update (TAU) was rejected, receiving a downlink signal from a network entity commanding radio resource control (RRC) release, and beginning RRC release.
  • the instructions, with the processor, cause a mobile terminal to perform the steps: notifying non access stratum (NAS) that RRC release is ongoing, placing NAS into hold status while RRC release is ongoing, notifying NAS that RRC release is complete, issuing an Attach request from NAS when RRC release is complete, and beginning random access signaling to establish a communications link with a network entity.
  • NAS non access stratum
  • an apparatus comprises means for receiving a downlink signal from a network entity indicating that a tracking area update (TAU) was rejected, means for receiving a downlink signal from a network entity commanding radio resource control (RRC) release, and means for beginning RRC release.
  • the apparatus may further comprise means for notifying non access stratum (NAS) that RRC release is ongoing, means for placing NAS into hold status while RRC release is ongoing, means for notifying NAS that RRC release is complete, means for issuing an Attach request from NAS when RRC release is complete, and means for beginning random access signaling to establish a communications link with a network entity.
  • NAS non access stratum
  • FIG. 1 is a schematic drawing of a mobile wireless network connection
  • FIG. 2 is a schematic drawing of a mobile terminal
  • FIG. 3 is Part 1 of a signaling diagram illustrating LTE reselection
  • FIG. 4 is Part 2 of a signaling diagram illustrating LTE reselection
  • FIG. 5 is Part 3 of a signaling diagram illustrating LTE reselection
  • FIG. 6 is a revised Part 2 of the signaling diagram of FIG. 4 according to one embodiment of the invention.
  • FIG. 7 is flow diagram of the method embodiment of the invention.
  • circuitry refers to all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and (b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s) software (including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.
  • circuitry applies to all uses of this term in this application, including in any claims.
  • circuitry would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware.
  • circuitry would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or application specific integrated circuit for a mobile phone or a similar integrated circuit in server, a cellular network device, or other network device.
  • mobile terminals 10 may communicate with a network 14 utilizing an uplink from the mobile terminal 10 to the network 14 and a downlink from the network 14 to the mobile terminal.
  • the mobile terminals 10 may be of various types of mobile communication devices such as, for example, mobile telephones, personal digital assistants (PDAs), pagers, laptop computers, or any of numerous other hand held or portable communication devices, computation devices, content generation devices, content consumption devices, or combinations thereof, generally termed “user equipment” (UE).
  • the mobile terminal 10 may communicate with a network via an access point 12 , such as a Node B, an evolved Node B (eNB), a base station or the like, each of which comprises a radio frequency transmitter and receiver.
  • an access point 12 such as a Node B, an evolved Node B (eNB), a base station or the like, each of which comprises a radio frequency transmitter and receiver.
  • eNB evolved Node B
  • the mobile terminal 10 may communicate with various types of networks 14 including, for example, a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, a Global Systems for Mobile communications (GSM) network, a Code Division Multiple Access (CDMA) network, e.g., a Wideband CDMA (WCDMA) network, a CDMA2000 network or the like, a General Packet Radio Service (GPRS) network, a Universal Terrestrial Radio Access Network (UTRAN), a GSM Edge Radio Access Network (GERAN) or other type of network.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • GSM Global Systems for Mobile communications
  • CDMA Code Division Multiple Access
  • WCDMA Wideband CDMA
  • GPRS General Packet Radio Service
  • UTRAN Universal Terrestrial Radio Access Network
  • GERAN GSM Edge Radio Access Network
  • an apparatus 20 that may be embodied by or otherwise associated with a mobile terminal 10 may include or otherwise be in communication with a processor 22 , a memory device 24 , a communication interface 28 , and a user interface 30 .
  • the processor 22 (and/or co-processors or any other processing circuitry assisting or otherwise associated with the processor) may be in communication with the memory device 24 via a bus for passing information among components of the apparatus 20 .
  • the memory device 24 may include, for example, one or more non-transitory volatile and/or non-volatile memories.
  • the memory device 24 may be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processor).
  • the memory device 24 may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus to carry out various functions in accordance with an example embodiment of the present invention.
  • the memory device could be configured to buffer input data for processing by the processor.
  • the memory device 24 could be configured to store instructions for execution by the processor 22 .
  • the apparatus 20 may, in some embodiments, be embodied by a mobile terminal 10 .
  • the apparatus may be embodied as a chip or chip set.
  • the apparatus may comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard).
  • the structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon.
  • the apparatus may therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single “system on a chip.”
  • a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
  • the processor 22 may be embodied in a number of different ways.
  • the processor may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other processing circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like.
  • the processor may include one or more processing cores configured to perform independently.
  • a multi-core processor may enable multiprocessing within a single physical package.
  • the processor may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.
  • the processor may be embodied by the processor of the mobile terminal.
  • the processor 22 may be configured to execute instructions stored in the memory device 24 or otherwise accessible to the processor.
  • the processor may be configured to execute hard coded functionality.
  • the processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present invention while configured accordingly.
  • the processor when the processor is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein.
  • the processor when the processor is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed.
  • the processor may be a processor of a specific device (e.g., a mobile terminal 10 ) configured to employ an embodiment of the present invention by further configuration of the processor by instructions for performing the algorithms and/or operations described herein.
  • the processor may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor.
  • ALU arithmetic logic unit
  • the communication interface 28 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network 12 and/or any other device or module in communication with the apparatus 20 .
  • the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s).
  • the communications interface of one embodiment may include a plurality of cellular radios, such as a plurality of radio front ends and a plurality of base band chains.
  • the communication interface may alternatively or also support wired communication.
  • the communication interface may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.
  • the apparatus may include a user interface 30 that may, in turn, be in communication with the processor 22 to receive an indication of a user input and/or to cause provision of an audible, visual, mechanical or other output to the user.
  • the user interface may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen(s), touch areas, soft keys, a microphone, a speaker, or other input/output mechanisms.
  • the processor may comprise user interface circuitry configured to control at least some functions of one or more user interface elements such as, for example, a speaker, ringer, microphone, display, and/or the like.
  • the processor and/or user interface circuitry comprising the processor may be configured to control one or more functions of one or more user interface elements through computer program instructions (e.g., software and/or firmware) stored on a memory accessible to the processor (e.g., memory device and/or the like).
  • computer program instructions e.g., software and/or firmware
  • a memory accessible to the processor e.g., memory device and/or the like.
  • the processor 22 is the means for executing various functions that may be specified for preparing the mobile terminal for network communications.
  • the memory device 24 may contain program code instructions causing the processor to execute the various functions, or the processor may have memory associated with it that contains the program code instructions.
  • the means for executing various functions in the mobile terminal may include the memory with computer code instructions stored therein.
  • the communications interface 28 is the means for receiving signals from a network entity that are then processed to determine appropriate functions to be executed by the processor.
  • the initial conditions 30 are that UE is in a 2G or 3G configuration.
  • the location update for the UE is complete.
  • Idle Mode Signaling (ISR) is not active. Reselection of the UE to Long Term Evolution (LTE) begins.
  • PDP Packet Data Protocol
  • ISR Idle Mode Signaling
  • FIG. 3 shows the first part (of three parts) of the signaling sequence.
  • UE and a network node exchange several signals in the LTI reselection sequence.
  • the sequence also involves a network Mobility Management Entity (MME) and the Source GPRS Support Node (SGSN) (where GPRS is the General Packet Radio Service). While the illustrated sequence of signals is exchanged, the end user of a mobile device is without service waiting for the connection to be established/updated.
  • MME Mobility Management Entity
  • SGSN Source GPRS Support Node
  • radio resource control (RRC) setup is completed 32 and the Non Access Stratum (NAS) layer issues a Tracking Area Update (TAU) request 34 .
  • the TAU request 36 is directed by the node to the MME.
  • the MME issues an SGSN context request 38 to the SGSN, which is returned to the MME 40 denied because PDP context is missing. That leads the MME to reject the TAU request 42 through the node to the UE in a downlink message 44 . The node then directs that RRC be released 46 . To this point, the sequence has taken about two hundred and fifty (250) milliseconds.
  • the sequence continues with UE simultaneously taking two actions. It begins the RRC connection release procedure 48 while NAS initiates an Attach request 50 to obtain the PDP context that led to the TAU rejection. But, because RRC is being released, the Attach fails 51 . An NAS Attach retry timer is automatically activated 52 , which interposes a ten (10) second delay into the sequence.
  • the NAS triggers a second Attach request 54 attempting to register to LTE.
  • UE transmits a random access preamble 56 in an uplink message to the node, which sends a random access response 58 in a subsequent downlink message.
  • the connection sequence continues routinely to its conclusion where the UE is in service 60 , attach complete. However, the entire sequence required about eleven (11) seconds to complete while the end user waits without network service.
  • the object of a UE-based solution is to avoid activation of the NAS Attach retry timer so that the ten second delay does not activate.
  • the retry timer activates when an NAS Attach is attempted 51 while the RRC release procedure is ongoing. So, the initial solution is to prevent activation of the NAS Attach procedure during the RRC release procedure. This can be accomplished in more than one manner, each of which will be labeled in the following description.
  • RRC could indicate to NAS that the RRC release is in progress (Option 1 a). During the period that the RRC release is active, NAS would not initiate an Attach, but rather would wait some period of time. Either a fixed timer could run (set within UE programming) (Option 1 a(i)) or RRC could indicate to NAS that the connection release is complete (Option 1 a(ii)).
  • RRC could delay sending the message until the connection is released and then starts establishing new RRC connection (Option 1 b).
  • RRC could delay sending the message until the connection is released and then starts establishing new RRC connection (Option 1 b).
  • RRC indicates to NAS that the RRC connection is released during the ATTACH procedure (or any ongoing NAS procedure requiring RRC to convey the NAS message)
  • NAS could immediately restart the Attach without delay or according to a specific timer (which could be specified or left to the UE implementation) (Option 1 c).
  • the UE could eliminate the sixty millisecond delay in handling the RRC connection release (see FIG. 3 ) (Option 3 ). That would cause a new RRC connection establishment for the NAS Attach.
  • Option 3 a drawback of this solution is that the network would not necessarily receive confirmation of RRC connection release reception and the network could continue trying to reach the UE. Therefore, this solution though possible may not be favored.
  • the network function could be amended such that the network would not release the RRC connection when TAU is rejected for the missing PDP context (Option 4 ).
  • This approach would require the provision of an indication of TAU failure to the eNB (Option 4 a).
  • a new “cause” value could be defined to delay the release for some time (Option 4 b). The time could be specified or left to NW implementation—or configurable by the MME.
  • the Option 1 a(ii) solution is illustrated in a signaling diagram.
  • the eNB receives the TAU reject signal, it notifies UE to release the RRC connection 46 as before.
  • RRC would send a new indication to the NAS layer immediately when RRC Connection Release is received from eNB alerting NAS that RRC release has started 100 .
  • Receiving that information from RRC NAS goes into a “hold” state 110 (rather than attempting Attach, as before).
  • the RRC Release process 48 takes about sixty (60) milliseconds. Once RRC release is complete, NAS receives that indication from RRC 120 . Only then does NAS trigger a first Attach request 130 . As FIG. 6 indicates, the Attach process then proceeds with random access signaling 56 , 58 between UE and the eNB to establish the connection.
  • the sequence labeled Part 2 takes about seventy (70) milliseconds rather than over ten seconds.
  • the revised signaling process of FIGS. 3, 6 and 5 together would cause the end user of UE a wait of less than one second for LTE network connectivity.
  • FIG. 7 illustrates a flowchart of an example method, and/or computer program product according to example embodiments of the invention. It will be understood that each block or operation of the flowcharts, and/or combinations of blocks or operations in the flowcharts, can be implemented by various means. Means for implementing the blocks or operations of the flowcharts, combinations of the blocks or operations in the flowchart, or other functionality of example embodiments of the present invention described herein may comprise hardware, and/or a computer program product comprising a computer-readable storage medium having one or more computer program code instructions, program instructions, or executable computer-readable program code instructions stored therein.
  • program code instructions may be stored on a memory device, such as memory device 24 ( FIG. 2 ), of an example apparatus, such as example apparatus 20 , and executed by a processor, such as the processor 22 .
  • any such program code instructions may be loaded onto a computer or other programmable apparatus (e.g., processor 22 , memory device 24 ) from a computer-readable storage medium to produce a particular machine, such that the particular machine becomes a means for implementing the functions specified in the flowcharts' block(s) or operation(s).
  • These program code instructions may also be stored in a computer-readable storage medium that can direct a computer, a processor, or other programmable apparatus to function in a particular manner to thereby generate a particular machine or particular article of manufacture.
  • the instructions stored in the computer-readable storage medium may produce an article of manufacture, where the article of manufacture becomes a means for implementing the functions specified in the flowchart block(s) or operation(s).
  • the program code instructions may be retrieved from a computer-readable storage medium and loaded into a computer, processor, or other programmable apparatus to configure the computer, processor, or other programmable apparatus to execute operations to be performed on or by the computer, processor, or other programmable apparatus.
  • Retrieval, loading, and execution of the program code instructions may be performed sequentially such that one instruction is retrieved, loaded, and executed at a time. In some example embodiments, retrieval, loading and/or execution may be performed in parallel such that multiple instructions are retrieved, loaded, and/or executed together.
  • Execution of the program code instructions may produce a computer-implemented process such that the instructions executed by the computer, processor, or other programmable apparatus provide operations for implementing the functions specified in the flowchart block(s) or operation(s).
  • execution of instructions associated with the blocks or operations of the flowchart by a processor, or storage of instructions associated with the blocks or operations of the flowchart in a computer-readable storage medium support combinations of operations for performing the specified functions. It will also be understood that one or more blocks or operations of the flowchart, and combinations of blocks or operations in the flowchart, may be implemented by special purpose hardware-based computer systems and/or processors which perform the specified functions, or combinations of special purpose hardware and program code instructions.
  • UE receives a signal 610 from the eNB to release the RRC connection after the TAU request is rejected.
  • RRC notifies NAS that RRC release has begun 620 .
  • NAS enters a “hold” status 630 , avoiding the execution of an Attach attempt and retry timer activation.
  • RRC connection release runs 640 for a period of about sixty (60) milliseconds.
  • RRC informs NAS that the release is concluded 650 .
  • NAS is then free to trigger an Attach Request 660 . That request causes the UE to begin Random Access Signaling 670 to re-establish a network connection.
  • the end user has network service in about seventy milliseconds rather than eleven seconds.
  • NAS Non Access Stratum
  • eNB evolved NodeB
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • PDCP Packet Data Convergence Protocol
  • SGSN Service GPRS Support Node
  • GPRS General Packet Radio Service

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Medicines That Contain Protein Lipid Enzymes And Other Medicines (AREA)
  • Peptides Or Proteins (AREA)
US15/978,054 2012-05-09 2013-05-06 Handling tracking area update reject without extended delay Active 2033-05-09 USRE48671E1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/978,054 USRE48671E1 (en) 2012-05-09 2013-05-06 Handling tracking area update reject without extended delay

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201261644763P 2012-05-09 2012-05-09
US14/396,255 US9918292B2 (en) 2012-05-09 2013-05-06 Handling tracking area update reject without extended delay
US15/978,054 USRE48671E1 (en) 2012-05-09 2013-05-06 Handling tracking area update reject without extended delay
PCT/FI2013/050492 WO2013167802A1 (en) 2012-05-09 2013-05-06 Handling tracking area update reject without extended delay

Publications (1)

Publication Number Publication Date
USRE48671E1 true USRE48671E1 (en) 2021-08-03

Family

ID=49550196

Family Applications (2)

Application Number Title Priority Date Filing Date
US15/978,054 Active 2033-05-09 USRE48671E1 (en) 2012-05-09 2013-05-06 Handling tracking area update reject without extended delay
US14/396,255 Ceased US9918292B2 (en) 2012-05-09 2013-05-06 Handling tracking area update reject without extended delay

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/396,255 Ceased US9918292B2 (en) 2012-05-09 2013-05-06 Handling tracking area update reject without extended delay

Country Status (15)

Country Link
US (2) USRE48671E1 (pt)
EP (1) EP2848037B1 (pt)
JP (1) JP5988466B2 (pt)
KR (1) KR101665224B1 (pt)
CN (1) CN104365148B9 (pt)
AU (2) AU2013257862A1 (pt)
BR (1) BR112014027912B1 (pt)
CA (1) CA2872531C (pt)
MX (1) MX342893B (pt)
PH (1) PH12014502459A1 (pt)
PL (1) PL2848037T3 (pt)
RU (1) RU2586106C1 (pt)
SG (1) SG11201407324UA (pt)
WO (1) WO2013167802A1 (pt)
ZA (1) ZA201408929B (pt)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103747492A (zh) * 2014-01-08 2014-04-23 华为终端有限公司 终端接入长期演进网络的方法和终端
US9814090B2 (en) * 2014-03-12 2017-11-07 Mediatek Inc. Maintaining a packet-switched signaling connection during handover between cells
US10244455B2 (en) 2014-08-29 2019-03-26 Huawei Technologies Co., Ltd. Mobility management procedure initiation method and device
JP2016122887A (ja) * 2014-12-24 2016-07-07 富士通株式会社 無線基地局、無線デバイス、無線通信システム、及び、無線通信制御方法
EP3437392B1 (en) * 2016-03-28 2022-03-02 Apple Inc. Tau on ims call request in radio access networks
JP6882509B2 (ja) * 2017-03-24 2021-06-02 テレフオンアクチーボラゲット エルエム エリクソン（パブル） Ｒｒｃ非アクティブ状態のための周期タイマー同期論理
US10390308B2 (en) 2017-09-08 2019-08-20 Apple Inc. Messaging control in mobile devices based on signal conditions
CN112088542B (zh) 2018-05-07 2024-04-30 瑞典爱立信有限公司 用于处置拒绝时的无线电接入网通知区域（rna）更新配置的方法和设备
CN109104719B (zh) * 2018-08-23 2021-10-29 南京佰联信息技术有限公司 获取移动设备标识信息的方法、装置和系统
US11182181B2 (en) 2018-09-25 2021-11-23 International Business Machines Corporation Virtual environments generator
CN115103347B (zh) * 2022-06-08 2024-05-14 Oppo广东移动通信有限公司 跟踪区更新方法、装置、电子设备和计算机可读存储介质

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2184944A1 (en) 2008-10-20 2010-05-12 HTC Corporation Method of improving radio resource control connection establishment in a wireless communication system
CN101888684A (zh) 2009-05-14 2010-11-17 中兴通讯股份有限公司 无线资源控制连接重建失败后快速连接建立的方法及系统
US20110170429A1 (en) * 2010-01-08 2011-07-14 Sycamore Networks, Inc. Mobile broadband packet switched traffic optimization
US20120082105A1 (en) 2010-10-01 2012-04-05 Nokia Siemens Networks Oy Radio resource control connection release message wait timer
GB2489725A (en) 2011-04-06 2012-10-10 Nec Casio Mobile Comm Ltd Non-access stratum signalling to indicate use of new or existing NAS signalling connection for connection re-establishment.
US20130012204A1 (en) * 2011-07-08 2013-01-10 Lg Electronics Inc. Method and terminal for performing detach procedure
US20130040605A1 (en) * 2011-08-10 2013-02-14 Nokia Siemens Networks Oy Methods and apparatus for radio resource control
US8515436B2 (en) 2008-03-27 2013-08-20 Qualcomm Incorporated Management of wireless connections
US8934334B2 (en) * 2012-03-16 2015-01-13 Lg Electronics Inc. Method and apparatus for processing NAS signaling request in wireless communication system
US8938236B2 (en) 2010-01-08 2015-01-20 Ntt Docomo, Inc. Mobile device redirecting technology

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2375001T3 (es) * 2007-01-15 2012-02-23 Telefonaktiebolaget Lm Ericsson (Publ) Método y disposiciones para localizar un equipo de usuario para servicios de circuitos conmutados mediante una red de comunicación lte de paquetes conmutados.
CN101986761B (zh) * 2010-11-01 2013-05-22 新邮通信设备有限公司 一种小区切换失败后保持用户特定业务的方法和一种ue

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8515436B2 (en) 2008-03-27 2013-08-20 Qualcomm Incorporated Management of wireless connections
EP2184944A1 (en) 2008-10-20 2010-05-12 HTC Corporation Method of improving radio resource control connection establishment in a wireless communication system
CN101888684A (zh) 2009-05-14 2010-11-17 中兴通讯股份有限公司 无线资源控制连接重建失败后快速连接建立的方法及系统
US20110170429A1 (en) * 2010-01-08 2011-07-14 Sycamore Networks, Inc. Mobile broadband packet switched traffic optimization
US8938236B2 (en) 2010-01-08 2015-01-20 Ntt Docomo, Inc. Mobile device redirecting technology
US20120082105A1 (en) 2010-10-01 2012-04-05 Nokia Siemens Networks Oy Radio resource control connection release message wait timer
GB2489725A (en) 2011-04-06 2012-10-10 Nec Casio Mobile Comm Ltd Non-access stratum signalling to indicate use of new or existing NAS signalling connection for connection re-establishment.
WO2012137978A1 (en) 2011-04-06 2012-10-11 Nec Casio Mobile Communication, Ltd. Mobile radio communications signalling
EP2695476A1 (en) 2011-04-06 2014-02-12 NEC CASIO Mobile Communications, Ltd. Mobile radio communications signalling
US20130012204A1 (en) * 2011-07-08 2013-01-10 Lg Electronics Inc. Method and terminal for performing detach procedure
US20130040605A1 (en) * 2011-08-10 2013-02-14 Nokia Siemens Networks Oy Methods and apparatus for radio resource control
US8934334B2 (en) * 2012-03-16 2015-01-13 Lg Electronics Inc. Method and apparatus for processing NAS signaling request in wireless communication system

Non-Patent Citations (12)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 10)", 3GPP TS 23.401, V10.7.0, Mar. 2012, pp. 1-278.
3GPP R2-122537 Excessive TAU delay, Nokia Corporation RAN WG2, Prague, Czech Republic, May 14, 2012.
3GPP TS 24.01 V10.6.1 (Mar. 2012). 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Status (NAS) protocol for Evolved Packet System (EPS); stage 3 (Release 10).
3GPP TS 24.01 V10.6.1 (Mar. 2012). 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratus (NAS) protocol for Evolved Packet System (EPS); stage 3 (Release 10).
3GPP TS 36.331 V10.5.0 (Mar. 2012). 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 10).
3GPP TSG RAN WG5: "LS on Automatic re-attach following TAU reject or Service Request reject", 3GPP DRAFT; R5-110835 LS TO CT1 ON AUTOMATIC RE-ATTACH FOLLOWING TAU REJECT OR SERVICE REQUEST, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG5, no. Taipei, Taiwan; 20110221 - 20110225, R5-110835 LS to CT1 on Automatic re-attach followi, 26 February 2011 (2011-02-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP050617678
3GPP TSG RAN WG5: "LS on Automatic re-attach following TAU reject or Service Request reject," Searched (IPC) 3GPP Draft; R5-110835 LS to CT1 on Automatic Reattach Following TAU Reject or Service Request, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, vol. RAN WG5, no. Taipei, Taiwan; Feb. 21, 2011-Feb. 25, 2011, Feb. 26, 2011 (Feb. 26, 2011), XP050617678, [retrieved on Feb. 26, 2011] * the whole document *.
International Search Report and Written Opinion received for corresponding Patent Cooperation Treaty Application No. PCT/FI2013/050492, dated Aug. 26, 2013, 14 pages.
Motorola Mobility, "GCF Priority 2—Correction to EMM test case 9.3.1.7," 3GPP Draft; 36523-1 CR1237 (REL-9)_R5-110775, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France. vol. RAN WG5, No. Taipei, Taiwan; Mar. 9, 2011, Feb. 21, 2011, Feb. 26, 2011, XP050512297, [retrieved on Mar. 9, 2011].
MOTOROLA MOBILITY: "GCF Priority 2 - Correction to EMM test case 9.3.1.7", 3GPP DRAFT; 36523-1_CR1237_(REL-9)_R5-110775, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG5, no. Taipei, Taiwan; 20110221, 36523-1_CR1237_(Rel-9)_R5-110775, 9 March 2011 (2011-03-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP050512297
Nec et al., "Handling of re-attach following TAU reject or Service Request reject," 3GPP Draft; C1-111700-Disc-Reattach-TAU-Serv-Reject, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France. vol. CT WG1, No. Tallinn; May 9, 2011, May 2, 2011.
Office action received for corresponding Vietnam Patent Application No. 1-2014-03749, dated Apr. 24, 2015, 1 page.

Also Published As

Publication number Publication date
BR112014027912A2 (pt) 2017-06-27
KR101665224B1 (ko) 2016-10-11
SG11201407324UA (en) 2014-12-30
EP2848037A1 (en) 2015-03-18
PH12014502459A1 (en) 2014-12-22
AU2017251784B2 (en) 2020-01-02
PL2848037T3 (pl) 2019-09-30
AU2013257862A1 (en) 2014-10-30
RU2586106C1 (ru) 2016-06-10
MX342893B (es) 2016-10-18
WO2013167802A1 (en) 2013-11-14
BR112014027912B1 (pt) 2023-04-11
EP2848037A4 (en) 2016-03-09
JP5988466B2 (ja) 2016-09-07
MX2014013644A (es) 2015-03-03
JP2015519832A (ja) 2015-07-09
KR20150008456A (ko) 2015-01-22
CA2872531C (en) 2019-01-08
ZA201408929B (en) 2016-09-28
CA2872531A1 (en) 2013-11-14
EP2848037B1 (en) 2019-04-10
AU2017251784A1 (en) 2017-11-16
CN104365148B9 (zh) 2018-08-21
US20150119032A1 (en) 2015-04-30
US9918292B2 (en) 2018-03-13
CN104365148B (zh) 2018-07-06
CN104365148A (zh) 2015-02-18

Similar Documents

Publication Publication Date Title
AU2017251784B2 (en) Handling tracking area update reject without extended delay
CN106937317B (zh) 通信装置及安全模式命令失败的恢复方法
ES2786042T3 (es) Gestión de parámetros proporcionados en liberación/suspensión
US20120207011A1 (en) Method and apparatus for responding to an unrecoverable error
RU2660632C2 (ru) Способ обработки службы с коммутацией каналов (cs) нисходящей линии связи и объект управления мобильностью
CN104303587A (zh) 对偶网络无线电资源管理中的快速通信恢复
WO2018040109A1 (zh) 一种无线通信的方法和装置
US20130237198A1 (en) System and method for managing data calls
WO2023109687A1 (zh) 条件小区变换方法、装置、ue及网络侧设备
JP2023554486A (ja) セカンダリセルグループの制御方法、端末及びネットワーク側機器
JP2017076982A (ja) セル更新手続中におけるセキュリティ構成を一致させる方法，装置，およびコンピュータプログラム
CN114765810B (zh) 配置方法、装置、设备及可读存储介质
WO2020064384A1 (en) Connection resume handling
WO2022206959A1 (zh) 主辅小区配置方法、装置、ue、网络侧设备及可读存储介质
US20230111158A1 (en) Method and apparatus for suspending secondary cell group
US20230086504A1 (en) Method and apparatus for leaving network, and terminal
WO2022022568A1 (zh) 数据传输方法、装置、核心网设备及接入网侧设备
EP4322572A1 (en) Paging method, device, and storage medium
WO2024027638A1 (zh) Ue能力控制方法、装置、终端及网络侧设备
US20200137716A1 (en) Method and user equipment for handling service connectivity in wireless communication system
CN116158128A (zh) 用于非活动直接数据传输的上下文提取过程

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: NOKIA CORPORATION, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KOSKELA, JARKKO;BERGIUS, HANNU;KAIKKONEN, JORMA;AND OTHERS;SIGNING DATES FROM 20120520 TO 20120529;REEL/FRAME:045907/0781

Owner name: NOKIA TECHNOLOGIES OY, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA CORPORATION;REEL/FRAME:045907/0788

Effective date: 20150116

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4