WO2015085565A1 - Procédés et appareil de sélection de cellule dans un système de communication sans fil - Google Patents

Procédés et appareil de sélection de cellule dans un système de communication sans fil Download PDF

Info

Publication number
WO2015085565A1
WO2015085565A1 PCT/CN2013/089339 CN2013089339W WO2015085565A1 WO 2015085565 A1 WO2015085565 A1 WO 2015085565A1 CN 2013089339 W CN2013089339 W CN 2013089339W WO 2015085565 A1 WO2015085565 A1 WO 2015085565A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
identifier
rnc
target cell
rnc identifier
Prior art date
Application number
PCT/CN2013/089339
Other languages
English (en)
Inventor
Xuepan GUAN
Zhang ZHOU
Tynghuei Tim LIOU
Shawn Shiau-He Tsai
Defang Chen
Yong Xie
Original Assignee
Qualcomm Incorporated
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 Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2013/089339 priority Critical patent/WO2015085565A1/fr
Publication of WO2015085565A1 publication Critical patent/WO2015085565A1/fr

Links

Classifications

    • 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
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • 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
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure

Definitions

  • aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to cell selection and/or reselection in a wireless communication system.
  • 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 Universal 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 Downlink Packet Data (HSDPA), which provides higher data transfer speeds and capacity to associated UMTS networks.
  • HSDPA High Speed Downlink Packet Data
  • a method of communication comprises initiating cell selection from a source cell to a target cell during an active communication state with the source cell.
  • the source cell is associated with a first radio network controller (RNC) identifier.
  • the methods and apparatus further comprise determining whether a second RNC identifier associated with the target cell is the same as the first RNC identifier. Additionally, the methods and apparatus comprise selecting to the target cell when the second RNC identifier is the same as the first RNC identifier.
  • RNC radio network controller
  • a computer program product comprising a computer- readable medium including at least one instruction executable to cause a computer to initiate cell selection from a source cell to a target cell during an active communication state with the source cell, wherein the source cell is associated with a first radio network controller (RNC) identifier.
  • the computer-readable medium further including at least one instruction executable to cause a computer to determine whether a second RNC identifier associated with the target cell is the same as the first RNC identifier.
  • the computer-readable medium includes at least one instruction executable to cause a computer to select to the target cell when the second RNC identifier is the same as the first RNC identifier.
  • an apparatus for communication comprises means for initiating cell selection from a source cell to a target cell during an active communication state with the source cell, wherein the source cell is associated with a first radio network controller (RNC) identifier. Additionally, the apparatus comprises means for determining whether a second RNC identifier associated with the target cell is the same as the first RNC identifier. Moreover, the apparatus comprises means for selecting to the target cell when the second R C identifier is the same as the first NC identifier.
  • RNC radio network controller
  • an apparatus for communication comprises a memory storing executable instructions and a processor in communication with the memory, wherein the processor is configured to execute the instructions to initiate cell selection from a source cell to a target cell during an active communication state with the source cell, wherein the source cell is associated with a first radio network controller (RNC) identifier.
  • the processor is further configured to execute the instructions to determine whether a second RNC identifier associated with the target cell is the same as the first RNC identifier.
  • the processor is configured to execute the instructions to select to the target cell when the second RNC identifier is the same as the first RNC identifier.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • Fig. 1 is a schematic diagram of a communication network including an aspect of a user equipment that may select and/or reselect to a target cell within the same radio access network;
  • Fig. 2 is a schematic diagram of an aspect of the communication component of
  • FIG. 3 is a flowchart of an aspect of the reselection features according to the aspects described herein;
  • Fig. 4 is a flowchart of a further aspect of the reselection features according to the aspects described herein;
  • FIG. 5 is a block diagram conceptually illustrating an example of a wireless communication system including an aspect of the user equipment and network entity described herein, e.g., according to Fig. 1;
  • FIG. 6 is a block diagram conceptually illustrating an example of a frame structure in a wireless communication system including an aspect of the user equipment and network entity described herein, e.g., according to Fig. 1;
  • Fig. 7 is a block diagram conceptually illustrating an example of the network entity of Fig. 1, in communication with the user equipment of Fig. 1, in a wireless communication system.
  • the present aspects generally relate to enhancements in cell selection and/or reselection at a user equipment (UE).
  • UE user equipment
  • an lur interface may not exist between a source radio network controller (e.g., RNC) and a target RNC.
  • RNC source radio network controller
  • the target RNC may fail to receive the necessary integrity correction security parameters from the source RNC in order to confirm the security parameters received from the UE included in the cell update message.
  • the target RNC may fail to send a cell update confirmation message to the UE in order to complete selection/reselection and maintain an active connection (e.g., a call).
  • the foregoing resulting failure may be considered as, or otherwise referred to as a radio link failure (RLF) and/or radio link control (RLC) unrecoverable error.
  • RLF radio link failure
  • RLC radio link control
  • the present aspects generally provide methods and apparatus for preventing RLFs and/or RLC unrecoverable errors when a UE attempts cell selection/reselection to a target cell on a target RNC that may be different from the serving RNC.
  • the UE may receive a system information message (e.g., system information block (SIB) 3) including cell identification (e.g., cell ID) from the target cell.
  • SIB system information block
  • the UE may then determine whether the target RNC associated with the target cell, as identified by an RNC identifier obtained by determining the most significant bit (MSB) of the cell ID, is the same from the source RNC identifier.
  • SIB system information block
  • the UE may select/reselect to the target cell (e.g., by sending the cell update message to the target cell). However, if a negative indication is determined, then UE may immediately enter idle mode, drop the active communicate (e.g., call), and perform a cell search and select to another cell based on signal strength. In some aspects, the foregoing SIB information comparison and selection/reselection determination may then be performed with respect to the cell identified as having the best or next best signal strength. In further aspects, if the UE is in an active state (e.g., FACH/PCH), then the UE may perform/conduct the aforementioned SIB information comparison and selection/reselection procedures.
  • an active state e.g., FACH/PCH
  • an implementation of a cell selection/reselection communication scheme may be made to enhance one or more corresponding communication or operational aspects of a UE.
  • the present methods and apparatuses may provide an efficient solution, as compared to current solutions, to prevent terminations in active or ongoing communications (e.g., a call) with a source cell by determining whether a target cell is associated with the same RNC as the source cell, thereby confirming or otherwise implicitly verifying the possession of the security parameters used for integrity protection.
  • a wireless communication system 10 includes at least one UE 12 in communication coverage of one or more network entities.
  • UE 12 may be in communication coverage of at least first network entity 14, second network entity 16 and third network entity 26.
  • first network entity 14, second network entity 16 and third network entity 26 may be alternatively referred to as a first cell, second cell and third cell, respectively.
  • UE 12 may communicate with source RNC 18 associated with source RNC registration area 32 by way of, for instance, first network entity 14 and/or second network entity 16.
  • UE 12 may be in an active or ongoing communication state (e.g., a call) with first network entity 14.
  • UE 12 may communicate with target RNC 28 associated with target
  • source RNC 18 and target RNC 28 may not be configured to communicate with each other.
  • source RNC 18 and target RNC 28 may lack a communication interface (e.g., Iur) between each other.
  • Iur a communication interface between each other.
  • source RNC 18 may not be capable of communicating security parameters used for integrity protection.
  • source RNC 18 may be identified by or associated with source RNC identifier 20.
  • target RNC 28 may be identified by or associated with target
  • RNC identifier 30 An RNC may include or otherwise be associated with an RNC identifier, which may be a unique identifier for the RNC within the network. Further, the RNC identifier of each RNC may be unique in a network. Additionally, the RNC identifier may be used or communicated along the Iun, Iub and/or Iu interfaces for RNC identification purposes.
  • UE 12 may communicate with source RNC 18 via one or more first communication channels 22 corresponding to first network entity 14 and/or second communication channels 24 corresponding to second network entity 16, and utilizing one or more radio access technologies (RATs) (e.g., TD-SCDMA). Additionally, UE 12 may communicate with target RNC 28 via one or more third communication channels 38 and utilizing one or more RATs (e.g., TD-SCDMA). In such aspects, the one or more first communication channels 22, second communication channels 24, and/or one or more third communication channels 38 may enable communication on both the uplink and downlink between UE 12 and first network entity 14, second network entity 16 and/or third network entity 26.
  • RATs radio access technologies
  • UE 12 may be transitioning from, or along the boundary of, source RNC registration area 32 and target RNC registration area 34.
  • UE 12 may engage in one or more selection/reselection procedures with a target network entity (e.g., second network entity 16 and/or third network entity 26).
  • a target network entity e.g., second network entity 16 and/or third network entity 26.
  • UE 12 may include communication component 40, which may be configured to facilitate cell selection/reselection based at least in part on determining whether source RNC identifier 20 is the same as or different from another RNC identifier (e.g., target RNC identifier 30).
  • Communication component 40 may include selection component 44, which may be configured to perform cell selection and/or reselection with a network entity in communication coverage. For example, during an active communication state (e.g., a call) with first network entity 14, communication component 40, via selection component 44, may be configured to initiate or attempt selection/reselection to a target network entity, which may include one or both of second network entity 16 and third network entity 26.
  • a target network entity which may include one or both of second network entity 16 and third network entity 26.
  • second network entity 16 may be associated with source RNC 18
  • third network entity 26 may be otherwise associated with target RNC 28, which may include a different RNC identifier (e.g., target RNC identifier 30) from source RNC 18.
  • communication component 40 may include comparator 48, which may be configured to determine whether a first or source RNC identifier (e.g., source RNC identifier 20) is the same as or different from a second or target RNC identifier (e.g., target RNC identifier 30).
  • comparator 48 may be configured to instruct or otherwise provide a selection/reselection confirmation indication to selection component 44 in order to reselect to a target cell (e.g., second network entity 16) when the second or target RNC identifier is the same as the first or source RNC identifier 20, thereby confirming or otherwise implicitly verifying the possession of the security parameters 36 used for integrity protection. Further aspects of communication component 40 are described herein with respect to Fig. 2.
  • UE 12 may also be referred to by those skilled in the art as a mobile station, 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, 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.
  • first network entity 14, second network entity 16 and/or third network entity 26 may be a macrocell, picocell, femtocell, access point, wireless local access network, relay, Node B, mobile Node B, UE (e.g., communicating in peer-to- peer or ad-hoc mode with UE 12), or substantially any type of component that can communicate with UE 12 to provide wireless network access at the UE 12.
  • an aspect of communication component 40 may include various components and/or subcomponents, which may be configured to perform cell selection and/or reselection with a network entity in communication coverage.
  • a network entity in communication coverage.
  • communication component 40 via selection component 44, may be configured to initiate or attempt selection/reselection to a target network entity, which may include one or both of second network entity 16 (Fig. 1) and third network entity 26 (Fig. 1).
  • target network entity which may include one or both of second network entity 16 (Fig. 1) and third network entity 26 (Fig. 1).
  • communication component 40 may include a first RNC identifier associated with the source cell.
  • selection component 44 may be configured to receive or otherwise obtain and store system information message 52 from a target cell. For instance, selection component 44, via communication component 40 may be configured to receive system information message 52 including a cell identifier from the target cell (e.g., second network entity 16 and/or third network entity 26).
  • a cell identifier 60 may be used so a cell (e.g., target cell) may be identified by an RNC (e.g., source RNC 18). Further, cell identifier 60 may be unique in a RNC, but cells in different RNCs (e.g., within source RNC registration area 32) may have the same cell identity.
  • the cell identifier (CI) may be a unique identity in a network, which may be comprised of the RNC identity (RNCID) and the cell identity (CID).
  • system information message 52 may include or take the form of
  • SIB3 may include information relating to cell selection and/or cell selection/reselection. Specifically, for example, SIB3 may include cell identity information as a 28 bit number which unambiguously identifies a cell within a PLMN (Public Land Mobile Network). In such aspects, SIB3 may be transmitted or otherwise communicated on the Broadcast Control Channel (BCCH) and/or on the Downlink Shared Channel (DL-SCH).
  • BCCH Broadcast Control Channel
  • DL-SCH Downlink Shared Channel
  • selection component 44 may be configured to identify a most significant bit of the cell identifier 60 (e.g., of target cell) in order to determine the second RNC identifier associated with the target cell. For example, selection component 44 may be configured to determine an RNC identifier associated with one or both of second network entity 16 (Fig. 1) and third network entity 26 (Fig. 1). As such, selection component 44 may be configured to determine the second RNC identifier associated with the target cell.
  • Selection component 44 may further include comparator 48, which may be configured to determine whether the second RNC identifier associated with the target cell is the same as the first RNC identifier associated with the source cell (e.g., first network entity 14, Fig. 1). For example, comparator 48 may be configured to compare first RNC identifier (e.g., source RNC identifier 20, Fig. 1) associated with source cell (e.g., first network entity 14, Fig. 1) with the second RNC identifier (e.g., RNC identifier associated with one of second network entity 16 or third network entity 26). As such, selection component 44 may be configured to reselect to the target cell (e.g., second network entity 16, Fig. 1) when the second RNC identifier is the same as the first RNC identifier.
  • comparator 48 may be configured to compare first RNC identifier (e.g., source RNC identifier 20, Fig. 1) associated with source cell (e.g., first network entity 14, Fig. 1) with the second RNC
  • selection component 44 may be configured to generate a low power state trigger 62 upon determining that the second RNC identifier associated with the target cell is not the same as the first RNC identifier associated with the source cell. Accordingly, UE 12 may be configured to enter a low power state (e.g., idle mode) when the second RNC identifier is different from or not the same as the first RNC identifier (e.g., source RNC identifier 20).
  • a low power state e.g., idle mode
  • communication component 40 may be configured to terminate an active call with the source cell upon or as part of entering the low power state. That is, for instance, communication component 40 may be configured to drop a call upon entering idle mode. Further, communication component 40 may include registration component 58, which may be configured to perform a registration procedure to select to a suitable cell after entering the low power state. In some aspects, the registering procedure may include conducting a cell search to obtain a list of one or more cells within a coverage area. Further, registration component 58 may be configured to select to a third cell having a highest signal strength from among the list of one or more cells.
  • communication component 40 may be configured to receive, obtain or otherwise store security parameters 36.
  • security parameters 36 may be utilized for integrity protection during cell selection and/or reselection.
  • the security parameters may be used for ciphering or otherwise determining the integrity protection at the target cell (e.g., second network entity 16 and/or third network entity 26.
  • Figs. 3 and 4 the methods are shown and described as a series of acts for purposes of simplicity of explanation. However, it is to be understood and appreciated that the methods (and further methods related thereto) are not limited by the order of acts, as some acts may, in accordance with one or more aspects, occur in different orders and/or concurrently with other acts from that shown and described herein. For example, it is to be appreciated that the methods may alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a method in accordance with one or more features described herein.
  • a UE such as UE 12 (Fig. 1) may perform one aspect of a method 80 for performing cell selection/reselection to a cell having the same RNC identifier.
  • method 80 provides a process tailored to avoid, or at least to reduce, service interruption experienced by UE 12 (Fig. 1) by comparing a first RNC identifier (e.g., source RNC identifier 20, Fig. 1) with a second RNC identifier (e.g., target RNC identifier 30, Fig. 1).
  • a first RNC identifier e.g., source RNC identifier 20, Fig. 1
  • a second RNC identifier e.g., target RNC identifier 30, Fig.
  • method 80 may include initiating cell selection/reselection from a source cell to a target cell during an active communication state.
  • communication component 40 may execute selection component 44 (Fig. 1) to initiate cell selection from the source cell (e.g., first network entity 14, Fig. 1) to a target cell (e.g., second network entity 16, Fig. 1) during an active communication state (e.g., call) with the source cell.
  • the source cell may be associated with a first RNC identifier (e.g., source RNC identifier 20, Fig. 1).
  • method 80 may include determining whether a second RNC identifier associated with the target cell is the same as a first RNC identifier. For instance, as described herein, selection component 44 (Figs. 1 and 2) may execute comparator 48 (Figs. 1 and 2) to determine whether the second RNC identifier (e.g., target RNC identifier 30, Fig. 1) associated with the target cell is the same as a first RNC identifier (e.g., source RNC identifier 20, Fig. 1).
  • the second RNC identifier e.g., target RNC identifier 30, Fig. 1
  • method 80 may include selecting/reselecting to the target cell when the second RNC identifier is the same as the first RNC identifier.
  • communication component 40 may execute selection component 44 (Fig. 1) to select/reselect to the target cell (e.g., second network entity 16) when the second RNC identifier (e.g., (e.g., source RNC identifier 20, Fig. 1) is the same as the first RNC identifier (e.g., source RNC identifier 20, Fig. 1).
  • a UE such as UE 12 (Fig. 1) may perform one aspect of a method 90 for performing cell selection/reselection to a cell having the same RNC identifier.
  • method 90 provides a process tailored to avoid, or at least to reduce, service interruption experienced by UE 12 (Fig. 1) by comparing a first RNC identifier (e.g., source RNC identifier 20, Fig. 1) with a second RNC identifier (e.g., target RNC identifier 30, Fig. 1).
  • a first RNC identifier e.g., source RNC identifier 20, Fig. 1
  • a second RNC identifier e.g., target RNC identifier 30, Fig.
  • method 90 may include initiating cell selection/reselection from a source cell to a target cell during an active communication state.
  • communication component 40 may execute selection component 44 (Fig. 1) to initiate cell selection/reselection from the source cell (e.g., first network entity 14, Fig. 1) to a target cell (e.g., second network entity 16, Fig. 1) during an active communication state (e.g., call) with the source cell (e.g., first network entity 14, Fig. 1).
  • the source cell may be associated with a first RNC identifier (e.g., source RNC identifier 20, Fig. 1).
  • method 90 may include receiving a system information message.
  • communication component 40 (Figs. 1 and 2) may execute selection component 44 to receive or otherwise obtain a system information message including a target cell identifier from a target cell.
  • method 90 may, at block 96, determine the most significant bit of the target cell identifier to obtain the a second RNC identifier.
  • communication component 40 (Figs. 1 and 2) may execute selection component 44 to obtain the second RNC identifier by determining the most significant bit of the target cell identifier (e.g., cell identifier 60, Fig. 2).
  • method 90 may include determining whether the second RNC identifier is the same as the first RNC identifier. For instance, as described herein, selection component 44 (Figs. 1 and 2) may execute comparator 48 (Figs. 1 and 2) to determine whether the second RNC identifier (e.g., target RNC identifier 30, Fig. 1) associated with the target cell is the same as a first RNC identifier (e.g., source RNC identifier 20, Fig. 1).
  • selection component 44 may execute comparator 48 (Figs. 1 and 2) to determine whether the second RNC identifier (e.g., target RNC identifier 30, Fig. 1) associated with the target cell is the same as a first RNC identifier (e.g., source RNC identifier 20, Fig. 1).
  • method 90 may proceed to block 100 based upon a determination at block 98 in the affirmative. That is, at block 100, method 90 may include selecting/reselecting to the target cell when the second RNC identifier is the same as the first RNC identifier.
  • communication component 40 (Fig. 1) may execute selection component 44 (Fig. 1) to select/reselect to the target cell (e.g., second network entity 16) when the second RNC identifier (e.g., (e.g., source RNC identifier 20, Fig. 1) is the same as the first RNC identifier (e.g., source RNC identifier 20, Fig. 1).
  • method 90 may proceed to block 102, which may include terminating a call or otherwise an active connection state of UE 12. In other words, method 90 may proceed to block 102 and terminate a call when the first RNC identifier is not the same as the second RNC identifier.
  • UE 12 (Fig. 1) may execute communication component 40 (Figs. 1 and 2) to terminate a call.
  • method 90 may include entering into an idle mode.
  • communication component 40 (Figs. 1 and 2) may execute low power state trigger 62 (Fig. 2) to enter into an idle mode.
  • method 90 may include performing a registration procedure.
  • communication component 40 (Figs. 1 and 2) may execute registration component 58 (Fig. 2) to perform a registration procedure.
  • the registering procedure may include conducting a cell search to obtain a list of one or more cells within a coverage area.
  • registration component 58 may be configured to select to a third cell having a highest signal strength from among the list of one or more cells.
  • a block diagram is shown illustrating an example of a telecommunications system 200 in which UE 12 including communication component 40 (Fig. 1), may operate, such as in the form of or as a part of UEs 210 and Node Bs 208.
  • UE 12 including communication component 40 (Fig. 1)
  • Fig. 1 UE 12 including communication component 40
  • Fig. 5 a block diagram is shown illustrating an example of a telecommunications system 200 in which UE 12 including communication component 40 (Fig. 1), may operate, such as in the form of or as a part of UEs 210 and Node Bs 208.
  • the various concepts presented throughout this disclosure may be implemented across a broad variety of telecommunication systems, network architectures, and communication standards.
  • the aspects of the present disclosure illustrated in Fig. 5 are presented with reference to a UMTS system employing a TD-SCDMA standard.
  • the UMTS system includes a (radio access network) RAN 202 (e.g., UTRAN) that provides
  • the RAN 202 may be divided into a number of Radio Network Subsystems
  • RNSs such as an RNS 207
  • RNC Radio Network Controller
  • RNC 206 is an apparatus responsible for, among other things, assigning, reconfiguring and releasing radio resources within the RNS 207.
  • the RNC 206 may be interconnected to other RNCs (not shown) in the RAN 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 RNS 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
  • the Node Bs 208 provide wireless access points to a core network 204 for any number of mobile apparatuses.
  • IP Initiation protocol
  • laptop a notebook
  • netbook a smartbook
  • PDA personal digital assistant
  • satellite radio a global positioning system (GPS) device
  • multimedia device e.g., a video device
  • digital audio player e.g., MP3 player
  • camera e.g., a game console, or any other similar functioning device.
  • 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.
  • UE user equipment
  • MS mobile station
  • AT access terminal
  • three UEs 210 are shown in communication with the Node Bs 208, each of which may include communication component 40 of UE 12 (Fig. 1).
  • the downlink (DL), also called the forward link refers to the communication link from a Node B to a UE
  • the uplink (UL) also called the reverse link, refers to the communication link from a UE
  • the core network 204 includes a GSM core network.
  • GSM Global System for Mobile communications
  • the core network 204 supports circuit-switched services with a mobile switching center (MSC) 212 and a gateway MSC (GMSC) 214.
  • MSC mobile switching center
  • GMSC gateway MSC
  • 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) (not shown) 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) (not shown) 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 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
  • DS-CDMA Spread spectrum Multiple Access
  • the TD-SCDMA standard is based on such direct sequence spread spectrum technology and additionally calls for a time division duplexing (TDD), rather than a frequency division duplexing (FDD) as used in many FDD mode UMTS/W-CDMA systems.
  • TDD uses the same carrier frequency for both the uplink (UL) and downlink (DL) between a Node B 208 and a UE 210, but divides uplink and downlink transmissions into different time slots in the carrier.
  • Fig. 6 shows a frame structure 250 for a TD-SCDMA carrier, which may be used in communications between UE 12 (Fig. 1) including communication component 40 and at least one network entity discussed herein.
  • the TD-SCDMA carrier as illustrated, has a frame 252 that may be 10 ms in length.
  • the frame 252 may have two 5 ms subframes 254, and each of the subframes 254 includes seven time slots, TSO through TS6.
  • the first time slot, TSO may be allocated for inter/intra frequency measurements and/or downlink communication, while the second time slot, TS1, may be allocated for uplink communication.
  • the remaining time slots, TS2 through TS6, may be used for either uplink or downlink, which allows for greater flexibility during times of higher data transmission times in either the uplink or downlink directions.
  • a downlink pilot time slot (DwPTS) 256, a guard period (GP) 258, and an uplink pilot time slot (UpPTS) 260 (also known as the uplink pilot channel (UpPCH)) are located between TSO and TS1.
  • Each time slot, TS0-TS6, may allow data transmission multiplexed on a maximum of, for instance, 16 code channels.
  • Data transmission on a code channel includes two data portions 262 separated by a midamble 264 and followed by a guard period (GP) 268.
  • the midamble 264 may be used for features, such as channel estimation, while the GP 268 may be used to avoid inter-burst interference.
  • Fig. 7 is a block diagram of a Node B 310 in communication with a UE 350 in a RAN 300, where RAN 300 may be the same as or similar to RAN 202 in Fig. 5, the Node B 310 may be the same as or similar to Node B 208 in Fig. 5, and the UE 350 may be the same as or similar to UE 210 in Fig. 5 or the UE 12 in Fig. 1 including communication component 40.
  • a transmit processor 320 may receive data from a data source 312 and control signals from a controller/processor 340. The transmit processor 320 provides various signal processing functions for the data and control signals, as well as reference signals (e.g., pilot signals).
  • the transmit processor 320 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.
  • CRC cyclic redundancy check
  • Channel estimates from a channel processor 344 may be used by a controller/processor 340 to determine the coding, modulation, spreading, and/or scrambling schemes for the transmit processor 320. These channel estimates may be derived from a reference signal transmitted by the UE 350 or from feedback contained in the midamble 214 (Fig. 7) from the UE 350.
  • the symbols generated by the transmit processor 320 are provided to a transmit frame processor 330 to create a frame structure.
  • the transmit frame processor 330 creates this frame structure by multiplexing the symbols with a midamble 214 (Fig. 7) from the controller/processor 340, resulting in a series of frames.
  • a transmitter 332 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 334.
  • the smart antennas 334 may be implemented with beam steering bidirectional adaptive antenna arrays or other similar beam technologies.
  • a receiver 354 receives the downlink transmission through an antenna 352 and processes the transmission to recover the information modulated onto the carrier.
  • the information recovered by the receiver 354 is provided to a receive frame processor 360, which parses each frame, and provides the midamble 214 (Fig. 8) to a channel processor 394 and the data, control, and reference signals to a receive processor 370.
  • the receive processor 370 then performs the inverse of the processing performed by the transmit processor 320 in the Node B 310. More specifically, the receive processor 370 descrambles and despreads the symbols, and then determines the most likely signal constellation points transmitted by the Node B 310 based on the modulation scheme.
  • These soft decisions may be based on channel estimates computed by the channel processor 394.
  • the soft decisions are then decoded and deinterleaved to recover the data, control, and reference signals.
  • the C C 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 372, which represents applications running in the UE 350 and/or various user interfaces (e.g., display).
  • Control signals carried by successfully decoded frames will be provided to a controller/processor 390.
  • the controller/processor 390 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 380 receives data from a data source 378 and control signals from the controller/processor 390 and 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 380 will be provided to a transmit frame processor 382 to create a frame structure.
  • the transmit frame processor 382 creates this frame structure by multiplexing the symbols with a midamble 214 (FIG. 2) from the controller/processor 390, resulting in a series of frames.
  • the frames are then provided to a transmitter 356, 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 352.
  • the uplink transmission is processed at the Node B 310 in a manner similar to that described in connection with the receiver function at the UE 350.
  • a receiver 335 receives the uplink transmission through the antenna 334 and processes the transmission to recover the information modulated onto the carrier.
  • the information recovered by the receiver 335 is provided to a receive frame processor 336, which parses each frame, and provides the midamble 214 (Fig. 7) to the channel processor 344 and the data, control, and reference signals to a receive processor 338.
  • the receive processor 338 performs the inverse of the processing performed by the transmit processor 380 in the UE 350.
  • the data and control signals carried by the successfully decoded frames may then be provided to a data sink 339 and the controller/processor, respectively. If some of the frames were unsuccessfully decoded by the receive processor, the controller/processor 340 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.
  • ACK acknowledgement
  • NACK
  • the controller/processors 340 and 390 may be used to direct the operation at the Node B 310 and the UE 350, respectively.
  • the controller/processors 340 and 390 may provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the computer readable media of memories 342 and 392 may store data and software for the Node B 310 and the UE 350, respectively.
  • a scheduler/processor 346 at the Node B 310 may be used to allocate resources to the UEs and schedule downlink and/or uplink transmissions for the UEs.
  • some or all of the functionality and/or features of the communication component 40 may be performed by at least the controller/processor 390 and the memory 392.
  • 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 electronic hardware, computer software, 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.
  • 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, memory such as a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., compact disc (CD), digital versatile disc (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, or a removable disk.
  • memory is shown separate from the processors in the various aspects presented throughout this disclosure, the memory may be internal to the processors (e.g., cache or register).
  • 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)

Abstract

L'invention concerne des procédés et un appareil de communication, qui consistent à initier une sélection de cellule d'une cellule source à une cellule cible durant un état de communication active avec la cellule source. Selon certains aspects, la cellule source est associée à un premier identifiant de contrôleur de réseau de radiocommunication (RNC). Les procédés et l'appareil consistent en outre à déterminer si un second identifiant de RNC associé à la cellule cible est ou non le même que le premier identifiant RNC. En outre, les procédés et l'appareil consistent à effectuer une sélection au niveau de la cellule cible lorsque le second identifiant RNC est le même que le premier identifiant RNC.
PCT/CN2013/089339 2013-12-13 2013-12-13 Procédés et appareil de sélection de cellule dans un système de communication sans fil WO2015085565A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/089339 WO2015085565A1 (fr) 2013-12-13 2013-12-13 Procédés et appareil de sélection de cellule dans un système de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/089339 WO2015085565A1 (fr) 2013-12-13 2013-12-13 Procédés et appareil de sélection de cellule dans un système de communication sans fil

Publications (1)

Publication Number Publication Date
WO2015085565A1 true WO2015085565A1 (fr) 2015-06-18

Family

ID=53370515

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/089339 WO2015085565A1 (fr) 2013-12-13 2013-12-13 Procédés et appareil de sélection de cellule dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2015085565A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9695212B2 (en) 2012-12-13 2017-07-04 Aduro Biotech, Inc. Compositions comprising cyclic purine dinucleotides having defined stereochemistries and methods for their preparation and use

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101616481A (zh) * 2008-06-23 2009-12-30 三星电子株式会社 支持用户设备进行位置更新的方法
CN101790216A (zh) * 2009-01-22 2010-07-28 鼎桥通信技术有限公司 一种切换方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101616481A (zh) * 2008-06-23 2009-12-30 三星电子株式会社 支持用户设备进行位置更新的方法
CN101790216A (zh) * 2009-01-22 2010-07-28 鼎桥通信技术有限公司 一种切换方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9695212B2 (en) 2012-12-13 2017-07-04 Aduro Biotech, Inc. Compositions comprising cyclic purine dinucleotides having defined stereochemistries and methods for their preparation and use

Similar Documents

Publication Publication Date Title
US8594670B2 (en) Measurement and handover of dual USIM mobile terminal
US20160366619A1 (en) Reduced handover failure for single radio voice call continuity
US20160338009A1 (en) Redirection failure handling in a wireless network
US9456399B2 (en) Circuit switched fall back redirection across mobile switching center pools
US20150289189A1 (en) Cell reselection
US20120176891A1 (en) Method and Apparatus for Recovery of Link Failure During Handover in TD-SCDMA Systems
US20150350973A1 (en) Priority based cell reselection
US20110243099A1 (en) Method of Service Redirection Procedures in TD-SCDMA and GSM Hybrid Mobile Terminals
US20160050599A1 (en) Power scan for establishing circuit switched fallback (csfb) call
US20150119036A1 (en) Cellular handover execution after first non-blind handover failure
US20150094069A1 (en) Enhanced inter-radio access technology handover procedures
US20160073314A1 (en) Redirection history based circuit switched fall back
US9036552B2 (en) Intelligent inter radio access technology measurement reporting
US8958281B2 (en) Early termination of a base station identity code procedure in TD-SDCMA
US20130176866A1 (en) Call recovery in td-scdma handover failure
US20160057671A1 (en) Fast return after circuit switched fall back (csfb) call release
US9326204B2 (en) Inter-radio access technology (IRAT) handover
US20110243093A1 (en) Method and Apparatus for Pre-Uplink Synchronization in TD-SCDMA Handover
US20160119836A1 (en) Fast return after circuit switched fallback failure
US20150201448A1 (en) Uplink pilot channel positioning for circuit switched fallback
US20160105830A1 (en) Reduced network access failure during radio access technology (rat) switching
US20150085754A1 (en) Methods and apparatus for enhanced frequency measurements
US20150350959A1 (en) Reduced latency during random access procedure
US20150079987A1 (en) Tone detection scheduling
US20140171070A1 (en) Expanded neighbor list for cell reselection

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13899102

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13899102

Country of ref document: EP

Kind code of ref document: A1