[go: up one dir, main page]

WO2015168895A1 - Appareil et procédés de validation d'un message de reconfiguration - Google Patents

Appareil et procédés de validation d'un message de reconfiguration Download PDF

Info

Publication number
WO2015168895A1
WO2015168895A1 PCT/CN2014/077016 CN2014077016W WO2015168895A1 WO 2015168895 A1 WO2015168895 A1 WO 2015168895A1 CN 2014077016 W CN2014077016 W CN 2014077016W WO 2015168895 A1 WO2015168895 A1 WO 2015168895A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
reconfiguration
cell update
valid
user equipment
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.)
Ceased
Application number
PCT/CN2014/077016
Other languages
English (en)
Inventor
Huan Xu
Yong Xie
Xuepan GUAN
Tim Tynghuei Liou
Shiau-He Tsai
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
Priority to PCT/CN2014/077016 priority Critical patent/WO2015168895A1/fr
Priority to PCT/CN2014/094615 priority patent/WO2015169092A1/fr
Publication of WO2015168895A1 publication Critical patent/WO2015168895A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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

  • aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to apparatus and methods for a user equipment to determine whether or not a received reconfiguration message is valid.
  • 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
  • the NW may have already initiated a new radio bearer reconfiguration procedure, for example for load balancing purposes, before the Cell Update message is received.
  • the NW may have a radio bearer reconfiguration message already been queued at the NW RLC layer and pending for delivery to the UE. In this case, after the NW receives the Cell Update .
  • the NW may abort the pending radio bearer reconfiguration procedure at NW RRC layer, and the NW will initiate and send a Cell Update Confirm message to the UE with new configurations.
  • their RLC layer may still keep the not transmitted radio bearer reconfiguration message and will start retransmission of the message after completion of a Cell Update Confirm procedure.
  • the radio bearer reconfiguration message becomes a dangling message that the higher layer of the NW has already discarded, and so the NW physical layer will not be configured accordingly.
  • the UE when the UE receives the radio bearer reconfiguration message after receiving Cell Update Confirm message, the UE does not know that the radio bearer reconfiguration message is a "leftover" radio bearer reconfiguration message at the NW RLC layer, e.g., a message that is already outdated. If the UE attempts to process this leftover radio bearer reconfiguration message, then a radio link failure may occur, which results in a call drop. Moreover, the processing of the leftover radio bearer reconfiguration message after receiving the Cell Update Confirm message may block or affect the on-going procedures, e.g. downlink measurement control messages.
  • apparatus and methods of a user equipment for wireless communication are configured to or include sending a cell update message configured to trigger a cell update procedure, receiving a cell update confirm message, and receiving a reconfiguration message after receiving the cell update confirm message. Further, the aspects include 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. Additionally, the aspects include reconfiguring or not reconfiguring the user equipment based on the reconfiguration message, depending on whether or not the reconfiguration message is determined to be valid or not valid.
  • FIG. 1 is a schematic diagram of a wireless communication system including an aspect of a user equipment having a reconfiguration validation component for determining whether or not a reconfiguration message received from a network device, after receipt of a cell update confirm message, is valid or not valid;
  • Fig. 2 is a flow chart of an aspect of an aspect of a method, e.g., executed by the user equipment of Fig. 1, to implement the functional characteristics of one aspect of the present disclosure
  • FIG. 3 is a schematic diagram of a telecommunications system including the user equipment and network device of Fig. 1;
  • Fig. 4 is a schematic diagram of an example of a frame structure that may be utilized by the user equipment and network device of Fig. 1;
  • Fig. 5 is a schematic diagram of an aspect of a user equipment in communication with a network device, such as an Radio Network Controller (RNC) and/or Node B, according to one or more aspects described herein.
  • RNC Radio Network Controller
  • the present disclosure includes apparatus and methods in which a user equipment (UE) is configured to determine whether a reconfiguration message, received from a network (NW) after the UE has performed a cell update procedure, is a leftover or outdated message, or a new message.
  • the reconfiguration message may be any type of reconfiguration message, such as, but not limited to, a Radio Bearer Reconfiguration message, a Physical Channel Reconfiguration message, and a Transport Channel Reconfiguration message.
  • a Radio Bearer Reconfiguration message such as, but not limited to, a Radio Bearer Reconfiguration message, a Physical Channel Reconfiguration message, and a Transport Channel Reconfiguration message.
  • the UE determines whether or not at least one of a UE reconfiguration triggering condition or a NW reconfiguration triggering condition has occurred subsequent to receiving the cell update confirm message from the network.
  • a UE reconfiguration triggering condition may include, but is not limited to, the UE sending an uplink message, such as a measurement report, that would cause the NW to respond with a reconfiguration message.
  • a NW reconfiguration triggering condition may include, but is not limited to, occurrence of a network management event, such as load balancing, which would lead the NW to send the reconfiguration message.
  • the UE when the UE determines that at least one of the UE reconfiguration triggering condition and the NW reconfiguration triggering condition has occurred since receiving the cell update confirm message, then the UE can determine that the reconfiguration message is valid and the UE can perform the reconfiguration. Alternatively, or in addition, when the UE determines that neither of the UE reconfiguration triggering condition and the NW reconfiguration triggering condition has occurred since receiving the cell update confirm message, then the UE can determine that the RB reconfiguration message is not valid. Thus, in the case of determining a not valid reconfiguration message, the UE can thereby avoid applying outdated configuration changes that may cause problems, such as a call drop.
  • a wireless communication network 10 includes a user equipment (UE) 12 configured to determine whether or not a reconfiguration message 14 received from a network device (NW) 16 is valid or not valid, and, in response, to reconfigure or not reconfigure a RB/channel 18 between UE 12 and NW 16.
  • Reconfiguration message 14 may be any type of reconfiguration message, such as, but not limited to, a Radio Bearer Reconfiguration message, a Physical Channel Reconfiguration message, and a Transport Channel Reconfiguration message.
  • UE 12 may include a UE radio bearer (RB) manager component 20 that interacts with a NW radio bearer (RB)/channel manager component 22 to initially establish a radio bearer and/or channel (RB/channel) 18 between UE 12 and NW 16.
  • NW 16 may be implemented by a radio network controller (RNC), or a Node B, or some combination of both.
  • RNC radio network controller
  • UE 12 is operating in a connected mode. Then, for example, as a result of changing radio conditions between UE 12 and NW 16, UE 12 may experience a Radio Link Control (RLC)
  • RLC Radio Link Control
  • UE 12 and/or a 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.
  • 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.
  • 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.
  • NW 16 may initiate the new reconfiguration procedure based on, for instance, information from UE 12, such as measurement report information, or based on other network information, such as loading.
  • NW 16 and/or NW RB/channel manager component 20 may have had reconfiguration message 14 queued at an NW RLC layer and pending for delivery to UE 12 at the time NW 16 received cell update message 26.
  • NW 16 and/or NW RB/channel manager component 20 may abort the pending reconfiguration procedure at the NW RRC layer, and the NW will initiate and send cell update confirm message 28 to UE 12 with new configurations.
  • their RLC layer may still keep the pending, e.g., "not transmitted,” reconfiguration message 14 and will start retransmission of this message after completion of a cell update confirm procedure associated with cell update confirm message 28.
  • UE 12 of the present aspects includes a radio bearer (RB) reconfiguration validation component 30 configured to execute a validation algorithm 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 validates if reconfiguration message 14 is a leftover or outdated message, or new one.
  • UE 12 and/or reconfiguration validation component 30 executes validation algorithm 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.
  • 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.
  • NW reconfiguration triggering condition 36 may include, but is not limited to, a condition caused by NW 16 that would have resulting in UE 12 receiving reconfiguration message 14, such as NW 16 performing a network management task including load balancing.
  • UE 12 and/or reconfiguration validation component 30 may execute validation algorithm 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
  • UE 12 and/or reconfiguration validation component 30 may execute validation algorithm 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, UE 12 and/or reconfiguration validation component 30 may execute validation algorithm 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.
  • 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 not valid when both of UE reconfiguration triggering condition 34 and NW reconfiguration triggering condition
  • the present aspects may determine that reconfiguration message 14 is leftover or outdated, and hence not valid, when UE 12 has not generated any uplink message (that could have triggered reconfiguration message 14) after the receipt of cell update confirm message 28 and when reconfiguration message 14 is received within guard time relative to receiving cell update confirm message 28.
  • 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 mobility manager component 20 may be configured to disregard reconfiguration message 14, or, optionally, to reply with a failure message 40 in response to reconfiguration message 14, when the determining determines that reconfiguration message 14 is not valid.
  • UE 12 may include a communications manager 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.
  • communications manager component 38 may include a bus that connects components internal to UE 12.
  • communications manager 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, and reconfiguration message 14, and maintaining a radio link, such as RB/channel 18.
  • an aspect of a method 200 of wireless communication includes, at block 202, sending, from a user equipment, a cell update message configured to trigger a cell update procedure.
  • UE 12 and/or UE RB/channel manager component 20 and/or cell update component 24 and/or communications manager 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 send cell update message 26, as discussed above.
  • 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 communications manager 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.
  • 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 communications manager 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.
  • 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.
  • the determining may include determining whether an uplink message (e.g., a measurement report) has been sent after the receipt of the cell update confirm message 28. Further, for example, in an aspect, the determining may include determining whether the reconfiguration message is received within a guard time relative to the receipt of the cell update confirm message 28. Additionally, in an aspect, the determining may determine that the reconfiguration message is not valid when both the user equipment reconfiguration
  • triggering condition and the network reconfiguration triggering condition have not occurred after receipt of cell update confirm message 28. Also, in an aspect, the determining may determine that the reconfiguration message is valid when the measurement report has been generated after the receiving of the cell update confirm message and when the reconfiguration message is not received within the guard time relative to the receiving of the cell update confirm message.
  • 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 the user equipment based on the reconfiguration message, or to ignore the reconfiguration message, depending on whether or not the reconfiguration message is determined to be valid or not valid.
  • the UE reconfigures the radio bearer/channel 18 to maintain a radio link with the network device.
  • the method may further include disregarding the reconfiguration message, or replying with a failure message 40 in response to the reconfiguration message 14.
  • the present apparatus and methods may reduce call drops caused by leftover RB reconfiguration messages due to a Cell Update procedure.
  • the UE needs to validate if the RB reconfiguration message is a leftover one or new one. If the message is a leftover one due to a race condition related to the cell update procedure, then the UE needs to discard such RB reconfiguration message.
  • the UE determines both of following conditions: (i) there are no UL message (e.g. measurement reports) that could have triggered a NW reconfigure that were sent out after the UE received Cell Update Confirm message— this condition is used to preclude the reconfiguration message being a valid one due to UE's response to the
  • 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. More specifically, on the UE side, 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.
  • any UL messages e.g. measurement report/service request
  • 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.
  • a block diagram is shown illustrating an example of additional components of telecommunications system 10, including one or more UEs 12 and one or more NWs 16 (which may include one or both of a Node B 308 and an RNC 306).
  • NWs 16 which may include one or both of a Node B 308 and an RNC 306.
  • 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.
  • RNC Radio Network Controller
  • the RNC 306 is an apparatus responsible for, among other things, assigning, reconfiguring and releasing radio resources within the RNS 307.
  • the RNC 306 may be interconnected to other RNCs (not shown) in the RAN 302 through various types of interfaces such
  • AFDOCS/10963108.1 as a direct physical connection, a virtual network, or the like, using any suitable transport network.
  • 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.
  • BS 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 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 310 are shown in communication with the Node Bs 308.
  • the downlink (DL) also called the forward link
  • the uplink (UL) also called the reverse link
  • 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, may be connected to the MSC 312.
  • the MSC 312 is an
  • 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 is 10 ms in length.
  • AFDOCS/10963108.1 has two 5 ms subframes 404, and each of the subframes 404 includes seven time slots, TSO through TS6.
  • the first time slot, TSO 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 (also known as the uplink pilot channel (UpPCH)) are located between TSO and TS1.
  • DwPTS downlink pilot time slot
  • GP guard period
  • UpPTS uplink pilot time slot
  • UpPCH uplink pilot channel
  • 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 communications component 38 in the remaining illustrated components.
  • 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.
  • 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
  • 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 from a transmit processor 580.
  • the data source 578 may represent applications running in the UE 12 and various user interfaces (e.g., keyboard). Similar to the functionality described in connection with the downlink transmission by the NW 16, the transmit processor 580 provides various signal
  • AFDOCS/10963108.1 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.
  • 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
  • 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.
  • 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,
  • AFDOCS/10963108.1 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

