WO2015169092A1 - Validation d'un message de reconfiguration - Google Patents

Validation d'un message de reconfiguration Download PDF

Info

Publication number
WO2015169092A1
WO2015169092A1 PCT/CN2014/094615 CN2014094615W WO2015169092A1 WO 2015169092 A1 WO2015169092 A1 WO 2015169092A1 CN 2014094615 W CN2014094615 W CN 2014094615W WO 2015169092 A1 WO2015169092 A1 WO 2015169092A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
reconfiguration
cell update
valid
user equipment
Prior art date
Application number
PCT/CN2014/094615
Other languages
English (en)
Inventor
Huan Xu
Yong Xie
Xuepan GUAN
Tim Tynghuei Liou
Shiau-He Tsai
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
Publication of WO2015169092A1 publication Critical patent/WO2015169092A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/06—Reselecting a communication resource in the serving access point
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • UE 12 of the present aspects includes a radio bearer (RB) reconfiguration validation component 30 configured to execute one or more validation algorithms 32 to determine whether or not a reconfiguration message 14 received from a network device (NW) 16 is valid or not valid.
  • RB radio bearer
  • reconfiguration validation component 30 determines if reconfiguration message 14 is a leftover or outdated message, or a new message.
  • UE 12 and/or reconfiguration validation component 30 executes one or more validation algorithms 32 to determine whether one or more of a UE reconfiguration triggering condition 34 and a NW reconfiguration triggering condition 36 has occurred since receiving cell update confirm message 28.
  • reconfiguration validation component 30 may further include a UE validation component 33 configured to determine whether UE reconfiguration triggering condition 34 has occurred and NW validation component 35 configured to determine whether NW reconfiguration triggering condition 36 has occurred.
  • UE 12 and/or reconfiguration validation component 30 and/or UE validation component 33 may execute ones or portions of one or more validation algorithms 32 to determine whether an uplink (UL) message, such as but not limited to a measurement report message, has been generated after the receiving of cell update confirm message 28. This condition is used to preclude reconfiguration message 14 from being a valid one, e.g., due to UE 12 reporting measured radio conditions.
  • reconfiguration validation component 30 and/or UE validation component 33 may access a memory on UE 12 that includes a message log to identify an entry or code that indicates whether a measurement report message was transmitted.
  • the guard time may be on the order of 5 seconds or less, while the NW reconfiguration triggering event, e.g., the load balancing procedure, may be expected to occur at some time later than the guard time, and in some cases substantially later than the guard time.
  • NW reconfiguration triggering event e.g., the load balancing procedure
  • UE 12 and/or reconfiguration validation component 30 may determine that reconfiguration message 14 is valid when UE 12 has generated any uplink message (that could have triggered reconfiguration message 14) after the receipt of cell update confirm message 28 or when reconfiguration message 14 is received after the guard time relative to receiving cell update confirm message 28.
  • UE 12 and/or UE radio bearer (RB) /channel manager component and/or UE mobility manager component 20 may be configured to disregard reconfiguration message 14, or, optionally, to further execute a feedback component 37 configured to reply with a failure message 40 in response to reconfiguration message 14, when reconfiguration validation component 30 determines that reconfiguration message 14 is not valid.
  • RB radio bearer
  • UE 12 may include a communication component 38 that is configured to carry communications between the components of UE 12, and also to provide an interface to exchange communications with external devices such as NW 16.
  • communication component 38 may include a bus that connects components internal to UE 12.
  • communication component 38 may include one or more transceivers, transmitters or receivers, and corresponding transmit chain and receive chain hardware and software elements for transmitting or receiving messages over-the-air, such as cell update message 26, cell update confirm message 28, reconfiguration message 14, and failure message 40, and maintaining a radio link, such as RB/channel 18.
  • UE 12 and/or cell update component 24 of UE RB/channel manager component 20 may cause UE 12 to send a cell update message 26 to NW 16 to resume the previous RB/channel 18 or to request a new configuration for RB/channel 18.
  • cell update message 26 may be sent include a radio link control (RLC) unrecoverable error message, etc.
  • RLC radio link control
  • method 200 includes receiving a cell update confirm message in response to the cell update message.
  • UE 12 and/or UE RB/channel manager component 20 and/or cell update component 24 and/or communication component 38 may include a processor executing a specially programmed computer readable medium, or a processor executing a specially programmed processor module, or some combination thereof, to receive cell update confirm message 28, as discussed above.
  • NW 16 may send a cell update confirm message 28 to UE 12.
  • cell update confirm message 28 may include new configurations for RB/channel 18, or reconfigure RB/channel 18. That is, UE 12 and/or communication component 38 may be configured to receive cell update confirm message 28 from NW 16.
  • method 200 includes receiving, at the user equipment, a reconfiguration message after the receiving of the cell update confirm message.
  • UE 12 and/or UE RB/channel manager component 20 and/or reconfiguration validation component 30 and/or communication component 38 may include a processor executing a specially programmed computer readable medium, or a processor executing a specially programmed processor module, or some combination thereof, to receive reconfiguration message 14 after the receiving of cell update confirm message 28, as discussed above. That is, in some cases, NW 16 and/or NW RB/channel manager component 20 may have already initiated a new reconfiguration procedure before cell update message 26 is received at NW 16.
  • method 200 includes determining whether the reconfiguration message is valid or not valid based on at least one of a user equipment reconfiguration triggering condition and a network reconfiguration triggering condition occurring subsequent to the receiving of the cell update confirm message.
  • UE 12 and/or UE RB/channel manager component 20 and/or reconfiguration validation component 30 may include a processor executing a specially programmed computer readable medium, or a processor executing a specially programmed processor module, or some combination thereof, to determining whether the reconfiguration message is valid or not valid based on at least one of a user equipment reconfiguration triggering condition and a network reconfiguration triggering condition occurring subsequent to the receiving of the cell update confirm message, as discussed above.
  • reconfiguration validation component 30 determines if reconfiguration message 14 is a leftover or outdated message, or a new message.
  • UE 12 and/or reconfiguration validation component 30 executes one or more validation algorithms 32 to determine whether one or more of a UE reconfiguration triggering condition 34 and a NW reconfiguration triggering condition 36 has occurred since receiving cell update confirm message 28.
  • method 200 may include determining if the user equipment reconfiguration triggering condition has occurred after the receiving of the cell update confirm message. That is, UE validation component 33 may be configured to determine whether UE reconfiguration triggering condition 34 has occurred.
  • UE reconfiguration triggering condition 34 may include, but is not limited to, a condition caused by UE 12 that would have triggered NW 16 to send reconfiguration message 14, such as the sending of a measurement report message.
  • method 200 may include determining whether the user equipment sent an uplink message after the receiving of the cell update confirm message. Further to the example above, reconfiguration validation component 30 and/or UE validation component 33 may execute validation algorithms 32 to determine whether an uplink (UL) message, such as but not limited to a measurement report message, has been generated after the receiving of cell update confirm message 28. This condition is used to preclude reconfiguration message 14 from being a valid one, e.g., due to UE 12 reporting measured radio conditions.
  • UL uplink
  • method 200 may include determining whether the reconfiguration message is received within a guard time relative to the receiving of the cell update confirm message.
  • reconfiguration validation component 30 and/or NW validation component 35 may execute validation algorithms 32 to determine whether reconfiguration message 14 is received within a guard time relative to receiving of cell update confirm message 28. For instance, upon receiving cell update confirm message 28, reconfiguration validation component 30 and/or NW validation component 35 may execute validation algorithms 32 to start a timer and track a value of time lapsed up to the time of receiving reconfiguration message 14, and then compare the lapsed time to guard time 36. This condition is to protect NW 16, which may start a load balancing procedure after the cell update, but the load balancing procedure is supposed to be a “slow” procedure, e.g., one that occurs significantly after the cell update procedure.
  • method 200 includes reconfiguring the user equipment based on the reconfiguration message, or ignoring the reconfiguration message, depending on whether or not the reconfiguration message is determined to be valid or not valid.
  • UE 12 and/or UE RB/channel manager component 20 and/or reconfiguration validation component 30 may include a processor executing a specially programmed computer readable medium, or a processor executing a specially programmed processor module, or some combination thereof, to reconfigure user equipment 12 based on reconfiguration message 14, or to ignore reconfiguration message 14, depending on whether or not reconfiguration message 14 is determined to be valid or not valid.
  • UE 12 reconfigures radio bearer/channel 18 to maintain a radio link with network device 16.
  • the method may further include disregarding reconfiguration message 14.
  • UE 12 may be reconfigured to establish or modify radio bearers, perform handover operations, setup radio frequency measurements, etc., in accordance with one or more instructions or parameters included in reconfiguration message 14.
  • reconfiguration message 14 is invalid, for example, the instructions or parameters included in reconfiguration message 14 may not be performed or adopted by UE 12.
  • method 200 may include replying with a failure message in response to the reconfiguration message, when the determining determines that the reconfiguration message is not valid. That is, for example, in addition to disregarding reconfiguration message 14, in an aspect, UE 12 and/or feedback component 37 may be configured to detect, or may be notified reconfiguration validation component 30, that reconfiguration message 14 is invalid. Upon the detection or notification of the invalidity of reconfiguration message 14, UE 12 and/or feedback component 37 may then be configured to reply with a failure message 40 that may be transmitted by communication component 38 to NW 16.
  • the radio RB reconfiguration message arrives at the UE within a short guard time after UE receives the Cell Update Confirm message --this condition is to protect the NW, which may start a load balancing procedure after the cell update procedure, but in this case the load balancing procedure is expected to be a “slow” procedure, e.g., one that occurs significantly after the cell update procedure.
  • the present aspects configure the UE to check the RRC layer to determine whether there are any UL messages (e.g. measurement report/service request) sent after the initiation of the Cell Update procedure. If there are no such UL messages, and the radio bearer reconfiguration message arrives at the UE within a guard time (such as, but not limited to, about 3-5 seconds) after getting the Cell Update Confirm message, then the UE can determine this RB reconfiguration message is a leftover or outdated one. As such, the UE can either disregard the message or reply back to the NW with a failure message, depending on the NW capability for exception handling.
  • UL messages e.g. measurement report/service request
  • a block diagram is shown illustrating an example of additional components of telecommunications system 10, including one or more UEs 12 having UE RB/channel manager component 20 and one or more NWs 16 (which may include one or both of a Node B 308 and an RNC 306) having NW RB/channel manager component 22.
  • NWs 16 which may include one or both of a Node B 308 and an RNC 306
  • NW RB/channel manager component 22 may include one or both of a Node B 308 and an RNC 306 having NW RB/channel manager component 22.
  • 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. 3 are presented with reference to a UMTS system employing a TD-SCDMA standard.
  • the telecommunications system 10 may be a UMTS system that includes a (radio access network) RAN 302 (e.g., UTRAN) that provides various wireless services including telephony, video, data, messaging, broadcasts, and/or other services.
  • the RAN 302 may be divided into a number of Radio Network Subsystems (RNSs) such as an RNS 307, each controlled by a Radio Network Controller (RNC) such as an RNC 306.
  • RNSs Radio Network Subsystems
  • RNC Radio Network Controller
  • the RAN 302 may include any number of RNCs and RNSs in addition to the RNC 306 and RNS 307.
  • the geographic region covered by the RNS 307 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.
  • BSS basic service set
  • ESS extended service set
  • AP access point
  • two Node Bs 308 are shown; however, the RNS 307 may include any number of wireless Node Bs.
  • the Node Bs 308 provide wireless access points to a core network 304 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 core network 304 includes a GSM core network.
  • GSM Global System for Mobile communications
  • the core network 304 supports circuit-switched services with a mobile switching center (MSC) 312 and a gateway MSC (GMSC) 314.
  • MSC mobile switching center
  • GMSC gateway MSC
  • RNCs such as the RNC 306
  • the MSC 312 is an apparatus that controls call setup, call routing, and UE mobility functions.
  • the MSC 312 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 312.
  • VLR visitor location register
  • the GMSC 314 provides a gateway through the MSC 312 for the UE to access a circuit-switched network 316.
  • the GMSC 314 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 304 also supports packet-data services with a serving GPRS support node (SGSN) 318 and a gateway GPRS support node (GGSN) 320.
  • 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 320 provides a connection for the RAN 302 to a packet-based network 322.
  • the packet-based network 322 may be the Internet, a private data network, or some other suitable packet-based network.
  • the primary function of the GGSN 320 is to provide the UEs 310 with packet-based network connectivity. Data packets are transferred between the GGSN 320 and the UEs 310 through the SGSN 318, which performs primarily the same functions in the packet-based domain as the MSC 312 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 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 308 and a UE 310, but divides uplink and downlink transmissions into different time slots in the carrier.
  • a frame structure 400 for a TD-SCDMA which may be used by UE 12 and NW 16 of Fig. 1, has a frame 402 that is 10 ms in length.
  • the frame 402 has two 5 ms subframes 404, and each of the subframes 404 includes seven time slots, TS0 through TS6.
  • the first time slot, TS0 is usually allocated for downlink communication, while the second time slot, TS1, is usually 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) 406, a guard period (GP) 408, and an uplink pilot time slot (UpPTS) 410 are located between TS0 and TS1.
  • Each time slot, TS0-TS6, may allow data transmission multiplexed on a maximum of 16 code channels.
  • Data transmission on a code channel includes two data portions 412 separated by a midamble 414 and followed by a guard period (GP) 416.
  • the midamble 414 may be used for features, such as channel estimation, while the GP 416 may be used to avoid inter-burst interference.
  • NW 16 (which may include one or both of a Node B and an RNC) is in communication with a UE 12 in a RAN 10.
  • UE 12 may implement UE RB/channel manager component 20 in controller/processor 590 and/or memory 592, and communication component 38 in the remaining illustrated components including memory 542, controller/processor 540, transmit processor 520, receive processor 538, etc.
  • a transmit processor 520 may receive data from a data source 512 and control signals from a controller/processor 540.
  • the transmit processor 520 provides various signal processing functions for the data and control signals, as well as reference signals (e.g., pilot signals) .
  • the transmit processor 520 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 544 may be used by a controller/processor 540 to determine the coding, modulation, spreading, and/or scrambling schemes for the transmit processor 520. These channel estimates may be derived from a reference signal transmitted by the UE 12 or from feedback contained in the midamble 414 (Fig. 4) from the UE 12.
  • the symbols generated by the transmit processor 520 are provided to a transmit frame processor 530 to create a frame structure.
  • the transmit frame processor 530 creates this frame structure by multiplexing the symbols with a midamble 414 (Fig. 4) from the controller/processor 540, resulting in a series of frames.
  • the frames are then provided to a transmitter 532, 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 534.
  • the smart antennas 534 may be implemented with beam steering bidirectional adaptive antenna arrays or other similar beam technologies.
  • a receiver 554 receives the downlink transmission through an antenna 552 and processes the transmission to recover the information modulated onto the carrier.
  • the information recovered by the receiver 554 is provided to a receive frame processor 560, which parses each frame, and provides the midamble 414 (Fig. 4) to a channel processor 594 and the data, control, and reference signals to a receive processor 570.
  • the receive processor 570 then performs the inverse of the processing performed by the transmit processor 520 in NW 16. More specifically, the receive processor 570 descrambles and despreads the symbols, and then determines the most likely signal constellation points transmitted by NW 16 based on the modulation scheme. These soft decisions may be based on channel estimates computed by the channel processor 594.
  • 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 572, which represents applications running in the UE 12 and/or various user interfaces (e.g., display) .
  • Control signals carried by successfully decoded frames will be provided to a controller/processor 590.
  • the controller/processor 590 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 580 receives data from a data source 578 and control signals from the controller/processor 590 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.
  • CRC codes CRC codes
  • coding and interleaving to facilitate FEC
  • mapping to signal constellations mapping to signal constellations
  • spreading with OVSFs e.g., and scrambling to produce a series of symbols.
  • Channel estimates, derived by the channel processor 594 from a reference signal transmitted by the NW 16 or from feedback contained in the midamble transmitted by the NW 16 may be used to select the appropriate coding, modulation, spreading, and/or scrambling schemes.
  • the symbols produced by the transmit processor 580 will be provided to a transmit frame processor 582 to create a frame structure.
  • the transmit frame processor 582 creates this frame structure by multiplexing the symbols with a midamble 414 (Fig. 4) from the controller/processor 590, resulting in a series of frames.
  • the frames are then provided to a transmitter 556, 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 552.
  • the uplink transmission is processed at the NW 16 in a manner similar to that described in connection with the receiver function at the UE 12.
  • a receiver 535 receives the uplink transmission through the antenna 534 and processes the transmission to recover the information modulated onto the carrier.
  • the information recovered by the receiver 535 is provided to a receive frame processor 536, which parses each frame, and provides the midamble 414 (Fig. 4) to the channel processor 544 and the data, control, and reference signals to a receive processor 538.
  • the receive processor 538 performs the inverse of the processing performed by the transmit processor 580 in the UE 12.
  • the data and control signals carried by the successfully decoded frames may then be provided to a data sink 539 and the controller/processor, respectively. If some of the frames were unsuccessfully decoded by the receive processor, the controller/processor 540 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.
  • ACK acknowledgement
  • NACK negative acknowledgement
  • the controller/processors 540 and 590 may be used to direct the operation at the NW 16 and the UE 12, respectively.
  • the controller/processors 540 and 590 may provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the computer readable media of memories 542 and 592 may store data and software for the NW 16 and the UE 12, respectively.
  • a scheduler/processor 546 at the NW 16 may be used to allocate resources to the UEs and schedule downlink and/or uplink transmissions for the UEs.
  • TD-SCDMA Time Division Multiple 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
  • EV-DO 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
  • a state machine gated logic, discrete hardware circuits, and other suitable processing components configured to perform the various functions described throughout this disclosure.
  • 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
  • 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

