EP2465288B1 - Systems and methods of maintaining core network status during serving radio network subsystem relocation - Google Patents

Systems and methods of maintaining core network status during serving radio network subsystem relocation Download PDF

Info

Publication number
EP2465288B1
EP2465288B1 EP10747737.4A EP10747737A EP2465288B1 EP 2465288 B1 EP2465288 B1 EP 2465288B1 EP 10747737 A EP10747737 A EP 10747737A EP 2465288 B1 EP2465288 B1 EP 2465288B1
Authority
EP
European Patent Office
Prior art keywords
srns
rnc
target
fast dormancy
processor
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
Application number
EP10747737.4A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2465288A1 (en
Inventor
Kiran Kishanrao Patil
Liangchi Hsu
Rohit Kapoor
Sharad Deepak Sambhwani
Aziz Gholmieh
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.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP2465288A1 publication Critical patent/EP2465288A1/en
Application granted granted Critical
Publication of EP2465288B1 publication Critical patent/EP2465288B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/10—Reselecting an access point controller
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to techniques for improving battery life in wireless mobile devices by enabling them to enter a dormant or idle mode.
  • Wireless communication networks are widely deployed to provide various communication services such as telephony, video, data, messaging, broadcasts, and so on.
  • Such networks which are usually multiple access networks, support communications for multiple users by sharing the available network resources.
  • UTRAN UMTS Terrestrial Radio Access Network
  • the UTRAN is the radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), a third generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3GPP).
  • UMTS Universal Mobile Telecommunications System
  • 3GPP 3rd Generation Partnership Project
  • the UMTS which is the successor to Global System for Mobile Communications (GSM) technologies, currently supports various air interface standards, such as Wideband-Code Division Multiple Access (W-CDMA), Time Division-Code Division Multiple Access (TD-CDMA), and Time Division-Synchronous Code Division Multiple Access (TD-SCDMA).
  • W-CDMA Wideband-Code Division Multiple Access
  • TD-CDMA Time Division-Code Division Multiple Access
  • TD-SCDMA Time Division-Synchronous Code Division Multiple Access
  • the UMTS also supports enhanced 3G data communications protocols, such as High Speed Packet Access (HSDPA), which provides higher data transfer speeds and capacity to associated UMTS networks.
  • HSDPA High Speed Packet Access
  • Document EP 1 377 096 A1 discloses a wireless communications device that supports a Radio Resource Control (RRC) layer having a plurality of states, which include states in which no uplink communications are possible with a base station.
  • the RRC layer receives a configuration procedure from the base station that initiates a base station relocation procedure from the base station for the wireless device.
  • the wireless device transmits confirmation to the base station in response to the configuration procedure.
  • the RRC layer receives acknowledgement that the base station successfully received the confirmation information.
  • the RRC re-establishes a Radio Link Control (RLC) entity supported by the wireless device to effect the base station relocation procedure.
  • RLC Radio Link Control
  • WO 2009/062304 A1 discloses a method and network element for sending a transition indication to transition a user equipment to a different state or mode, the method receiving a configuration message from a network; and transmitting a transition indication from the user equipment, the transition indication only includes a cause if the configuration message contains an inhibit transition indication. Also, a method and user equipment for processing a transitioning indication from a user equipment indicating the user equipment desires a transition to a different state or mode, the method comprising: receiving the transition indication from the user equipment; if the transition indication contains a cause: releasing a signaling connection of the user equipment or transitioning the user equipment to a different state or mode; and if the transition indication does not contain the cause: releasing the signaling connection.
  • a method of wireless communication includes receiving a notification to relocate from a source serving radio network subsystem (SRNS) to a target SRNS and determining whether a target radio network controller (RNC) corresponding to the target SRNS supports a fast dormancy feature. If the target RNC supports the fast dormancy feature, the user equipment (UE) may enter a dormant state, power saving state, or idle state to save battery life.
  • SRNS source serving radio network subsystem
  • RNC target radio network controller
  • an apparatus of wireless communication includes means for receiving a notification to relocate from a source SRNS to a target SRNS, and means for determining whether a target RNC corresponding to the target SRNS supports a fast dormancy feature. If the target RNC supports the fast dormancy feature, the UE includes means for entering a dormant state, power saving state, or idle state to save battery life.
  • a computer program product includes a computer-readable medium having code for receiving a notification to relocate from a source SRNS to a target SRNS, and for determining whether a target RNC corresponding to the target SRNS supports a fast dormancy feature. If the target RNC supports the fast dormancy feature, the computer-readable medium has code for entering a dormant state, power saving state, or idle state.
  • an apparatus for wireless communication includes at least one processor and a memory coupled to the at least one processor.
  • the at least one processor is configured to receive a notification to relocate from a source SRNS to a target SRNS, and to determine whether a target RNC corresponding to the target SRNS supports a fast dormancy feature. If the target RNC supports the fast dormancy feature, the processor is configured to enter a dormant state. power saving state, or idle state.
  • processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • One or more processors in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the software may reside on a computer-readable medium.
  • a computer-readable medium may include, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., compact disk (CD), digital versatile disk (DVD)), a smart card, a flash memory device (e.g., card, stick, key drive), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a register, a removable disk, a carrier wave, a transmission line, and any other suitable medium for storing or transmitting software.
  • the computer-readable medium may be resident in the processing system, external to the processing system, or distributed across multiple entities including the processing system.
  • Computer-readable medium may be embodied in a computer-program product.
  • a computer-program product may include a computer-readable medium in packaging materials.
  • FIG. 1 is a conceptual diagram illustrating an example of a hardware implementation for an apparatus 100 employing a processing system 114.
  • the processing system 114 may be implemented with a bus architecture, represented generally by the bus 102.
  • the bus 102 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 114 and the overall design constraints.
  • the bus 102 links together various circuits including one or more processors, represented generally by the processor 104, and computer-readable media, represented generally by the computer-readable medium 106.
  • the bus 102 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • a bus interface 108 provides an interface between the bus 102 and a transceiver 110.
  • the transceiver 110 provides a means for communicating with various other apparatus over a transmission medium.
  • a user interface 112 e.g., keypad, display, speaker, microphone, joystick
  • keypad e.g., keypad, display, speaker, microphone, joystick
  • the processor 104 is responsible for managing the bus 102 and general processing, including the execution of software stored on the computer-readable medium 106.
  • the software when executed by the processor 104, causes the processing system 114 to perform the various functions described infra for any particular apparatus.
  • the computer-readable medium 106 may also be used for storing data that is manipulated by the processor 104 when executing software.
  • a UMTS network includes three interacting domains: a Core Network (CN) 204, a UTRAN 202, and UE 210.
  • CN Core Network
  • UTRAN 202 provides various wireless services including telephony, video, data, messaging, broadcasts, and/or other services.
  • the UTRAN 202 may include a plurality of Serving Radio Network Subsystems (SRNSs) such as an SRNSs 207, each controlled by a respective Radio Network Controller (RNC) such as an RNC 206.
  • SRNSs Serving Radio Network Subsystems
  • RNC Radio Network Controller
  • the UTRAN 202 may include any number of RNCs 206 and SRNSs 207 in addition to the RNCs 206 and SRNSs 207 illustrated herein.
  • the RNC 206 is an apparatus responsible for, among other things, assigning, reconfiguring and releasing radio resources within the SRNS 207.
  • the RNC 206 may be interconnected to other RNCs (not shown) in the UTRAN 202 through various types of interfaces such as a direct physical connection, a virtual network, or the like, using any suitable transport network.
  • the geographic region covered by the SRNS 207 may be divided into a number of cells, with a radio transceiver apparatus serving each cell.
  • a radio transceiver apparatus is commonly referred to as a Node B in UMTS applications, but may also be referred to by those skilled in the art as a base station (BS), a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), or some other suitable terminology.
  • BS basic service set
  • ESS extended service set
  • AP access point
  • three Node Bs 208 are shown in each SRNS 207; however, the SRNSs 207 may include any number of wireless Node Bs.
  • the Node Bs 208 provide wireless access points to a core network (CN) 204 for any number of mobile apparatuses.
  • a mobile apparatus include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a notebook, a netbook, a smartbook, a personal digital assistant (PDA), a satellite radio, a global positioning system (GPS) device, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, or any other similar functioning device.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • GPS global positioning system
  • multimedia device e.g., a digital audio player (e.g., MP3 player), a camera, a game console, or any other similar functioning device.
  • MP3 player digital audio player
  • the mobile apparatus is commonly referred to as user equipment (UE) in UMTS applications, but may also be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.
  • the UE 210 may further include a universal subscriber identity module (USIM) 211, which contains a user's subscription information to a network.
  • USIM universal subscriber identity module
  • DL downlink
  • UL uplink
  • the CN domain 204 interfaces with one or more access networks, such as the UTRAN 202.
  • the core network 204 is a GSM core network.
  • GSM Global System for Mobile communications
  • the core network 204 includes a circuit-switched (CS) domain and a packet-switched (PS) domain.
  • Some of the circuit-switched elements are a Mobile services Switching Centre (MSC), a Visitor location register (VLR) and a Gateway MSC.
  • Packet-switched elements include a Serving GPRS Support Node (SGSN) and a Gateway GPRS Support Node (GGSN).
  • Some network elements, like EIR, HLR, VLR and AuC may be shared by both of the circuit-switched and packet-switched domains.
  • the core network 204 supports circuit-switched services with a MSC 212 and a GMSC 214.
  • the GMSC 214 may be referred to as a media gateway (MGW).
  • MGW media gateway
  • the MSC 212 is an apparatus that controls call setup, call routing, and UE mobility functions.
  • the MSC 212 also includes a visitor location register (VLR) that contains subscriber-related information for the duration that a UE is in the coverage area of the MSC 212.
  • VLR visitor location register
  • the GMSC 214 provides a gateway through the MSC 212 for the UE to access a circuit-switched network 216.
  • the GMSC 214 includes a home location register (HLR) 215 containing subscriber data, such as the data reflecting the details of the services to which a particular user has subscribed.
  • HLR home location register
  • the HLR is also associated with an authentication center (AuC) that contains subscriber-specific authentication data.
  • AuC authentication center
  • the GMSC 214 queries the HLR 215 to determine the UE's location and forwards the call to the particular MSC serving that location.
  • the core network 204 also supports packet-data services with a serving GPRS support node (SGSN) 218 and a gateway GPRS support node (GGSN) 220.
  • GPRS which stands for General Packet Radio Service, is designed to provide packet-data services at speeds higher than those available with standard GSM circuit-switched data services.
  • the GGSN 220 provides a connection for the RAN 202 to a packet-based network 222.
  • the packet-based network 222 may be the Internet, a private data network, or some other suitable packet-based network.
  • the primary function of the GGSN 220 is to provide the UEs 210 with packet-based network connectivity. Data packets are transferred between the GGSN 220 and the UEs 210 through the SGSN 218, which performs primarily the same functions in the packet-based domain as the MSC 212 performs in the circuit-switched domain.
  • the UMTS air interface is a spread spectrum Direct-Sequence Code Division Multiple Access (DS-CDMA) system.
  • DS-CDMA Spread spectrum Direct-Sequence Code Division Multiple Access
  • the W-CDMA air interface is based on such direct sequence spread spectrum technology and additionally calls for a frequency division duplexing (FDD).
  • FDD uses a different carrier frequency for the UL and DL between a Node B 208 and a UE 210.
  • the multiple access wireless communication system includes multiple cellular regions (cells), including cells 302, 304, and 306, each of which may include one or more sectors.
  • the multiple sectors can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell. For example, in cell 302, antenna groups 312, 314, and 316 may each correspond to a different sector.
  • antenna groups 318, 320, and 322 each correspond to a different sector.
  • antenna groups 324, 326, and 328 each correspond to a different sector.
  • the cells 302, 304 and 306 may include several wireless communication devices, e.g., User Equipment or UEs, which may be in communication with one or more sectors of each cell 302, 304 or 306.
  • UEs 330 and 332 may be in communication with Node B 342
  • UEs 334 and 336 may be in communication with Node B 344
  • UEs 338 and 340 can be in communication with Node B 346.
  • each Node B 342, 344, 346 is configured to provide an access point to a core network 204 (see FIG. 2 ) for all the UEs 330, 332, 334, 336, 338, 340 in the respective cells 302, 304, and 306.
  • the UMTS signaling protocol stack may be divided into Access Stratum (AS) and Non-Access Stratum (NAS).
  • AS Access Stratum
  • NAS Non-Access Stratum
  • the NAS is a functional layer between the UE and the core network, managing functions and services that are independent from the access technology.
  • the AS supports the NAS by managing functions and protocols for the transport of information across the UTRAN (UMTS Terrestrial Access Network) and air interface.
  • UTRAN UMTS Terrestrial Access Network
  • the NAS may include a Connection Management unit for handling circuit-switched calls, and may include sublayers responsible for call control (e.g., establish, release), supplementary services (e.g., call forwarding, 3-way calling), and short message service (SMS).
  • the NAS may further include a Session Management unit for handling packet-switched calls (e.g., establish, release).
  • the NAS may further include a Mobility Management module for handling location updating and authentication for circuit-switched calls.
  • the NAS may further include a GPRS mobility management unit for handling location updating and authentication for packet-switched calls.
  • the AS may include a Radio Resource Control (RRC) unit having protocols that are defined between the UE and RNC to handle establishment, release, and configuration of radio resources.
  • the AS may further include a Radio Link Control (RLC) unit having protocols that are defined between the UE and RNC to provide segmentation, re-assembly, duplicate detection, and other traditional Layer 2 functions.
  • the AS may further include a Medium Access Control (MAC) unit having protocols that are defined between UE and RNC to multiplex user plane and control plane data.
  • the AS may further include a Physical Layer unit having protocols that are defined between the UE and Node B to transfer data over the radio link.
  • the interface between UE and RNC at the Physical Layer handles macrodiversity combining and splitting functions.
  • the NAS may employ services provided by the RRC (i.e., the upper layer of the AS), such as an initial direct transfer procedure, a downlink direct transfer procedure, and an uplink transfer procedure.
  • the initial direct transfer procedure may be used to establish a signaling connection. It may also be used to carry the initial higher layer (NAS) messages over the radio interface.
  • the downlink direct transfer procedure may be used in the downlink direction to carry NAS messages over the radio interface.
  • the uplink direct transfer procedure may be used in the uplink direction to carry NAS messages over the radio interface belonging to a signaling connection.
  • a signaling connection which may be established at the initial direct transfer procedure, may be maintained at the RRC until it is not explicitly requested to close by the NAS.
  • RRC Radio Resource Control
  • Certain portions of the instant disclosure will utilize protocols and terminology specific to 3GPP TS 25.331, v9.1.0 ("Radio Resource Control (RRC) Protocol Specification"), incorporated by reference herein in its entirety, in order to provide improved clarity of the details described herein. However, those skilled in the art will comprehend that other protocols and standards may be utilized.
  • the modulation and multiple access scheme employed by the access network 300 may vary depending on the particular telecommunications standard being deployed.
  • the standard may include Evolution-Data Optimized (EV-DO) or Ultra Mobile Broadband (UMB).
  • EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations.
  • 3GPP2 3rd Generation Partnership Project 2
  • the standard may alternately be Universal Terrestrial Radio Access (UTRA) employing Wideband-CDMA (W-CDMA) and other variants of CDMA, such as TD-SCDMA; Global System for Mobile Communications (GSM) employing TDMA; and Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM employing OFDMA.
  • UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from the 3GPP organization.
  • CDMA2000 and UMB are described in documents from the 3GPP2 organization.
  • the actual wireless communication standard and the multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system.
  • the Node B may have multiple antennas supporting MIMO technology.
  • MIMO technology enables the Node B 342 to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity.
  • Spatial multiplexing may be used to transmit different streams of data simultaneously on the same frequency.
  • the data steams may be transmitted to a single UE (e.g., 330) to increase the data rate or to multiple UEs (e.g., 330, 332) to increase the overall system capacity.
  • This is achieved by spatially precoding each data stream and then transmitting each spatially precoded stream through a different transmit antenna on the downlink.
  • the spatially precoded data streams arrive at the UE(s) 330, 332 with different spatial signatures, which enables each of the UE(s) 330, 332 to recover the one or more the data streams destined for that UE 330, 332.
  • each UE 330 transmits a spatially precoded data stream, which enables the Node B 342 to identify the source of each spatially precoded data stream.
  • Beamforming may be used to focus the transmission energy in one or more directions. This may be achieved by spatially precoding the data for transmission through multiple antennas. To achieve good coverage at the edges of the cell, a single stream beamforming transmission may be used in combination with transmit diversity.
  • FIG. 4 is a block diagram of a Node B 410 in communication with a UE 450 in a RAN 400, where the RAN 400 may be the RAN 202 in FIG. 2 , the Node B 410 may be the Node B 208 in FIG. 2 , and the UE 450 may be the UE 210 in FIG. 2 .
  • a transmit processor 420 may receive data from a data source 412 and control signals from a controller/processor 440.
  • the transmit processor 420 provides various signal processing functions for the data and control signals, as well as reference signals (e.g., pilot signals).
  • the transmit processor 420 may provide cyclic redundancy check (CRC) codes for error detection, coding and interleaving to facilitate forward error correction (FEC), mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM), and the like), spreading with orthogonal variable spreading factors (OVSF), and multiplying with scrambling codes to produce a series of symbols.
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • OVSF orthogonal variable spreading factors
  • channel estimates may be derived from a reference signal transmitted by the UE 450 or from feedback contained in the midamble 214 ( FIG. 2 ) from the UE 450.
  • the symbols generated by the transmit processor 420 are provided to a transmit frame processor 430 to create a frame structure.
  • the transmit frame processor 430 creates this frame structure by multiplexing the symbols with a midamble 214 ( FIG. 2 ) from the controller/processor 440, resulting in a series of frames.
  • the frames are then provided to a transmitter 432, which provides various signal conditioning functions including amplifying, filtering, and modulating the frames onto a carrier for downlink transmission over the wireless medium through smart antennas 434.
  • the smart antennas 434 may be implemented with beam steering bidirectional adaptive antenna arrays or other similar beam technologies.
  • a receiver 454 receives the downlink transmission through an antenna 452 and processes the transmission to recover the information modulated onto the carrier.
  • the information recovered by the receiver 454 is provided to a receive frame processor 460, which parses each frame, and provides the midamble 214 ( FIG. 2 ) to a channel processor 494 and the data, control, and reference signals to a receive processor 470.
  • the receive processor 470 then performs the inverse of the processing performed by the transmit processor 420 in the Node B 410. More specifically, the receive processor 470 descrambles and despreads the symbols, and then determines the most likely signal constellation points transmitted by the Node B 410 based on the modulation scheme.
  • the soft decisions may be based on channel estimates computed by the channel processor 494.
  • the soft decisions are then decoded and deinterleaved to recover the data, control, and reference signals.
  • the CRC codes are then checked to determine whether the frames were successfully decoded.
  • the data carried by the successfully decoded frames will then be provided to a data sink 472, which represents applications running in the UE 450 and/or various user interfaces (e.g., display).
  • Control signals carried by successfully decoded frames will be provided to a controller/processor 490.
  • the controller/processor 490 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.
  • ACK acknowledgement
  • NACK negative acknowledgement
  • a transmit processor 480 In the uplink, data from a data source 478 and control signals from the controller/processor 490 are provided to a transmit processor 480.
  • the data source 478 may represent applications running in the UE 450 and various user interfaces (e.g., keyboard). Similar to the functionality described in connection with the downlink transmission by the Node B 410, the transmit processor 480 provides various signal processing functions including CRC codes, coding and interleaving to facilitate FEC, mapping to signal constellations, spreading with OVSFs, and scrambling to produce a series of symbols.
  • Channel estimates may be used to select the appropriate coding, modulation, spreading, and/or scrambling schemes.
  • the symbols produced by the transmit processor 480 will be provided to a transmit frame processor 482 to create a frame structure.
  • the transmit frame processor 482 creates this frame structure by multiplexing the symbols with a midamble 214 ( FIG. 2 ) from the controller/processor 490, resulting in a series of frames.
  • the frames are then provided to a transmitter 456, which provides various signal conditioning functions including amplification, filtering, and modulating the frames onto a carrier for uplink transmission over the wireless medium through the antenna 452.
  • the uplink transmission is processed at the Node B 410 in a manner similar to that described in connection with the receiver function at the UE 450.
  • a receiver 435 receives the uplink transmission through the antenna 434 and processes the transmission to recover the information modulated onto the carrier.
  • the information recovered by the receiver 435 is provided to a receive frame processor 436, which parses each frame, and provides the midamble 214 ( FIG. 2 ) to the channel processor 444 and the data, control, and reference signals to a receive processor 438.
  • the receive processor 438 performs the inverse of the processing performed by the transmit processor 480 in the UE 450.
  • the data and control signals carried by the successfully decoded frames may then be provided to a data sink 439 and the controller/processor, respectively. If some of the frames were unsuccessfully decoded by the receive processor, the controller/processor 440 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.
  • ACK acknowledgement
  • the controller/processors 440 and 490 may be used to direct the operation at the Node B 410 and the UE 450, respectively.
  • the controller/processors 440 and 490 may provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the computer readable media of memories 442 and 492 may store data and software for the Node B 410 and the UE 450, respectively.
  • a scheduler/processor 446 at the Node B 410 may be used to allocate resources to the UEs and schedule downlink and/or uplink transmissions for the UEs.
  • Fast dormancy is a feature for packet data users, generally supported by an RNC, which enables a substantial reduction in the amount of time that a UE is required to remain in an active state, thus improving battery life.
  • live field test results indicate an improvement in standby time of over 100% on a UMTS device utilizing fast dormancy to send the UE to idle in existing networks.
  • Fast dormancy additionally releases radio resources not being used and moves the UE to an idle mode or a so-called "URA_PCH" state (defined in the 3GPP RRC protocol specification) so that the network may free up extra capacity that may be utilized for other users.
  • a UE may have completed its data transfer and not expect further data exchange, the UE must wait for the network to move it from the CELL_DCH or CELL_FACH state to the idle mode or to the CELL_PCH or URA_PCH state (each of these states is also defined in the 3GPP RRC protocol specification). This is because the network may not know whether the UE has more data to transfer, and therefore may keep the UE in these data transfer states for a much longer period than necessary. The network does this to avoid an additional setup delay for subsequent packet data transfers, in the event that there are in fact more data packets to transfer.
  • the UE's application layer generally autonomously determines whether it has any more data to exchange.
  • application layer acknowledgement for the data transfer
  • application specific inactivity timers the UE is able to determine reliably when it is appropriate to send an indication to the network indicating that the UE no longer needs this signaling connection, as data transfer is complete, by including a cause value indicating the end of the data transfer session.
  • the fast dormancy feature allows the UE to send this indication to the network in an RRC Signaling Connection Release Indication (SCRI) message. In this way, the network can make an informed decision about how to handle this UE.
  • SCRI RRC Signaling Connection Release Indication
  • the network may decide to release the signaling connection, in which case it may then decide to release the RRC connection and let the UE become idle.
  • it may keep the UE in the CELL_PCH or URA_PCH state in order to achieve similar battery savings while ensuring a quicker reconfiguration for data transfer in the more distant future.
  • Such behavior is described as fast dormancy, as the UE moves from active data transfer to idle much faster than traditionally waiting for inefficient inactivity timers to expire.
  • FIG. 5 is a call flow diagram 500 illustrating an issue with a prior art procedure for relocating a UE 502 from a source RNC (RNC-1) 504, which supports a fast dormancy feature, to a target RNC (RNC-2) 506, which does not support the fast dormancy feature. That is, in this scenario, the UE 502 and the target RNC 506 may lose synchronization with regard to the core network domain status.
  • five sequential phases are designated with the numbers 1-5 on the lefthand side of the illustration, where time moves forward in a downward direction according to the illustration.
  • the illustration shows communication occurring directly between the UE and the RNCs or the PS domain of the CN, those skilled in the art will comprehend that these arrows represent higher-layer communication that relies on lower-layer communication between other entities such as a NodeB, etc.
  • the UE 502 establishes an RRC connection with RNC-1 504.
  • the UE 502 provides an RRC connection request message 510 to the RNC-1 504, for example, utilizing the uplink CCCH, including an initial UE identity and an establishment cause value, with a domain indicator set to indicate the PS-domain.
  • the RNC-1 504 may then respond with an RRC connection setup message 512, for example, utilizing the downlink CCCH, including the parameters needed to establish packet-switched communication.
  • the UE 502 provides an initial direct transfer 514 to initiate a packet-switched call to the packet-switched domain of the core network 508.
  • radio bearer (RB) reconfiguration message 516 is sent from the source RNC 504 to the UE 502, including an instruction for the UE 502 to relocate from a source SRNS, serviced by the source RNC (RNC-1) 504, to a target SRNS, serviced by the target RNC (RNC-2) 506.
  • This reconfiguration/relocation may be requested due to a change in QoS, due to differences in services available at the two SRNSs, or for any other suitable reason.
  • a relocation procedure may be requested as a portion of any one or more of the following RRC reconfiguration messages from the source RNC 504: RADIO BEARER RECONFIGURATION (as illustrated, 516), PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER RELEASE, RADIO BEARER SETUP, TRANSPORT CHANNEL RECONFIGURATION, CELL UPDATE CONFIRM, URA UPDATE CONFIRM, etc.
  • the UE 502 may provide a RB reconfiguration complete message 518 to the target RNC 506 indicating that the reconfiguration has been done.
  • an application/entity in the UE 502 may become idle when no data traffic is exchanged between the UE 502 and the RNC 506. Accordingly, this state of no data exchange may be noticed at the UE 502, in which case the application may turn down an active state and trigger a dormant state, power saving state, or idle state (e.g., to save battery life). Accordingly, an indicator such as a message may be sent from the radio resource control layer in the UE 502 to the RNC 506.
  • the UE 502 provides a signaling connection release indication (SCRI) message 520.
  • SCRI signaling connection release indication
  • the SCRI message 520 may be used by the UE 502 to request for the network to initiate a state transition to a dormant, idle, or essentially any battery efficient RRC state such as CELL_PCH or URA_PCH.
  • a radio link failure occurs thereafter with respect to the RNC 506 because the RNC 506 does not support the fast dormancy feature.
  • the UE 502 and the RNC 506 become out of sync after to the relocation, and at phase 6, the behavior in the UE 502 becomes unknown to the network. That is, the PS domain of the core network 508 is open with respect to the UE 502, and yet is closed with respect to the RNC 506.
  • Current information in messaging as described below does not address such issues.
  • a timer T323 may be kept in the UE 502, as well as in the RNC 506.
  • the timer T323 may be a timer for managing the release of a signaling connection and termination of a packet-switched data session.
  • Those skilled in the art will be familiar with the timer T323 as defined in the UMTS RRC protocol specification TS 25.331.
  • expiry of the timer T323 may be utilized to trigger a low-power mode in the UE and a release of radio resources assigned to that UE.
  • the UE retains a valid value of the timer T323 stored in an information element (IE) called "UE Timers and constants in connected mode" in the variable TIMERS_AND_CONSTANTS of system information block (SIB) type 1.
  • IE information element
  • UE Timers and constants in connected mode in the variable TIMERS_AND_CONSTANTS of system information block (SIB) type 1.
  • SIB system information block
  • the UE 502 in order to indicate the fast dormancy feature the UE 502 conventionally re-uses an existing RRC message called the signaling connection release indication (SCRI) with a new cause.
  • SCRI signaling connection release indication
  • the UE 502 generally does not close the packet-switched domain of the core network 508 from the ESTABLISHED_SIGNALING_CONNECTIONS (that is, a variable used to store information about established signaling connections including a signaling connection list).
  • the SCRI message and procedure is conventionally utilized by the UE 502 to indicate to the UTRAN that one of its signaling connections has been released. This procedure may in turn initiate an RRC connection release procedure.
  • RNC RNC-2
  • the RNC 506 does not support the fast dormancy feature, it fails to recognize the different cause of the SCRI message, and may release the connection with the packet-switched domain of the core network 508.
  • the UE 502 and the RNC 506 conventionally go out of sync with respect to the packet-switched domain open status as a consequence of the relocation from the RNC-1 504, which supports the fast dormancy feature, to the RNC-2 506, which does not support the fast dormancy feature. Subsequent packet-switched calls or packet-switched signaling messages from the UE 502 may then be dropped by the network, breaking the NAS layer functionality.
  • an open status of a packet-switched domain of a core network is synchronized at a UE and at an RNC when SRNS relocation occurs while a fast dormancy feature is active.
  • the UE may always assume that the target RNC does not support the fast dormancy feature, and thus, the UE may disable the fast dormancy feature at the SRNS relocation. In this way, although the UE does not know whether the new RNC supports this feature, the potential loss of synchronization may be avoided.
  • the drawback to this approach is the disabling of the fast dormancy feature even in a scenario where it may have been supported, whereby the UE would not indicate to the target RNC that it does not have any data to send in the uplink, resulting in a shortened battery life at the UE.
  • the status of the packet-switched domain of the core network may be synchronized by exchanging reconfiguration messages between the UE and the target RNC, wherein timers are employed to preserve UE/network synchronization, and while a UE application has triggered UE dormancy.
  • the timer T323 value may be carried in the reconfiguration messages in a way to support synchronization.
  • each type of reconfiguration message (e.g., the messages RADIO BEARER RECONFIGURATION, PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER RELEASE, RADIO BEARER SETUP, TRANSPORT CHANNEL RECONFIGURATION, CELL UPDATE CONFIRM, and URA UPDATE CONFIRM) sent from an RNC to the UE may carry an information element (IE) corresponding to the timer T323 value when a network supports the fast dormancy feature.
  • IE information element
  • a source RNC 504 may communicate to a UE 502 that a target RNC 506 to which the UE 502 is to relocate does or does not support the fast dormancy feature.
  • the source RNC 504 and the target RNC 506 may include a communication interface on a backhaul connection, e.g., being a direct link between the target and source RNCs, or a connection through an intermediary, for example, in the core network.
  • each type of reconfiguration message sent from an RNC to the UE may carry an IE corresponding to the timer T323 value when the timer T323 value has changed; when the timer T323 value has not changed, but the network supports the fast dormancy feature, each type of reconfiguration message may carry a simple indication, such as a single bit, to indicate that the network supports the fast dormancy feature. In this way, the amount of air transmission overhead may be reduced when compared to the transmission of the IE corresponding to the timer T323 value.
  • reconfiguration messages are utilized by the network for various types of reconfiguration within the same cell, unnecessary overhead still may occur when the T323 value has changed even though a SRNS relocation is not being requested.
  • reconfiguration messages that are requesting an SRNS relocation to a target RNC that supports the fast dormancy feature may carry the IE corresponding to the timer T323 value when the timer T323 value has changed; when the timer T323 value is unchanged but the target RNC supports the fast dormancy feature the reconfiguration message may include a simple indication such as a single bit to indicate that the target RNC supports the fast dormancy feature. In this way, the unnecessary overhead in broadcasting the IE corresponding to the timer T323 value in each reconfiguration message (i.e., those messages even where an SRNS relocation is not being requested) can be substantially reduced.
  • the air transmission overhead can be reduced when the timer T323 value is unchanged, by virtue of the transmission only of the simple indication instead of the IE corresponding to the timer T323 value.
  • the source RNC 504 and the target RNC 506 may require communication of the timer T323 value over a backhaul connection. This communication of the timer T323 value may be difficult to implement in existing networks.
  • reconfiguration messages that are requesting an SRNS relocation to a target RNC that supports the fast dormancy feature may carry the IE corresponding to the timer T323 value.
  • the UE may interpret the presence of the IE corresponding to the timer T323 value as an indication that the target RNC to which an SRNS relocation is to take place supports the fast dormancy feature. That is, if a reconfiguration message that is requesting an SRNS relocation does not include the IE corresponding to the timer T323 value, then the UE will understand this as an indication that the target RNC to which the SRNS relocation is to take place does not support the fast dormancy feature.
  • the UE may handle signaling with the target RNC following the SRNS relocation as a legacy RNC, and may properly maintain synchronization as to the status of the packet-switched domain of the core network.
  • coordination among RNCs as to the value of the timer T323 is not required.
  • FIG. 6 is a flow chart illustrating a process of relocating a UE from a source RNC to a target RNC according to an aspect of the instant disclosure.
  • the process may be performed by circuitry or a processor as illustrated in FIG. 1 .
  • the process may be performed by a combination of a plurality of RNCs 206 and a UE 210 as illustrated in FIG. 2 .
  • portions of the process may be performed by the UE 450 of FIG. 4 .
  • the process may be performed by the UE and RNC illustrated in FIG. 7 , described below.
  • the process sends a first reconfiguration message from a first RNC to a UE.
  • the first reconfiguration message is utilized by the network to change a configuration of the UE without relocating the UE.
  • the first reconfiguration message may be a PHYSICAL CHANNEL RECONFIGURATION message.
  • the process reconfigures the UE responsive to the first reconfiguration message.
  • the process sends a second reconfiguration message from the first RNC to the UE.
  • the second reconfiguration message includes a notification for the UE that it is to undergo an SRNS relocation from a first SRNS corresponding to the first RNC, to a second SRNS corresponding to a second (target) RNC.
  • the second reconfiguration message may be a RADIO BEARER RECONFIGURATION message.
  • other reconfiguration messages may include the notification for the UE that it is to undergo the SRNS relocation.
  • the process determines at the UE whether the second, target RNC corresponding to the target SRNS supports a fast dormancy feature.
  • the UE may determine whether the target RNC supports the fast dormancy feature by looking for an indicator within the second reconfiguration message received from the first, source RNC, that the target RNC supports the fast dormancy feature.
  • the indicator may be a single bit within the second reconfiguration message designated for this purpose; the indicator may be an information element corresponding to the timer T323 value; or any other suitable indicator for indicating that the target RNC supports the fast dormancy feature.
  • the process moves to block 610; otherwise, if the second reconfiguration message does not indicate that the target RNC supports the fast dormancy feature, then the process moves to block 616.
  • the process performs an SRNS relocation, wherein the UE undergoes a relocation from the source SRNS corresponding to the source RNC, to the target SRNS corresponding to the target RNC.
  • the target RNC supports the fast dormancy feature, and the UE is aware of this situation due to the notification received by the UE in the second reconfiguration message, the UE may enter a dormant state when it is determined that there is an absence of data to transfer from the UE to the network. For example, as described above, an application or entity in the UE may detect this condition and trigger the dormant state, such as an idle state in the UE.
  • the process moves to block 612, wherein the UE provides an SCRI message including an indication that the UE will enter the dormant state to the second, target RNC. Then, in block 614, the UE enters the dormant state, such as the idle state, the CELL_PCH or URA_PCH state, or any suitable battery-saving state. The process then ends.
  • the process has determined in block 608 that the target RNC does not support the fast dormancy feature, that is, the target RNC may be a legacy RNC.
  • the process relocates the UE from the source RNC to the target RNC as instructed.
  • the process undergoes legacy operation of the UE and target RNC, without utilizing the fast dormancy feature. For example, with legacy operation, when the target RNC receives an SCRI message from the UE, if the IE "Signaling Connection Release Indication Cause" is not included in the SCRI message, the target RNC may request the release of the signaling connection.
  • FIG. 7 is a conceptual block diagram of a UE 702 and an RNC 704 according to an aspect of the instant disclosure.
  • the UE 702 and the RNC 704 each includes various electronic components for performing certain functions.
  • the UE 702 includes an electronic component 706 for receiving an SRNS relocation message, e.g., from a source RNC and an electronic component 708 for determining whether an SRNS, e.g., the target SRNS to which the UE 702 has been instructed to relocate, supports a fast dormancy feature.
  • an SRNS relocation message e.g., from a source RNC
  • an electronic component 708 for determining whether an SRNS, e.g., the target SRNS to which the UE 702 has been instructed to relocate, supports a fast dormancy feature.
  • the UE 702 further includes an electronic component 710 for providing an SCRI message, e.g., including an indication that the UE will enter a dormant state; an electronic component 712 for detecting an absence of data to transfer to an RNC; and an electronic component 714 for entering a dormant state.
  • the RNC 704 includes an electronic component 716 for receiving an SCRI message from a UE and an electronic component 718 for providing a reconfiguration message to a UE.
  • the RNC 704 may further include electronic components within the dashed box 720. That is, the RNC 704 may include an electronic component 722 for supporting a fast dormancy feature and an electronic component 724 for receiving an indication that a UE with which it has a connection will enter a dormant state.
  • TD-SCDMA High Speed Downlink Packet Access
  • HSDPA High Speed Downlink Packet Access
  • HSUPA High Speed Uplink Packet Access
  • HSPA+ High Speed Packet Access Plus
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • CDMA2000 Evolution-Data Optimized
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Ultra-Wideband
  • Bluetooth Bluetooth
  • the actual telecommunication standard, network architecture, and/or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.
  • processors have been described in connection with various apparatuses and methods. These processors may be implemented using computer software, various electrical components such as electronic hardware, or any combination thereof. Whether such processors are implemented as hardware or software will depend upon the particular application and overall design constraints imposed on the system.
  • a processor, any portion of a processor, or any combination of processors presented in this disclosure may be implemented with a microprocessor, microcontroller, digital signal processor (DSP), a field-programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gated logic, discrete hardware circuits, and other suitable processing components configured to perform the various functions described throughout this disclosure.
  • DSP digital signal processor
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • the functionality of a processor, any portion of a processor, or any combination of processors presented in this disclosure may be implemented with software being executed by a microprocessor, microcontroller, DSP, or other suitable platform.
  • the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media may be transitory or non-transitory, and may include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a general purpose or special purpose computer.
  • non-transitory computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
  • Computer-readable media may be embodied in a computer-program product.
  • a computer-program product may include a computer-readable medium in packaging materials.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP10747737.4A 2009-08-11 2010-08-11 Systems and methods of maintaining core network status during serving radio network subsystem relocation Active EP2465288B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US23304309P 2009-08-11 2009-08-11