La présente invention concerne un appareil et des procédés de communication sans fil comprenant 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 la réception du message de confirmation de mise à jour de cellule. D'autres aspects consistent à déterminer si le message de reconfiguration est valide ou non valide sur la base d'une condition de déclenchement de reconfiguration de l'équipement d'utilisateur et/ou d'une condition de déclenchement de reconfiguration du réseau survenant à la suite de la réception du message de confirmation de mise à jour de cellule. En plus, les aspects consistent à reconfigurer ou à ne pas reconfigurer l'équipement d'utilisateur sur la base du message de reconfiguration selon qu'il est déterminé ou non que le message de reconfiguration est valide ou non valide.
PCT/CN2014/077016 2014-05-08 2014-05-08 Appareil et procédés de validation d'un message de reconfiguration Ceased WO2015168895A1 (fr)

Priority Applications (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
PCT/CN2014/094615 WO2015169092A1 (fr) 2014-05-08 2014-12-23 Validation d'un message de reconfiguration

Applications Claiming Priority (1)

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

Publications (1)

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

Family

ID=54391983

Family Applications (2)

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

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/094615 Ceased WO2015169092A1 (fr) 2014-05-08 2014-12-23 Validation d'un message de reconfiguration

Country Status (1)

Country Link
WO (2) WO2015168895A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11985559B2 (en) 2017-03-22 2024-05-14 Interdigital Patent Holdings, Inc. System and methods for phased reconfiguration in wireless systems
US12035187B2 (en) 2017-03-22 2024-07-09 Interdigital Patent Holdings, Inc. Delayed handover execution in wireless networks based on a trigger condition

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101646213A (zh) * 2008-08-07 2010-02-10 华为技术有限公司 小区重选优化方法和装置
US20120264416A1 (en) * 2011-04-14 2012-10-18 Qualcomm Incorporated Selective state transitions of a user equipment within a wireless communications system
CN103716834A (zh) * 2012-09-28 2014-04-09 展讯通信（上海）有限公司 解决小区更新后将ue配置到错误小区的方法与装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1519606B8 (fr) * 2003-09-29 2008-07-02 Research in Motion 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
CN103220716B (zh) * 2012-01-18 2017-10-13 中兴通讯股份有限公司 上行无线公共资源重配置方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101646213A (zh) * 2008-08-07 2010-02-10 华为技术有限公司 小区重选优化方法和装置
US20120264416A1 (en) * 2011-04-14 2012-10-18 Qualcomm Incorporated Selective state transitions of a user equipment within a wireless communications system
CN103716834A (zh) * 2012-09-28 2014-04-09 展讯通信（上海）有限公司 解决小区更新后将ue配置到错误小区的方法与装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11985559B2 (en) 2017-03-22 2024-05-14 Interdigital Patent Holdings, Inc. System and methods for phased reconfiguration in wireless systems
US12035187B2 (en) 2017-03-22 2024-07-09 Interdigital Patent Holdings, Inc. Delayed handover execution in wireless networks based on a trigger condition
US12439308B2 (en) 2017-03-22 2025-10-07 Interdigital Patent Holdings, Inc. System and methods for phased reconfiguration in wireless systems

Also Published As

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

Similar Documents

Publication Publication Date Title
US8594670B2 (en) Measurement and handover of dual USIM mobile terminal
EP3132625B1 (fr) Mécanisme de traitement de registre d'horloge perfectionné
US20150281989A1 (en) Delaying transmission of measurement report
US8874111B2 (en) Uplink synchronization of TD-SCDMA multiple USIM mobile terminal during handover
US20110243099A1 (en) Method of Service Redirection Procedures in TD-SCDMA and GSM Hybrid Mobile Terminals
US8902905B2 (en) Area update procedures for a multiple USIM mobile terminal
US20130176866A1 (en) Call recovery in td-scdma handover failure
US8958281B2 (en) Early termination of a base station identity code procedure in TD-SDCMA
US20160073314A1 (en) Redirection history based circuit switched fall back
US9331818B2 (en) Method and apparatus for optimized HARQ feedback with configured measurement gap
WO2013173380A1 (fr) Système et appareil destinés à des améliorations multirab en maintenant actifs un appel vocal à commutation de circuit et une session de données à commutation de paquets
US20120039261A1 (en) CQI Reporting of TD-SCDMA Multiple USIM Mobile Terminal During HSDPA Operation
US8594054B2 (en) Technique for scheduling TD-SCDMA idle intervals
US20150201448A1 (en) Uplink pilot channel positioning for circuit switched fallback
US20150264613A1 (en) Modified reselection evaluation
US20110292871A1 (en) Wireless Attachment To Multiple Radio Access Networks At The Same Time
WO2015169092A1 (fr) Validation d'un message de reconfiguration
US20130223428A1 (en) Method and apparatus for irat measurement when in td-scdma connected mode
US20120230295A1 (en) Method and Apparatus to Support HSDPA ACK/CQI Operation During Baton Handover in TD-SCDMA Systems
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
US8718017B2 (en) Confirmation of base station identification to improve handover
US20140179303A1 (en) Varying neighbor cell measurement periods based on serving cell signal strength
WO2015065783A1 (fr) Procédé et appareil de resélection de cellule durant un repositionnement d'un sous-système de réseau radio de desserte (srns)
US20160105856A1 (en) Disabling wireless channel reconfiguration requests
WO2015131311A1 (fr) Appareils et procédés de transfert dans des systèmes td-scdma

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

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

Country of ref document: EP

Kind code of ref document: A1