Un appareil et des procédés de communication sans fil comprennent un équipement d'utilisateur qui envoie un message de mise à jour de cellule configuré pour déclencher une procédure de mise à jour de cellule, reçoit un message de confirmation de mise à jour de cellule, et reçoit un message de reconfiguration après avoir reçu le message de confirmation de mise à jour de cellule. Les aspects de l'invention consistent à déterminer si le message de reconfiguration est valide ou invalide, d'après la condition de déclenchement de reconfiguration d'équipement utilisateur et/ou une condition de déclenchement de reconfiguration de réseau consécutive à la réception du message de confirmation de mise à jour de cellule. Les aspects de l'invention consistent également à reconfigurer ou à ne pas reconfigurer l'équipement d'utilisateur d'après le message de reconfiguration, selon que le message de reconfiguration est déterminé comme étant valide ou invalide.
PCT/CN2014/094615 2014-05-08 2014-12-23 Validation d'un message de reconfiguration WO2015169092A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
PCT/CN2014/077016 WO2015168895A1 (fr) 2014-05-08 2014-05-08 Appareil et procédés de validation d'un message de reconfiguration
CNPCT/CN2014/077016 2014-05-08

Publications (1)

Publication Number Publication Date
WO2015169092A1 true WO2015169092A1 (fr) 2015-11-12

