[go: up one dir, main page]

WO2018031110A1 - Support x2 pour mobilité améliorée (emob) - Google Patents

Support x2 pour mobilité améliorée (emob) Download PDF

Info

Publication number
WO2018031110A1
WO2018031110A1 PCT/US2017/035736 US2017035736W WO2018031110A1 WO 2018031110 A1 WO2018031110 A1 WO 2018031110A1 US 2017035736 W US2017035736 W US 2017035736W WO 2018031110 A1 WO2018031110 A1 WO 2018031110A1
Authority
WO
WIPO (PCT)
Prior art keywords
handover
handover request
acknowledge message
rach
request acknowledge
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/US2017/035736
Other languages
English (en)
Inventor
Candy YIU
Yujian Zhang
Alexander Sirotkin
Umesh PHUYAL
Youn Hyoung Heo
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.)
Intel IP Corp
Original Assignee
Intel IP Corp
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 Intel IP Corp filed Critical Intel IP Corp
Priority to DE112017004034.5T priority Critical patent/DE112017004034T5/de
Publication of WO2018031110A1 publication Critical patent/WO2018031110A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/0077—Transmission or use of information for re-establishing the radio link of access information of target 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/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]

Definitions

  • the random-access channel (RACH) procedure is utilized to obtain a timing advance (TA) value for the target eNB 112.
  • TA timing advance
  • a RACH procedure may be avoided at least in some deployments without introducing any new time alignment control or estimation mechanisms because the network knows when the timing alignment is the same for both source and target cells.
  • FIG. 1 is a diagram of a RACH-less handover procedure wherein a timing advance for a target cell is approximately equal to zero in accordance with one or more embodiments;
  • FIG. 2 is a diagram of a RACH-less handover procedure using a MobilityControlInfo information element in accordance with one or more embodiments
  • FIG. 3A and FIG. 3B show a flow diagram of a RACH-less handover procedure in accordance with one or more embodiments
  • FIG. 4 illustrates example components of a device 400 in accordance with some embodiments.
  • FIG. 5 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • Coupled may mean that two or more elements are in direct physical and/or electrical contact.
  • coupled may also mean that two or more elements may not be in direct contact with each other, but yet may still cooperate and/or interact with each other.
  • “coupled” may mean that two or more elements do not contact each other but are indirectly joined together via another element or intermediate elements.
  • “On,” “overlying,” and “over” may be used to indicate that two or more elements are in direct physical contact with each other. It should be noted, however, that “over” may also mean that two or more elements are not in direct contact with each other. For example, “over” may mean that one element is above another element but not contact each other and may have another element or elements in between the two elements.
  • the term “and/or” may mean “and”, it may mean “or”, it may mean “exclusive-or”, it may mean “one”, it may mean “some, but not all”, it may mean “neither", and/or it may mean “both”, although the scope of claimed subject matter is not limited in this respect.
  • the terms “comprise” and “include,” along with their derivatives, may be used and are intended as synonyms for each other.
  • FIG. 1 a diagram of a RACH-less handover procedure wherein a timing advance for a target cell is approximately equal to zero in accordance with one or more embodiments will be discussed.
  • the random-access channel (RACH) procedure is utilized to obtain a timing advance (TA) value for the target eNB 112.
  • TA timing advance
  • UE 114 may be able to obtain the TA value for the target eNB 112 without an explicit TA command if the source eNB 110 and the target eNB 112 are time synchronized.
  • UE 114 may obtain the difference in downlink (DL) propagation delays between the source eNB 110, having a propagation delay Tl, and the target eNB 112, having a propagation delay T2.
  • the DL propagation delay difference is T1-T2. If it is assumed that the uplink (UL) propagation delay is the same as the DL propagation delay, UE 114 may derive the TA value for the target eNB 112 from the TA value of the source eNB 110 as follows:
  • RACH procedure during handover is to obtain an UL grant for the transmission of the handover command response, the radio resource control (RRC) Connection Reconfiguration Complete message.
  • RRC radio resource control
  • allocation of the UL grant is needed in the target eNB 112.
  • One option is to utilize a UL grant pre-allocation in handover command.
  • the pre-allocated UL grant may be kept valid within a period of time, starting from the time when UE 114 achieves synchronization with the target eNB 112.
  • Another option is to utilize a UL grant allocation by dynamic scheduling in the target eNB 112.
  • the target eNB 112 may allocate an UL grant to UE 114 by dynamic scheduling from the time when target eNB 112 expects UE 114 to be available for scheduling, for example based on mutually agreed time, or sometime later after the handover preparation procedure which is subject to implementation by the target eNB 112.
  • the initial value of physical uplink shared channel (PUSCH) transmission power control may be based on physical random access channel (PRACH) preamble power and total power ramp. If the PRACH procedure is removed, power control in the PUSCH may be modified.
  • PRACH physical random access channel
  • a RACH-less procedure may involve obtaining a TA value for the target eNB 112, power ramping, and an UL grant.
  • the TA value may be obtained from either a calculation performed by UE 114 or from a calculation performed by the network such as by the source eNB 110 or the target eNB 112.
  • it may be possible to skip the RACH procedure for handover to small cell which has a small radius, for example less than about 240 meters, although the scope of the claimed subject matter is not limited in this respect.
  • TA 0, configured by the network
  • a RACH-less handover may be applied in a handover from a macro cell to a small cell, wherein the source eNB 110 is a macro cell and the target eNB 112 is a small cell.
  • a RACH-less handover may be applied in a handover from a small cell to a small cell, wherein the source eNB 110 is a small cell and the target eNB 112 is a small cell.
  • a macro cell may refer to a cell in a cellular network that generally may provide a higher power cellular base station, typically the highest power base station on the network with an output power on the order of tens of watts.
  • a small cell may refer to a radio access node of a network that may operate on the network with a lower output power and range that is less than the power of the higher power macro cell and which may include, for example, femtocells, picocells, and/or microcells, although the scope of the claimed subject matter is not limited in this respect.
  • Options for providing knowledge to UE 114 to know if a RACH-less handover may be utilized are shown in and described with respect to FIG. 2, below.
  • UE 114 may perform a handover from source eNB 110 using link 116 to target eNB 112 using link 118.
  • UE 114 may know whether or not a RACH-less handover (HO), or a RACH-skip, may be utilized as follows.
  • HO RACH-less handover
  • UE 114 sends the measurement report to the source eNB 110.
  • the source eNB 110 then may decide whether or not to handover UE 114 to the target eNB 112.
  • the target eNB 110 may decide to apply a RACH-less handover when receive HO request from source eNB.
  • the decision to apply a RACH-less handover may be indicated in the handover command sent to UE 114 from the source eNB 110 (but the information for mobility is generated by target eNB), for example in the mobility control information element (IE) MobilityControlInfo (generated by target eNB) that is sent with the RRC Connection Reconfiguration message RRCConnectionReconfiguration in the handover command in accordance with the Third Generation Partnership Project (3 GPP) Technical Standard (TS) 36.331 shown below.
  • IE mobility control information element
  • MobilityControlInfo generated by target eNB
  • the mobility control IE MobilityControlInfo includes parameters relevant for network controlled mobility to and/or within the Evolved Universal Terrestrial Radio Access (E-UTRA).
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • the modification to the mobility control information element (IE) MobilityControlInfo providing the indication to apply a RACH-less handover to a small is shown in underlining, below.
  • a handover (HO) of UE 114 from source eNB 110 to target eNB 112 may be implemented in compliance with a 3GPP Technical Standard (TS), for example as described in Section 5.3.1.3 "Connected mod mobility" of 3GPP TS 36.331 Release 14, although the scope of the claimed subject matter is not limited in this respect.
  • TS 3GPP Technical Standard
  • the network controls UE 114 mobility, i.e. the network decides when the UE 114 shall connect to which Evolved Universal Terrestrial Radio Access (E-UTRA) cell(s), or inter Radio Access Technology (inter-RAT) cell.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • inter-RAT Inter-RAT
  • the Primary Cell (PCell) can be changed using an RRCConnectionReconfiguration message including the mobilityControlInfo (handover), whereas the Secondary Cell or Cells (SCell(s)) can be changed using the RRCConnectionReconfiguration message either with or without the mobilityControlInfo.
  • PCell Primary Cell
  • SCell(s) Secondary Cell or Cells
  • An SCG can be established, reconfigured or released by using an
  • RRCConnectionReconfiguration message with or without the mobilityControlInfo.
  • E-UTRAN employs the SCG change procedure (i.e. an RRCConnectionReconfiguration message including the
  • the Primary SCell (PSCell) can only be changed using the SCG change procedure and by release and addition of the PSCell.
  • the network triggers the handover procedure, for example based on radio conditions, load.
  • the network may configure the UE 114 to perform measurement reporting (possibly including the configuration of measurement gaps).
  • the network may also initiate handover blindly, that is without having received measurement reports from the UE 114.
  • the source eNB 110 Before sending the handover message to the UE 114, the source eNB 110 prepares one or more target cells.
  • the source eNB 110 selects the target PCell.
  • the source eNB 110 may also provide the target eNB 112 with a list of best cells on each frequency for which measurement information is available, in order of decreasing Reference Signal Received Power (RSRP).
  • RSRP Reference Signal Received Power
  • the source eNB 110 may also include available measurement information for the cells provided in the list.
  • the target eNB 112 decides which SCells are configured for use after handover, which may include cells other than the ones indicated by the source eNB. If an SCG is configured, handover involves either SCG release or SCG change.
  • the target eNB 112 indicates in the handover message whether the UE 114 shall release the entire SCG configuration.
  • the UE 114 releases the entire SCG configuration except for the Data Radio Bearer (DRB) configuration, while E-UTRAN in the first reconfiguration message following the re-establishment either releases the DRB(s) or reconfigures the DRB(s) to Master Cell Group (MCG) DRB(s).
  • DRB Data Radio Bearer
  • the target eNB 112 generates the message used to perform the handover, i.e. the message including the Access Stratum configuration (AS-configuration) to be used in the target cell(s).
  • the source eNB 110 transparently (i.e. does not alter values/ content) forwards the handover message/ information received from the target to the UE.
  • the source eNB 110 may initiate data forwarding for (a subset of) the DRBs.
  • the UE 114 After receiving the handover message, the UE 114 attempts to access the target PCell at the first available RACH occasion according to Random Access resource selection defined in 3GPP TS 36.321, i.e. the handover is asynchronous, or at the first available Physical Uplink Control Channel (PUSCH) occasion if RACH-Skip is configured. Consequently, when allocating a dedicated preamble for the random access in the target PCell, E-UTRA shall ensure it is available from the first RACH occasion the UE 114 may use.
  • the UE 114 Upon successful completion of the handover, the UE 114 sends a message used to confirm the handover.
  • PUSCH Physical Uplink Control Channel
  • the target eNB 112 may be unable to comprehend the UE 114 configuration provided by the source eNB 110. In this case, the target eNB 112 should use the full configuration option to reconfigure the UE 114 for Handover and Re-establishment.
  • Full configuration option includes an initialization of the radio configuration, which makes the procedure independent of the configuration used in the source cell(s) with the exception that the security algorithms are continued for the RRC re- establishment.
  • Packet Data Convergence Protocol (PDCP) Service Data Units (SDUs) may be re-transmitted in the target cell(s). This only applies for DRBs using Radio Link Control Acknowledgement Mode (RLC-AM) mode and for handovers not involving full configuration option.
  • RLC-AM Radio Link Control Acknowledgement Mode
  • the further details are specified in 3GPP TS 36.323.
  • the Sequence Number (SN) and the Hyper Frame Number (HFN) are reset except for the DRBs using RLC-AM mode (for which both SN and HFN continue).
  • the PDCP entities are newly established (SN and HFN do not continue) for all DRBs irrespective of the RLC mode.
  • the further details are specified in 3GPP TS 36.323.
  • One UE 114 behavior to be performed upon handover is specified, i.e. this is regardless of the handover procedures used within the network (e.g. whether the handover includes X2 or SI signaling procedures).
  • the source eNB 110 should, for some time, maintain a context to enable the UE 114 to return in case of handover failure.
  • the UE 114 attempts to resume the RRC connection either in the source PCell or in another cell using the RRC re-establishment procedure. This connection resumption succeeds only if the accessed cell is prepared, i.e. concerns a cell of the source eNB 110 or of another eNB towards which handover preparation has been performed.
  • E-UTRAN may configure the UE 114 to report that it is entering or leaving the proximity of cell(s) included in its CSG whitelist.
  • E-UTRAN may request the UE 114 to provide additional information broadcast by the handover candidate cell e.g. global cell identity, CSG identity, CSG membership status.
  • E-UTRAN may use the 'proximity report' to configure measurements as well as to decide whether or not to request additional information broadcast by the handover candidate cell.
  • the additional information is used to verify whether or not the UE 114 is authorized to access the target PCell and may also be needed to identify handover candidate cell (Physical Cell Identity (PCI) confusion i.e. when the physical layer identity that is included in the measurement report does not uniquely identify the cell).
  • PCI Physical Cell Identity
  • the RACH-less handover procedure shown in FIG. 3A and 3B may be adopted in a Third-Generation Partnership Project (3 GPP) Technical Standard (TS) such as 3GPP TS 36.300.
  • TS Technical Standard
  • the procedure of FIG. 3A and 3B may include the following procedures including one or more procedures for an enhanced mobility (eMOB) UE 114 as discussed below.
  • eMOB enhanced mobility
  • the UE 114 context within the source eNB 110 contains information regarding roaming and access restrictions which were provided either at connection establishment or at the last timing advance (TA) update.
  • the source eNB 110 configures the UE 114 measurement procedures according to the roaming and access restriction information and the available multiple frequency band information. Measurements provided by the source eNB 110 may assist the function controlling the UE's connection mobility.
  • a MEASUREMENT REPORT is triggered and sent to the source eNB 110.
  • the source eNB 110 makes decision based on MEASUREMENT REPORT and radio resource management (RRM) information to hand off the UE 114.
  • RRM radio resource management
  • the source eNB 110 issues a HANDOVER REQUEST message to the target eNB 112 passing necessary information to prepare the handover (HO) at the target side via UE X2 signaling context reference at source eNB 110, UE SI EPC signaling context reference, target cell 112 identifier (ID), evolved Node B key (KeNB*), radio resource control (RRC) context including the cell radio network temporary identifier (C-RNTI) of the UE 114 in the source eNB 110, access stratum (AS) configuration, E-UTRAN Radio Access Bearer (E-RAB) context and physical layer ID of the source cell and short Message Authentication Code Integrity (MAC-I) for possible radio link failure (RLF) recovery.
  • UE X2 signaling context reference at source eNB 110 UE SI EPC signaling context reference
  • ID target cell 112 identifier
  • KeNB* evolved Node B key
  • RRC radio resource control
  • C-RNTI cell radio network temporary identifier
  • AS access stratum
  • the E-RAB context includes necessary Radio Network Layer (RNL) and Transport Network Layer (TNL) addressing information, and Quality of Service (QoS) profiles of the E-RABs.
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • QoS Quality of Service
  • Admission Control may be performed by the target eNB 112 dependent on the received E-RAB QoS information to increase the likelihood of a successful HO, if the resources can be granted by the target eNB 112.
  • the target eNB 112 configures the required resources according to the received E-RAB QoS information and reserves a C-RNTI and optionally a RACH preamble.
  • the AS-configuration to be used in the target cell 112 may either be specified independently, as an "establishment", or as a delta compared to the AS- configuration used in the source cell, as a "reconfiguration".
  • the target eNB 112 prepares HO with Layer 1 and Layer 2 (L1/L2) and sends the HANDOVER REQUEST ACKNOWLEDGE to the source eNB 110, for example via the X2 interface.
  • the HANDOVER REQUEST ACKNOWLEDGE message includes a transparent container to be sent to the UE 114 as an RRC message to perform the handover.
  • the container includes a new C-RNTI, target eNB 112 security algorithm identifiers for the selected security algorithms, and may include a dedicated RACH preamble, periodic uplink (UL) grant and possibly some other parameters, that is access parameters, System Information Blocks (SIBs), and so on.
  • SIBs System Information Blocks
  • the HANDOVER REQUEST ACKNOWLEDGE message may also include RNL/TNL information for the forwarding tunnels, if necessary.
  • the target eNB 112 prepares handover (HO) with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE to the source eNB 110, for example via the X2 interface.
  • the HANDOVER REQUEST ACKNOWLEDGE message includes a transparent container to be sent to the UE 114 as an RRC message to perform the handover.
  • the container includes a new C-RNTI, target eNB 112 security algorithm identifiers for the selected security algorithms, may include a dedicated RACH preamble, and possibly some other parameters i.e., access parameters, SIBs, etc.
  • the container includes timing adjustment indication and optionally a pre-allocated uplink grant.
  • the HANDOVER REQUEST ACKNOWLEDGE message may also include RNL/TNL information for the forwarding tunnels, if necessary.
  • the target eNB 112 may acknowledge a RACH-less handover via a pre-allocated periodic uplink (UL) grant via the HANDOVER REQUEST ACKNOWLEDGE message.
  • the indication by target eNB 112 of a RACH-less handover may be implicit via target eNB 112 providing a pre-allocated UL grant to the UE 114 via the HANDOVER REQUEST ACKNOWLEDGE message in response to a RACH-less HANDOVER REQUEST message provided by source eNB 110 to target eNB 112.
  • Operation 7 through operation 16 provide a mechanism to avoid data loss during HO and are further detailed in sections 10.1.2.1.2 and 10.1.2.3 of 3 GPP TS 36.300.
  • the target eNB 112 generates the RRC message to perform the handover, that is the RRCConnectionReconfiguration message including the mobility Controllnformation, to be sent by the source eNB 110 towards the UE 114.
  • the source eNB 110 performs the necessary integrity protection and ciphering of the message.
  • the UE 114 receives the RRCConnectionReconfiguration message with necessary parameters, including new C-RNTI, target eNB 112 security algorithm identifiers, and optionally dedicated RACH preamble, target eNB SIBs, UL grant, and so on, and is commanded by the source eNB 110 to perform the HO.
  • the UE 114 does not need to delay the handover execution for delivering the hybrid automatic repeat request and/or automatic repeat request (HARQ/ARQ) responses to source eNB 110.
  • the source eNB 110 continues sending downlink data to the UE 114 in the subframe that is not allocated for periodic UL grant after sending the RRCConnectionReconfiguration message to the UE 114.
  • the source eNB 110 sends the sequence number (SN) status transfer SN STATUS TRANSFER message to the target eNB 112 to convey the uplink Packet Data Convergence Protocol SN (PDCP SN) receiver status and the downlink PDCP SN transmitter status of E-RABs for which PDCP status preservation applies, that is for RLC Acknowledge Mode (AM).
  • the uplink PDCP SN receiver status includes at least the PDCP SN of the first missing UL SDU and may include a bit map of the receive status of the out of sequence UL Service Data Units (SDUs) that the UE 114 needs to retransmit in the target cell 112, if there are any such SDUs.
  • SDUs Service Data Units
  • the downlink PDCP SN transmitter status indicates the next PDCP SN that the target eNB 112 shall assign to new SDUs, not having a PDCP SN yet.
  • the source eNB 110 may omit sending this message if none of the E-RABs of the UE 114 shall be treated with PDCP status preservation.
  • the UE 114 when the UE 114 is ready to synchronize to the target eNB 112, it uses the earliest periodic UL grant to send the RRCConnectionReconfigurationComplete message (C- RNTI) to confirm the handover, along with an uplink Buffer Status Report, whenever possible, to the target eNB 112 to indicate that the handover procedure is completed for the UE 114.
  • the target eNB 112 verifies the C-RNTI sent in the RRCConnectionReconfigurationComplete message.
  • the target eNB can now begin sending data to the UE.
  • the target eNB 112 can optionally send an indicator to source eNB 110 indicating the UE 114 has successfully accessed the target cell 112.
  • both source eNB 110 and target eNB 112 will support such a feature. Therefore, the source eNB 110 may indicate to the target eNB 112 in the handover request message that this handover maybe using RACH-less handover. If the target eNB 112 is able to support it, the target eNB 112 will generate the periodic UL grant in the transparent container in the handover request message. As shown below, the existing information element (IE) for a handover request in 3GPP TS 36.423 with the added information to support a RACH-less handover indicated via underlining.
  • IE existing information element
  • RACH-lessHO can be Boolean as follows:
  • Target eNB 112 may reply with the following options. For Option 1 : Target eNB 112 provides an implicit reply with the periodic UL grant in the mobilityConrolInfo in the HANDOVER REQUEST ACKNOWLEDGE message. For Option 2: Target eNB 112 may provide an explicit indicator in the HANDOVER REQUEST ACKNOWLEDGE message with the periodic UL grant in the mobilityConrolInfo in the HANDOVER REQUEST ACKNOWLEDGE message.
  • target eNB 112 may reply with the following options.
  • Target eNB 112 provides an implicit reject without the periodic UL grant in the mobilityConrolInfo in the HANDOVER REQUEST ACKNOWLEDGE message.
  • Target eNB 112 provides an explicit indication in the HANDOVER REQUEST ACKNOWLEDGE message that target eNB 112 does not support RACH-less handover.
  • Option 1 may involve changes in 3GPP TS 36.331. If RACH-less handover is supported, periodic UL grants for handover purposes may be specified in 3GPP TS 36.331. The reception of an RRCConnectionReconfiguration message including the mobilityControlInfo may be described in 3GPP TS 36.331 as follows.
  • start timer T304 with the timer value set to t304, as included in the mobilityControlInfo; 1> stop timer T370, if running;
  • the UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.
  • makeBeforeBreak is configured:
  • the received RRCConnectionReconfiguration includes the scg-Configuration; or 1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb- ToAddModList:
  • 3> include rlf-Info Available
  • discRxInterest or discTxResourceReq if SystemInformationBlockTypel9 includes discConfigPS or discRxGapReq or discTxGapReq if the UE is configured with gapRequestsAUowedDedicated set to true or if the UE is not configured with gapRequestsAUowedDedicated and SystemInformationBlockTypel9 includes gapRequestsAllowedCommon) during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInf o :
  • the UE is not required to determine the SFN of the target PCell by acquiring system information from that cell before performing RACH access in the target PCell, except for BL UEs or UEs in CE.
  • the MobilityControlInfo information element may be described in 3GPP TS 36.331 as follows.
  • MobilityControlInfo :: SEQUENCE ⁇
  • RadioResourceConfigCommon RadioResourceConfigCommon, rach-ConfigDedicated RACH-ConfigDedicated
  • MobilityControlInfoSCG-rl2 SEQUENCE ⁇
  • MobilityControlInfoV2X-rl4 SEQUENCE ⁇
  • CarrierBandwidthEUTRA SEQUENCE ⁇
  • CarrierFreqEUTRA :: SEQUENCE ⁇
  • CarrierFreqEUTRA-v9eO :: SEQUENCE ⁇
  • Option 2 may involve changes in 3GPP TS 36.423 as shown below in underlining.
  • HandoverRequestAcknowledge-IEs X2AP-PROTOCOL-IES :: ⁇
  • RACH-lessHO ENUMERATED ⁇ True. False!
  • RACH-lessHO may be Boolean as follows:
  • FIG. 4 illustrates example components of a device 400 in accordance with some embodiments.
  • the device 400 may include application circuitry 402, baseband circuitry 404, Radio Frequency (RF) circuitry 406, front-end module (FEM) circuitry 408, one or more antennas 410, and power management circuitry (PMC) 412 coupled together at least as shown.
  • the components of the illustrated device 400 may be included in a UE or a RAN node.
  • the device 400 may include less elements (e.g., a RAN node may not utilize application circuitry 402, and instead include a processor/controller to process IP data received from an EPC).
  • the device 400 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud- RAN (C-RAN) implementations).
  • C-RAN Cloud- RAN
  • the application circuitry 402 may include one or more application processors.
  • the application circuitry 402 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 400.
  • processors of application circuitry 402 may process IP data packets received from an EPC.
  • the baseband circuitry 404 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 404 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 406 and to generate baseband signals for a transmit signal path of the RF circuitry 406.
  • Baseband processing circuity 404 may interface with the application circuitry 402 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 406.
  • the baseband circuitry 404 may include a third generation (3G) baseband processor 404A, a fourth generation (4G) baseband processor 404B, a fifth generation (5G) baseband processor 404C, or other baseband processor(s) 404D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 404 e.g., one or more of baseband processors 404A-D
  • baseband processors 404A-D may be included in modules stored in the memory 404G and executed via a Central Processing Unit (CPU) 404E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 404 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 404 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 404 may include one or more audio digital signal processor(s) (DSP) 404F.
  • the audio DSP(s) 404F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 404 and the application circuitry 402 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 404 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 404 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 404 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 406 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 406 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 406 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 408 and provide baseband signals to the baseband circuitry 404.
  • RF circuitry 406 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 404 and provide RF output signals to the FEM circuitry 408 for transmission.
  • the receive signal path of the RF circuitry 406 may include mixer circuitry 406a, amplifier circuitry 406b and filter circuitry 406c.
  • the transmit signal path of the RF circuitry 406 may include filter circuitry 406c and mixer circuitry 406a.
  • RF circuitry 406 may also include synthesizer circuitry 406d for synthesizing a frequency for use by the mixer circuitry 406a of the receive signal path and the transmit signal path.
  • the mixer circuitry 406a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 408 based on the synthesized frequency provided by synthesizer circuitry 406d.
  • the amplifier circuitry 406b may be configured to amplify the down-converted signals and the filter circuitry 406c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down- converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 404 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 406a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 406a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 406d to generate RF output signals for the FEM circuitry 408.
  • the baseband signals may be provided by the baseband circuitry 404 and may be filtered by filter circuitry 406c.
  • the mixer circuitry 406a of the receive signal path and the mixer circuitry 406a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 406a of the receive signal path and the mixer circuitry 406a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 406a of the receive signal path and the mixer circuitry 406a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 406a of the receive signal path and the mixer circuitry 406a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 406 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 404 may include a digital baseband interface to communicate with the RF circuitry 406.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 406d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 406d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 406d may be configured to synthesize an output frequency for use by the mixer circuitry 406a of the RF circuitry 406 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 406d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 404 or the applications processor 402 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 402.
  • Synthesizer circuitry 406d of the RF circuitry 406 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 406d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 406 may include an IQ/polar converter.
  • FEM circuitry 408 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 410, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 406 for further processing.
  • FEM circuitry 408 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 406 for transmission by one or more of the one or more antennas 410.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 406, solely in the FEM 408, or in both the RF circuitry 406 and the FEM 408.
  • the FEM circuitry 408 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 406).
  • the transmit signal path of the FEM circuitry 408 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 406), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 410).
  • PA power amplifier
  • the PMC 412 may manage power provided to the baseband circuitry 404.
  • the PMC 412 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 412 may often be included when the device 400 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 412 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 4 shows the PMC 412 coupled only with the baseband circuitry 404.
  • the PMC 4 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 402, RF circuitry 406, or FEM 408.
  • the PMC 412 may control, or otherwise be part of, various power saving mechanisms of the device 400. For example, if the device 400 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 400 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 400 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 400 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 400 may not receive data in this state, in order to receive data, it must transition back to RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 402 and processors of the baseband circuitry 404 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 404 may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 404 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 5 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 404 of FIG. 4 may comprise processors 404A-404E and a memory 404G utilized by said processors.
  • Each of the processors 404A-404E may include a memory interface, 504A-504E, respectively, to send/receive data to/from the memory 404G.
  • the baseband circuitry 404 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 512 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 404), an application circuitry interface 514 (e.g., an interface to send/receive data to/from the application circuitry 402 of FIG. 4), an RF circuitry interface 516 (e.g., an interface to send/receive data to/from RF circuitry 406 of FIG.
  • a memory interface 512 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 404
  • an application circuitry interface 514 e.g., an interface to send/receive data to/from the application circuitry 402 of FIG. 4
  • an RF circuitry interface 516 e.g., an interface to send/receive data to/from RF circuitry 406 of FIG.
  • a wireless hardware connectivity interface 518 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 520 e.g., an interface to send/receive power or control signals to/from the PMC 412.
  • circuit may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.
  • an apparatus of a source evolved Node B (eNB) to perform a handover of a user equipment (UE) to a target eNB comprises one or more baseband processors to generate a handover request message for the target eNB, wherein the handover request message indicates a RACH-less handover is to be used, and to process a handover request acknowledge message from the target eNB, and a memory to store the handover request acknowledge message, wherein the one or more baseband processors determine if a RACH-less handover should be applied based at least in part on the handover acknowledge message, and wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • eNB source evolved Node B
  • the apparatus may include the subject matter of example one or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via an indicator in the handover request acknowledge message.
  • the apparatus may include the subject matter of example one or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an absence of a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • the apparatus may include the subject matter of example one or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an indicator in the handover request acknowledge message.
  • the apparatus may include the subject matter of example one or any of the examples described herein, wherein the handover request message or the handover request acknowledge message, or a combination thereof, are sent via X2 signaling.
  • an apparatus of a target evolved Node B (eNB) to perform a handover of a user equipment (UE) from a source eNB comprises one or more baseband processors to process a handover request message from the source eNB, wherein the handover request message indicates a RACH-less handover is to be used, and a memory to store the handover request message, wherein the one or more baseband processors are to generate a handover request acknowledge message for the source eNB, including information whether a RACH-less handover should be applied, and wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • the apparatus may include the subject matter of example six or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via an indicator in the handover request acknowledge message.
  • the apparatus may include the subject matter of example six or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an absence of a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • the apparatus may include the subject matter of example six or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an indicator in the handover request acknowledge message.
  • the apparatus may include the subject matter of example six or any of the examples described herein, wherein the handover request message or the handover request acknowledge message, or a combination thereof, are sent via X2 signaling.
  • one or more machine readable media have instructions thereon that, if executed by an apparatus of a source evolved Node B (eNB) to perform a handover of a user equipment (UE) to a target eNB, result in generating a handover request message for the target eNB, wherein the handover request message indicates a RACH-less handover is to be used, and to process a handover request acknowledge message from the target eNB 112, storing the handover request acknowledge message in a memory, and determining if a RACH-less handover should be applied based at least in part on the handover acknowledge message, wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • eNB source evolved Node B
  • UE user equipment
  • the one or more machine readable media have instructions stored thereon that, if executed, may result in the subject matter of example eleven or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via an indicator in the handover request acknowledge message.
  • the one or more machine readable media have instructions stored thereon that, if executed, may result in the subject matter of example eleven or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an absence of a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • the one or more machine readable media have instructions stored thereon that, if executed, may result in the subject matter of example eleven or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an indicator in the handover request acknowledge message.
  • the one or more machine readable media have instructions stored thereon that, if executed, may result in the subject matter of example eleven or any of the examples described herein, wherein the handover request message or the handover request acknowledge message, or a combination thereof, are sent via X2 signaling.
  • one or more machine readable media having instructions thereon that, if executed by an apparatus a target evolved Node B (eNB) to perform a handover of a user equipment (UE) from a source eNB, result in processing a handover request message from the source eNB, wherein the handover request message indicates a RACH-less handover is to be used, storing the handover request message in a memory, and generating a handover request acknowledge message for the source eNB, including information whether a RACH-less handover should be applied, wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • eNB target evolved Node B
  • UE user equipment
  • the one or more machine readable media have instructions stored thereon that, if executed, may result in the subject matter of example sixteen or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH- less handover via an indicator in the handover request acknowledge message.
  • the one or more machine readable media have instructions stored thereon that, if executed, may result in the subject matter of example sixteen or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an absence of a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • the one or more machine readable media have instructions stored thereon that, if executed, may result in the subject matter of example sixteen or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an indicator in the handover request acknowledge message.
  • the one or more machine readable media have instructions stored thereon that, if executed, may result in the subject matter of example sixteen or any of the examples described herein, wherein the handover request message or the handover request acknowledge message, or a combination thereof, are sent via X2 signaling.
  • an apparatus of a source evolved Node B (eNB) to perform a handover of a user equipment (UE) to a target eNB comprises means for generating a handover request message for the target eNB, wherein the handover request message indicates a RACH- less handover is to be used, and to process a handover request acknowledge message from the target eNB, means for storing the handover request acknowledge message in a memory, and means for determining if a RACH-less handover should be applied based at least in part on the handover acknowledge message, wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • eNB source evolved Node B
  • the apparatus may include the subject matter of example twenty-one or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via an indicator in the handover request acknowledge message.
  • the apparatus may include the subject matter of example twenty-one or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an absence of a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • the apparatus may include the subject matter of example twenty-one or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an indicator in the handover request acknowledge message.
  • the apparatus may include the subject matter of example twenty-one or any of the examples described herein, wherein the handover request message or the handover request acknowledge message, or a combination thereof, are sent via X2 signaling.
  • an apparatus a target evolved Node B (eNB) to perform a handover of a user equipment (UE) from a source eNB comprises means for processing a handover request message from the source eNB, wherein the handover request message indicates a RACH-less handover is to be used, means for storing the handover request message in a memory, and means for generating a handover request acknowledge message for the source eNB, including information whether a RACH-less handover should be applied, wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • eNB evolved Node B
  • the apparatus may include the subject matter of example twenty-six or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB is capable of a RACH-less handover via an indicator in the handover request acknowledge message.
  • the apparatus may include the subject matter of example twenty- six or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an absence of a periodic uplink grant in mobility control information in the handover request acknowledge message.
  • the apparatus may include the subject matter of example twenty-six or any of the examples described herein, wherein the handover request acknowledge message indicates that the target eNB has rejected the RACH-less handover via an indicator in the handover request acknowledge message.
  • the apparatus may include the subject matter of example twenty-six or any of the examples described herein, wherein the handover request message or the handover request acknowledge message, or a combination thereof, are sent via X2 signaling.
  • machine-readable storage includes machine-readable instructions, when executed, to realize an apparatus as claimed in any preceding claim.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

En résumé, selon un ou plusieurs modes de réalisation, un appareil d'un nœud B évolué (eNB) source pour effectuer un transfert d'un équipement utilisateur (UE) vers un eNB cible comprend un ou plusieurs processeurs de bande de base pour générer un message de requête de transfert pour l'eNB cible, le message de requête de transfert indiquant qu'un transfert sans RACH doit être utilisé, et pour traiter un message d'accusé de réception de requête de transfert provenant de l'eNB cible, et une mémoire pour stocker le message d'accusé de réception de requête de transfert. Le ou les processeurs de bande de base déterminent si un transfert sans RACH devrait être appliqué sur la base, au moins en partie, du message d'accusé de réception de transfert, et le message d'accusé de réception de requête de transfert indique que l'eNB cible est capable d'un transfert sans RACH par l'intermédiaire d'une autorisation de liaison montante périodique dans des informations de commande de mobilité dans le message d'accusé de réception de requête de transfert.
PCT/US2017/035736 2016-08-09 2017-06-02 Support x2 pour mobilité améliorée (emob) Ceased WO2018031110A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
DE112017004034.5T DE112017004034T5 (de) 2016-08-09 2017-06-02 X2 support für verbesserte mobilität (emob)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662372501P 2016-08-09 2016-08-09
US62/372,501 2016-08-09

Publications (1)

Publication Number Publication Date
WO2018031110A1 true WO2018031110A1 (fr) 2018-02-15

Family

ID=59054313

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/035736 Ceased WO2018031110A1 (fr) 2016-08-09 2017-06-02 Support x2 pour mobilité améliorée (emob)

Country Status (2)

Country Link
DE (1) DE112017004034T5 (fr)
WO (1) WO2018031110A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020167230A1 (fr) * 2019-02-14 2020-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Nœud d'accès source, nœud d'accès cible, et procédés pour un transfert amélioré
WO2021021440A1 (fr) * 2019-07-30 2021-02-04 Qualcomm Incorporated Multiplexage par répartition dans le temps de communications en liaison montante pendant un transfert intercellulaire à fermeture avant ouverture
CN113632538A (zh) * 2019-02-13 2021-11-09 瑞典爱立信有限公司 用于无随机接入信道切换/辅小区组变更的对齐配置
CN113826438A (zh) * 2019-04-26 2021-12-21 上海诺基亚贝尔股份有限公司 随机接入过程
CN114245999A (zh) * 2019-08-16 2022-03-25 苹果公司 无线电蜂窝系统中的小区切换
US20220124645A1 (en) * 2019-08-05 2022-04-21 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Wireless communication method, terminal device, and network device
US20230092054A1 (en) * 2020-05-30 2023-03-23 Huawei Technologies Co., Ltd. Communication method and apparatus

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015127987A1 (fr) * 2014-02-28 2015-09-03 Nokia Solutions And Networks Oy Techniques permettant un transfert intercellulaire synchronisé avec moins de canaux d'accès aléatoire (rach) pour des réseaux sans fil
WO2016031779A1 (fr) * 2014-08-28 2016-03-03 株式会社Ｎｔｔドコモ Station de base et dispositif d'utilisateur

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015127987A1 (fr) * 2014-02-28 2015-09-03 Nokia Solutions And Networks Oy Techniques permettant un transfert intercellulaire synchronisé avec moins de canaux d'accès aléatoire (rach) pour des réseaux sans fil
WO2016031779A1 (fr) * 2014-08-28 2016-03-03 株式会社Ｎｔｔドコモ Station de base et dispositif d'utilisateur
US20160381611A1 (en) * 2014-08-28 2016-12-29 Ntt Docomo, Inc. Base station and user equipment

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12047828B2 (en) 2019-02-13 2024-07-23 Telefonaktiebolaget Lm Ericsson (Publ) Aligned configuration for random access channel-less handover/secondary cell group change
CN113632538A (zh) * 2019-02-13 2021-11-09 瑞典爱立信有限公司 用于无随机接入信道切换/辅小区组变更的对齐配置
JP7275292B2 (ja) 2019-02-14 2023-05-17 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ソースアクセスノード、ターゲットアクセスノード、および拡張ハンドオーバの方法
WO2020167230A1 (fr) * 2019-02-14 2020-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Nœud d'accès source, nœud d'accès cible, et procédés pour un transfert amélioré
US11818611B2 (en) 2019-02-14 2023-11-14 Telefonaktiebolaget Lm Ericsson (Publ) Source access node, target access node and methods for enhanced handover
JP2022521074A (ja) * 2019-02-14 2022-04-05 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ソースアクセスノード、ターゲットアクセスノード、および拡張ハンドオーバの方法
CN113826438A (zh) * 2019-04-26 2021-12-21 上海诺基亚贝尔股份有限公司 随机接入过程
US11895694B2 (en) 2019-07-30 2024-02-06 Qualcomm Incorporated Time-division multiplexing of uplink communications during make-before-break handover
WO2021021440A1 (fr) * 2019-07-30 2021-02-04 Qualcomm Incorporated Multiplexage par répartition dans le temps de communications en liaison montante pendant un transfert intercellulaire à fermeture avant ouverture
US12289757B2 (en) 2019-07-30 2025-04-29 Qualcomm Incorporated Time-division multiplexing of uplink communications during make-before-break handover
US20220124645A1 (en) * 2019-08-05 2022-04-21 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Wireless communication method, terminal device, and network device
US12010636B2 (en) * 2019-08-05 2024-06-11 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Wireless communication method, terminal device, and network device
CN114245999A (zh) * 2019-08-16 2022-03-25 苹果公司 无线电蜂窝系统中的小区切换
US20230092054A1 (en) * 2020-05-30 2023-03-23 Huawei Technologies Co., Ltd. Communication method and apparatus

Also Published As

Publication number Publication date
DE112017004034T5 (de) 2019-06-13

Similar Documents

Publication Publication Date Title
EP3923631B1 (fr) Systèmes et procédés pour réduire des interruptions dans des transmissions de données en raison d'opérations de transfert intercellulaire
CN108702673B (zh) 用于减少由于切换操作而导致的数据传输中断的系统和方法
US9894702B2 (en) Performing primary cell functions in a secondary cell
WO2018031110A1 (fr) Support x2 pour mobilité améliorée (emob)
CN108307681B (zh) 频率间公共陆地移动网络(plmn)间发现
WO2018085049A1 (fr) Systèmes, procédés et dispositifs de transfert intercellulaire à établissement avant rupture et reconfiguration de groupe de cellules secondaires
TW201703579A (zh) 用於長期演進／無線區域網路聚合之無線區域網路行動
JP7669530B2 (ja) 非地上系ネットワーク（ｎｔｎ）におけるビーム障害回復タイミング
TWI821153B (zh) 移動性增強及可穿戴裝置路徑選擇之裝置及方法
TW201729576A (zh) 在通透模式中的封包資料收斂協定(pdcp)操作技術
US12336017B2 (en) Channel state information reference signal (CSI-RS) based contention free random access (CFRA) in radio resource management (RRM)
TW201728126A (zh) 用於軟體定義無線電存取網路的行動管理
US20250331032A1 (en) Systems, methods, and devices for ul timing advance acquisition and update in a wireless communication network
CN116097818B (zh) 用于基站（bs）在无线电资源控制（rrc）连接中的测量增强
CN116097700B (zh) 用于用户装备（ue）在无线电资源控制（rrc）连接中的测量增强
WO2023044824A1 (fr) Intervalle de mesure (mg) et conception d'interruption pour lecture d'informations de système (si) dans un module d'identité d'abonné universel multiple (musim)
US10448237B2 (en) RRM requirement for D2D inter-carrier discovery gap
CN117917135A (zh) 用于在混合流量中进行功率控制和波束选择的系统、方法和设备
HK40059958A (en) Systems and methods for reducing interruptions in data transmissions due to handover operations
CN119138030A (zh) 用于增强型短数据发送（sdt）的系统、方法和设备
CN119908080A (zh) 用于控制链路和回传链路波束的系统、方法和设备
HK1256563B (en) Inter-frequency inter-public land mobile network (plmn) discovery
HK1252887B (zh) 用於在多模操作中注册电路交换(cs)服务的方法和用户设备(ue)

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

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17729716

Country of ref document: EP

Kind code of ref document: A1