US12/853,937 US8638711B2 (en) 2009-08-11 2010-08-10 Systems and methods of maintaining core network status during serving radio network subsystem relocation
PCT/US2010/045192 WO2011019832A1 (en) 2009-08-11 2010-08-11 Systems and methods of maintaining core network status during serving radio network subsystem relocation

Publications (2)

Publication Number Publication Date
EP2465288A1 EP2465288A1 (en) 2012-06-20
EP2465288B1 true EP2465288B1 (en) 2017-06-07

Family

ID=42983400

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10747737.4A Active EP2465288B1 (en) 2009-08-11 2010-08-11 Systems and methods of maintaining core network status during serving radio network subsystem relocation

Country Status (10)

Country Link
US (1) US8638711B2 (es)
EP (1) EP2465288B1 (es)
JP (2) JP5583768B2 (es)
KR (1) KR101364654B1 (es)
CN (2) CN102474769B (es)
BR (1) BR112012003056B1 (es)
ES (1) ES2639415T3 (es)
HU (1) HUE035879T2 (es)
TW (1) TWI450607B (es)
WO (1) WO2011019832A1 (es)

Families Citing this family (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2262328B1 (en) 2005-12-14 2012-09-26 Research In Motion Limited Method and apparatus for user equipment directed radio resource control
DE602006017517D1 (de) 2006-05-17 2010-11-25 Research In Motion Ltd Verfahren und System zur Anzeige einer Ursache für einen Abbau einer Signalisierungsverbindung in einem UMTS Netz
US20080049662A1 (en) * 2006-08-25 2008-02-28 Research In Motion Limited Apparatus, and associated method, for releasing a data-service radio resource allocated to a data-service-capable mobile node
US8085714B2 (en) * 2007-09-29 2011-12-27 Jaakko Johannes Sitomaniemi Method, apparatus and computer program product for preserving a signalling connection
ATE553628T1 (de) 2007-11-13 2012-04-15 Research In Motion Ltd Verfahren und vorrichtung für status- /modusübergänge
AU2009313191B2 (en) * 2008-11-10 2014-03-13 Blackberry Limited Method and apparatus of transition to a battery efficient state or configuration by indicating end of data transmission in long term evolution
WO2011025284A2 (en) 2009-08-26 2011-03-03 Samsung Electronics Co., Ltd. Method and system to handle a signaling connection release process in a wireless communication system
EP3691347B1 (en) 2009-11-23 2022-02-16 BlackBerry Limited Method and apparatus for state/mode transitioning
CN102763484B (zh) 2009-11-23 2016-06-01 黑莓有限公司 用于状态/模式转换的方法和设备
JP5525621B2 (ja) 2009-11-23 2014-06-18 ブラックベリー リミテッド Ｓｒｉメッセージ伝送に基づいてトリガする状態またはモード遷移
EP2505035A1 (en) * 2009-11-24 2012-10-03 Research In Motion Limited Method and apparatus for state/mode transitioning
US8983532B2 (en) * 2009-12-30 2015-03-17 Blackberry Limited Method and system for a wireless communication device to adopt varied functionalities based on different communication systems by specific protocol messages
KR20140063902A (ko) * 2010-02-10 2014-05-27 블랙베리 리미티드 상태/모드 전이 방법 및 장치
KR101691482B1 (ko) * 2010-10-15 2016-12-30 삼성전자주식회사 적응적 데이터 통신 제어를 수행하는 단말기 및 이의 운용 방법
US9167618B2 (en) 2010-11-16 2015-10-20 At&T Mobility Ii Llc Data bundling and fast dormancy based upon intelligent application learning
CN102469446B (zh) * 2010-11-19 2014-08-20 华为技术有限公司 一种业务处理的方法和装置
CN103535107B (zh) * 2011-03-29 2017-06-23 日本电气株式会社 通信设备、通信系统、通信方法
CN107580376B (zh) 2011-04-01 2021-08-20 交互数字专利控股公司 移动性管理实体及用于提供连接性信息的方法
EP2557889B1 (en) * 2011-08-12 2019-07-17 BlackBerry Limited Simplified ue + enb messaging
US20130039287A1 (en) 2011-08-12 2013-02-14 Venkata Ratnakar Rao Rayavarapu Simplified ue + enb messaging
US9001714B2 (en) 2011-09-06 2015-04-07 Broadcom Corporation Ethernet physical layer device using time division duplex
EP2777358B1 (en) 2011-11-11 2018-01-10 BlackBerry Limited Method and apparatus for user equipment state transition
CN102413516B (zh) * 2011-12-23 2014-03-12 大唐移动通信设备有限公司 一种释放无线信令承载资源的方法及设备
EP2611257B1 (en) * 2011-12-27 2016-08-03 Telefonaktiebolaget LM Ericsson (publ) Method and device for increasing performance in a radio communication system
EP2814289A4 (en) 2012-02-06 2015-12-16 Samsung Electronics Co Ltd METHOD AND APPARATUS FOR ENABLING THE SLEEP MODE OF A TERMINAL
CN103297211B (zh) * 2012-02-29 2016-01-20 华为技术有限公司 单独的上行高速专用物理控制信道的建立方法及装置
US9155121B2 (en) 2012-03-27 2015-10-06 Blackberry Limited Re-establishment of suspended RRC connection at a different eNB
US9295095B2 (en) 2012-03-27 2016-03-22 Blackberry Limited UE preference indicator for suspension
US9247575B2 (en) 2012-03-27 2016-01-26 Blackberry Limited eNB storing RRC configuration information at another network component
GB2501931A (en) * 2012-05-11 2013-11-13 Renesas Mobile Corp Wireless devices and apparatus and computer programs therefor
CN103428762A (zh) * 2012-05-22 2013-12-04 中兴通讯股份有限公司 无线资源管理方法、无线网络控制器及用户设备
US9781767B2 (en) 2012-08-24 2017-10-03 Samsung Electronics Co., Ltd. Method for achieving fast dormancy of user equipment (UE) in Cell—PCH or URA—PCH state in UMTS
WO2014129849A1 (ko) * 2013-02-21 2014-08-28 엘지전자 주식회사 무선 통신 시스템에서 공통 설정 기반 운영 방법 및 이를 지원하는 장치
CN105659661A (zh) * 2013-10-25 2016-06-08 高通股份有限公司 在切换期间选择性地忽略rlc错误
US20150119038A1 (en) * 2013-10-30 2015-04-30 Qualcomm Incorporated Method and apparatus for cell reselection during serving radio network subsystem (srns) relocation
CN104853450A (zh) * 2014-01-27 2015-08-19 马维尔国际有限公司 在处理分组业务交换中使用的方法和设备
CN105592534B (zh) * 2014-11-07 2019-03-29 思科技术公司 用于在网络环境中提供省电模式增强的系统和方法
WO2020050754A1 (en) * 2018-09-03 2020-03-12 Telefonaktiebolaget Lm Ericsson (Publ) Relocation of a user equipment connection from a source radio network controller rnc to a target rnc initiated via a core network
US20210337481A1 (en) * 2020-04-23 2021-10-28 Qualcomm Incorporated Application information aided fast dormancy

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10105093A1 (de) * 2001-02-05 2002-08-08 Nokia Corp Paging-Verfahren und -System für ein Funkzugriffsnetz
US7068636B2 (en) 2002-06-21 2006-06-27 Asustek Computer Inc. Method for determining RLC entity re-establishment during SRNS relocation
AU2006267255B2 (en) * 2005-07-07 2010-03-04 Nokia Technologies Oy Handover method and apparatus between different systems
DE202005021930U1 (de) * 2005-08-01 2011-08-08 Corning Cable Systems Llc Faseroptische Auskoppelkabel und vorverbundene Baugruppen mit Toning-Teilen
US8265034B2 (en) * 2006-05-17 2012-09-11 Research In Motion Limited Method and system for a signaling connection release indication
CN101606420B (zh) * 2007-02-05 2013-05-22 日本电气株式会社 基站间切换方法、无线通信系统、drx控制方法、基站和通信终端
US8693409B2 (en) * 2007-08-10 2014-04-08 Interdigital Patent Holdings, Inc. Method and apparatus for supporting paging over an HS-DSCH in CELL—PCH and URA—PCH states
ATE553628T1 (de) 2007-11-13 2012-04-15 Research In Motion Ltd Verfahren und vorrichtung für status- /modusübergänge
WO2009104086A1 (en) * 2008-02-22 2009-08-27 Nokia Corporation Mobile equipment autonomous quick release detection

Also Published As

Publication number Publication date
BR112012003056B1 (pt) 2021-04-20
US20110038347A1 (en) 2011-02-17
KR101364654B1 (ko) 2014-02-19
ES2639415T3 (es) 2017-10-26
WO2011019832A1 (en) 2011-02-17
CN102474769A (zh) 2012-05-23
TW201119436A (en) 2011-06-01
JP2014140201A (ja) 2014-07-31
US8638711B2 (en) 2014-01-28
CN102474769B (zh) 2015-12-09
CN104469863B (zh) 2018-04-10
JP2013502164A (ja) 2013-01-17
KR20120043084A (ko) 2012-05-03
TWI450607B (zh) 2014-08-21
EP2465288A1 (en) 2012-06-20
HUE035879T2 (en) 2018-05-28
JP5749365B2 (ja) 2015-07-15
BR112012003056A2 (pt) 2016-08-02
CN104469863A (zh) 2015-03-25
JP5583768B2 (ja) 2014-09-03

Similar Documents

Publication Publication Date Title
EP2465288B1 (en) Systems and methods of maintaining core network status during serving radio network subsystem relocation
US9867182B2 (en) Apparatus and method for scheduling cell broadcast messages
US20130229964A1 (en) Method and apparatus for maintaining a power saving state at a network device
US10257813B2 (en) Apparatus and method for deferring cell update messages from user equipment
EP2929731B1 (en) Apparatus and method for enhanced mobile power management
US20130265922A1 (en) Apparatus and method of managing a power saving request
US20150365856A1 (en) Managing radio resource control (rrc) state transitions at a user equipment
EP2732673B1 (en) Apparatus and method for maintaining a circuit-switched voice call in a multi-rab wireless communication system in an area of weak coverage
US20150146628A1 (en) Techniques for handling reconfiguration messages and uplink data indications
EP2987383B1 (en) Enhanced reconfiguration procedure at a mobile terminal to reduce signaling and power consumption overhead
US20150119038A1 (en) Method and apparatus for cell reselection during serving radio network subsystem (srns) relocation

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20120306

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20140806

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 36/10 20090101ALN20160624BHEP

Ipc: H04W 36/00 20090101AFI20160624BHEP

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 36/10 20090101ALN20160712BHEP

Ipc: H04W 36/00 20090101AFI20160712BHEP

INTG Intention to grant announced

Effective date: 20160729

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 36/00 20090101AFI20160720BHEP

Ipc: H04W 36/10 20090101ALN20160720BHEP

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

INTC Intention to grant announced (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 36/10 20090101ALN20161114BHEP

Ipc: H04W 36/00 20090101AFI20161114BHEP

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 36/00 20090101AFI20161206BHEP

Ipc: H04W 36/10 20090101ALN20161206BHEP

INTG Intention to grant announced

Effective date: 20161220

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 900038

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170615

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602010042838

Country of ref document: DE

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 8

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2639415

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20171026

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170908

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170907

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 900038

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170907

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171007

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010042838

Country of ref document: DE

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170831

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170831

26N No opposition filed

Effective date: 20180308

REG Reference to a national code

Ref country code: HU

Ref legal event code: AG4A

Ref document number: E035879

Country of ref document: HU

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20170831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170811

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170607

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20230810

Year of fee payment: 14

Ref country code: FI

Payment date: 20230727

Year of fee payment: 14

Ref country code: ES

Payment date: 20230906

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: HU

Payment date: 20230726

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20240711

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240709

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20240711

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20240710

Year of fee payment: 15