Family

ID=54391983

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2014/077016 WO2015168895A1 (fr) 2014-05-08 2014-05-08 Appareil et procédés de validation d'un message de reconfiguration
PCT/CN2014/094615 WO2015169092A1 (fr) 2014-05-08 2014-12-23 Validation d'un message de reconfiguration

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/077016 WO2015168895A1 (fr) 2014-05-08 2014-05-08 Appareil et procédés de validation d'un message de reconfiguration

Country Status (1)

Country Link
WO (2) WO2015168895A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116669122A (zh) 2017-03-22 2023-08-29 交互数字专利控股公司 用于无线系统中分阶段重配置的系统和方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1519606A1 (fr) * 2003-09-29 2005-03-30 M-Stack Limited Procédé pour le traitement de la mise à jour de cellules pendant la reconfiguration dans un équipement utilisateur d'un réseau UMTS et équipement utilisateur correspondant
CN101646213A (zh) * 2008-08-07 2010-02-10 华为技术有限公司 小区重选优化方法和装置
CN103220716A (zh) * 2012-01-18 2013-07-24 中兴通讯股份有限公司 上行无线公共资源重配置方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8447291B2 (en) * 2011-04-14 2013-05-21 Qualcomm Incorporated Selective state transitions of a user equipment within a wireless communications system
CN103716834B (zh) * 2012-09-28 2017-09-08 展讯通信（上海）有限公司 解决小区更新后将ue配置到错误小区的方法与装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1519606A1 (fr) * 2003-09-29 2005-03-30 M-Stack Limited Procédé pour le traitement de la mise à jour de cellules pendant la reconfiguration dans un équipement utilisateur d'un réseau UMTS et équipement utilisateur correspondant
CN101646213A (zh) * 2008-08-07 2010-02-10 华为技术有限公司 小区重选优化方法和装置
CN103220716A (zh) * 2012-01-18 2013-07-24 中兴通讯股份有限公司 上行无线公共资源重配置方法及装置

Also Published As

Publication number Publication date
WO2015168895A1 (fr) 2015-11-12

Similar Documents

Publication Publication Date Title
EP3132625B1 (fr) Mécanisme de traitement de registre d'horloge perfectionné
US20150181476A1 (en) Baton handover transition for single receiver user equipment
US20150049737A1 (en) Measurement reporting when communicating with weak serving cell
US20150281989A1 (en) Delaying transmission of measurement report
US20110243099A1 (en) Method of Service Redirection Procedures in TD-SCDMA and GSM Hybrid Mobile Terminals
US8874111B2 (en) Uplink synchronization of TD-SCDMA multiple USIM mobile terminal during handover
WO2015195347A1 (fr) Gestion de transitions d'état de commande de ressources radio (rrc) dans un équipement utilisateur
US8958281B2 (en) Early termination of a base station identity code procedure in TD-SDCMA
US20130176866A1 (en) Call recovery in td-scdma handover failure
US20160073314A1 (en) Redirection history based circuit switched fall back
US20150094069A1 (en) Enhanced inter-radio access technology handover procedures
US20160057671A1 (en) Fast return after circuit switched fall back (csfb) call release
US20110292908A1 (en) Additional Service Type Setup in Mobile Terminals Having Multiple Radio Access Network Accessiblity
US20150201448A1 (en) Uplink pilot channel positioning for circuit switched fallback
US20150264613A1 (en) Modified reselection evaluation
WO2015184805A1 (fr) Procédé de réduction de taux d'abandon d'appels via l'ajournement d'un rapport tvm pendant et juste après une procédure de transfert
US20120230295A1 (en) Method and Apparatus to Support HSDPA ACK/CQI Operation During Baton Handover in TD-SCDMA Systems
US9179342B2 (en) FCCH burst detection abort method for inter-radio access technology (IRAT) measurement
WO2015169092A1 (fr) Validation d'un message de reconfiguration
US20160057685A1 (en) Multiple frequency measurement scheduling for cell reselection
US20150085754A1 (en) Methods and apparatus for enhanced frequency measurements
US20140179303A1 (en) Varying neighbor cell measurement periods based on serving cell signal strength
US20160066311A1 (en) Cell update procedure enhancements
US20150119038A1 (en) Method and apparatus for cell reselection during serving radio network subsystem (srns) relocation
US20160105856A1 (en) Disabling wireless channel reconfiguration requests

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: 14891364

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: 14891364

Country of ref document: EP

Kind code of ref document: A1