DE112017004789T5 - Make-before-break delivery and secondary cell group reconfiguration systems, methods and devices - Google Patents

Abstract

A make-before-break handover procedure can reduce the interruption time of an intra-frequency handover. A user equipment may continue uplink (UL) transmission and downlink (DL) reception with the source cell until initiation of radio frequency (RF) re-tuning of the UE for connection to the destination cell. The UE may autonomously select a time to stop the UL transmission and the DL reception of the UE with the source cell to initiate the RF retune. After the UL transmission and the DL reception of the UE stop with the source cell, the UE may perform a second part of the handover procedure for connecting to the target cell.

Description

Related applications

This application claims the benefit of the provisional U.S. Patent Application No. 62 / 417,701 filed November 4, 2016, which is hereby incorporated by reference in its entirety.

Technical area

This disclosure relates to wireless communication networks. More particularly, this disclosure relates to make-before-break handover and make-before-break secondary cell group re-configuration in wireless communication systems.

General state of the art

The wireless mobile communication technology uses various standards and protocols for communicating data between a base station and a wireless mobile device. Wireless communication system standards and protocols may include the Long-Term Evolution (LTE) of the 3rd Generation Partnership Project (3GPP); the IEEE (Institute for Electrical and Electronics Engineers) 802.16 standard, which is commonly known to industry groups as Worldwide Interoperability for Microwave Access (WiMAX); and the IEEE 802.11 wireless local area network (WLAN) standard, which is commonly known to industry groups as Wi-Fi. In 3GPP radio access networks (RANs) in LTE systems, the base station may have a RAN node, such as an Evolved Universal Terrestrial Radio Access Network (ETRT) node B (also commonly as an evolved node B (evolved node B ), improved node B (enhanced node B , eNodeB or eNB) and / or radio network controller (RNC) in an E-UTRAN communicating with a wireless communication device known as User Equipment (UE). In fifth-generation (5G) wireless RANs, the RAN nodes can connect a 5G node (gNB or Neufunk node B (NR NB, New Radio Node B)).

The RANs use radio access technology (RAT) technology to communicate between the RAN node and the UE. RANs can be GSM (Global System for Mobile Communications), EDGE (Enhanced Data Rates for GSM Evolution), RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Universal Terrestrial Radio Access Network (UTRAN) ) and / or E-UTRAN, which provide access to communication services through a core network. Each of the RANs works according to a specific 3GPP RAT. For example, the GERAN implements GSM and / or EDGE RAT, implements the UTRAN UMTS (Universal Mobile Telecommunication System) RAT or other 3GPP RAT, and implements the E-UTRAN LTE RAT.

A core network may be connected to the UE through the RAN node. The core network may include a service gateway (SGW), a packet data network (PDN) gateway (PGW), an access network detection and selection function (ANDSF) server, enhanced packet data Gateway (ePDG, Enhanced Packet Data Gateway) and / or Mobility Management Entity (MME).

list of figures

• 1 FIG. 12 illustrates a flowchart of a method according to certain embodiments for a UE to make a make-before-break handover when a UE radio frequency (RF) re-tuning occurs.
• 2 FIG. 12 illustrates a flowchart of a method according to certain embodiments for a eNB to make a make-before-break handover where a UE-RF re-vote can occur.
• 3 FIG. 12 illustrates a flowchart of a method according to certain embodiments of a message flow associated with handing over a UE from a source cell to a target cell in LTE.
• 4 FIG. 12 illustrates a flowchart of a method according to certain embodiments of an intra-MME / service gateway handover.
• 5 illustrates an architecture of a system of a network according to some embodiments.
• 6 illustrates example components of a device according to some embodiments.
• 7 FIG. 10 illustrates exemplary interfaces of the baseband circuitry according to some embodiments. FIG.
• 8th FIG. 12 is a block diagram illustrating components according to some exemplary ones. FIG Embodiments illustrate that are capable of reading instructions from a machine-readable or computer-readable medium and performing one or more of the methodologies discussed herein.

Detailed description

One goal for cellular technology is to improve mobility and reduce or minimize the length of a data service interruption during handover to meet ever-increasing expectations of the end-user experience. The make-before-break handover and the RACHlose handover (HO, handover) should help with these goals. The RACHlose handover assumes that a Random Access (RA) method may be omitted from the target cell (s), which may result in minimizing data interception time. Another possibility is to continue the transmission to and reception from the source cell as long as no new radio connection is established at the target cell. Such an approach is often referred to as make-before-break handover.

There may be some interruption during the transmission, even with efforts to reduce or minimize the interruption. For example, a handover may introduce a handover delay and a break time. A handover delay includes a radio resource control (RRC) method delay and a handover processing time. An interruption time may occur, for example, when a user equipment (UE) receives a handover command from a source cell requiring retuning. Re-tuning may interrupt data transmission or reception.

To minimize the impact of the interruption, make-before-break intra-frequency handovers may require a handoff delay and a break time. In some implementations, a handover delay requirement may indicate that when the UE receives an RRC message that implies a handover, the UE is ready to transmit the new Physical Random Access Channel (PRACH) within the D-Handoff Seconds after the end of the Transmission Time Interval (TTI) including the RRC command. In some implementations, the D-commit corresponds to the maximum RRC process delay plus the handoff processing time (eg, T-handoff as with certain handoff methods). An interruption time requirement can take into account handover cases with bandwidth change and without bandwidth change. In some embodiments, the requirements regarding the interruption time could be general for the handover cases with or without bandwidth change.

Certain embodiments discussed herein relate to a make-before-break operation when the bandwidths of the source and destination evolved node B (eNB) are different. These embodiments may reduce or minimize the interrupt time, handover delay, and / or effects of these interrupts.

Certain embodiments discussed herein are applicable to intra-frequency handover and Secondary Cell Group (SCG) handover. Thus, in one embodiment, when intra-frequency handoffs are discussed, it will be understood that the same principles can be applied to an SCG handoff, and vice versa. A secondary cell group is the subset of serving cells that are not part of the master cell group (MCG). A primary secondary cell is an SCG cell in which the UE is instructed to perform a random access or an initial PUSCH transmission if a random access method is skipped when performing an SCG interchange procedure.

In a make-before-break embodiment, a UE continues a downlink and an uplink with the source cell until the UE performs an RF vote on a target cell. In such an embodiment, the UE stops communicating with the source cell when the UE makes radio (RF) settings for the destination source. In case the same bandwidth is used for both the source and the destination cells, the UE will stop communicating with the source cell if it is ready for a first PUSCH or PRACH transmission.

In another make-before-break embodiment, it is up to the UE implementation to decide when to stop communicating with the source cell if the bandwidths of the source and destination cells are different.

Additional details and examples are provided with reference to the following figures. The embodiments of the disclosure may be understood by reference to the drawings, wherein like parts are designated by like reference numerals throughout. The components of the disclosed embodiments, as generally described and illustrated in the figures herein, could be arranged in a wide variety of different configurations be designated. Thus, the following detailed description of the embodiments of the systems and methods of the disclosure is not intended to limit the scope of the disclosure as claimed, but is only representative of possible embodiments.

1 illustrates a flowchart of a method 100 according to certain embodiments for a UE to make a make-before-break handler, if one UE RF re-voting takes place. The illustrated method 100 For example, provides UE make-before-break handoff procedures when the UE camps in a target cell in scenarios where the bandwidth of the target cell is not the same as a source cell.

A UE may be a memory interface for storage or retrieval 102 from a storage device of an RRC connection reconfiguration message from a source cell in a wireless network. The RRC connection reconfiguration message is the command to modify an RRC connection. It can include measurement configuration, mobility control, and radio resource configuration information (including Radio Bearers (RBs), Medium Access Control (MAC) Master Configuration, and Physical Channel Configuration), including any associated Non-Access Stratum dedicated (NAS) information and security configuration to transfer.

In certain embodiments, a baseband processor of the UE decodes the RRC connection reconfiguration message to obtain mobility control information items 104 , The mobility controls may include network-controlled mobility parameters of the UE to the wireless network or within the wireless network. In some embodiments, the mobility controls may include indications of make-before-break configuration, RACH configuration, and / or bandwidth changes between cells.

In response to the mobility control information item, the baseband processor initiates 106 a handoff procedure from the source cell to a target cell. A first part of the surrender procedure concludes a provision 108 whether make-before-break handoff is configured. This can be done if Make-before-break is configured UE start syncing with the downlink of a target cell. If in the make-before-break transfer solution the UE If there is no RF re-tuning, the UE continues the downlink and uplink with the source cell until the UE performs the first transmission through a shared physical uplink channel (PUSCH) or PRACH to the destination eNB.

If that UE Performing the RF retuning to camp in the target cell, the handover procedure can be done in part before and after that UE the uplink transmission / downlink reception with the source cell (s) stops. The handover may include a MAC reset after the UE stops the uplink transmission / downlink reception with the source cell (s).

If it is determined 108 that make-before-break is not configured, the UE may perform a second part of the handover procedure 124 to connect to the target cell based on the configured handover procedure. If it is determined 108 in that make-before-break is configured, the baseband processor can control the UE 110 to continue the uplink (UL) transmission and the downlink (DL) reception with the source cell until initiation of the RF re-tuning of the UE for connection to the target cell.

In some embodiments, the mobility control information element further comprises a random access channel (RACH) skip parameter to indicate whether a random access method for a target primary cell (PCell) is skipped. Thus, the baseband processor can also determine 112 whether the RACH skip parameter is configured. The RACH skip parameter indicates whether the UE is continuing the uplink transmission / downlink reception with the source cell (s) before the first transmission through the PRACH to the destination PCell or through the PUSCH to the destination PCell is carried out. The RACH-Iose solution and maintaining a connection with the source eNB (eg, make-before-break) can be considered as two independent mechanisms whose activation depends on the decision of the network. The two solutions can be activated simultaneously.

Based on the RACH determination, the baseband processor continues UL transmission and DL reception with the source cell prior to transmission through various channels. For example, if the RACH skip parameter is not configured, the baseband processor may continue UL transmission and DL reception with the source cell prior to transmission through a PRACH to the destination Pcell 114 , If the RACH skip parameter is configured, the baseband processor may continue UL transmission and DL reception with the source cell prior to transmission through a PUSCH to the destination Pcell 116 ,

The baseband processor may further determine 118 whether the source cell and the target cell have different bandwidths. If the source cell and the target cell do not have different bandwidths The baseband processor may perform a second part of the handover procedure for connecting to the target cell as a typical make-before-break process 124 ,

However, if determined 118 that the source cell and the target cell have different bandwidths, a typical make-before-break handover process would fail. For example, a typical make-before-break handover process may wait to suspend UL transmission and DL reception with the source cell until a connection to the target cell is established and the source cell establishes the UE instructs to separate. This is during the re-vote UE however, you may not be able to communicate with the source cell. Thus, the source cell may not be able to do this UE to instruct when to stop the UL transmission and the DL reception.

To address this, the baseband processor autonomously selects a time 120 to the UL transmission and the DL reception of the UE to stop with the source cell if it is determined 118 in that the source cell and the target cell have different bandwidths. In some embodiments, the baseband processor is configured to select the time to stop the UL transmission and the DL reception of the UE with the source cell based on the determination that the source cell and the destination cell have different bandwidths. In other words, it depends on the implementation of the UE when the uplink transmission / downlink reception with the source cell (s) should be stopped in order to initiate the retune for connection to the target cell.

After the UL transmission and the DL reception are stopped, the UE starts the retuning 122 to cause the UE to cover the bandwidth of the target cell. The timing for stopping the transmission and reception of the UE with the source cell to initiate RF retuning may be selected to reduce the service interruption. For example, in some embodiments, the UE continues the downlink and the uplink with the source cell until a known or selected set of data has been communicated. In some embodiments, it depends on the implementation of the UE when the data from the source cell is stopped when the bandwidths of the source cell and destination cell are different.

The bandwidth of the target cell can be determined either by the UE be determined or obtained from the source cell. For example, the source cell may transmit the bandwidth of the destination cell in the mobility control information element. In some embodiments, the UE will sample the bandwidth to determine the bandwidth of the target cell.

After the UL transmission and the DL reception of the UE with the source cell stops, the baseband processor performs a second part of the handoff procedure for connecting to the target cell 124 , The second part of the handover procedure may include a medium access control (MAC) reset after the UE stops UL transmission and DL reception with the source cell.

In some embodiments, the UE is configured for dual connectivity. In dual-connectivity embodiments, the baseband processor may determine that the RRC connection reconfiguration message has a secondary cell group (SCG) reconfiguration parameter. In response to the SCG reconfiguration parameter, the baseband processor starts synchronization with a DL a primary target secondary cell (PSCell) in the first part of the handover procedure. When a make-before-break SCG parameter is configured, the baseband processor performs at least part of an SCG reconfiguration procedure after the UL transmission and the DL reception of the UE stop with the source cell.

In addition, the control information element may further include a random access channel (RACH) skip SCG parameter to indicate whether a random access procedure for the target PSCell is skipped. In some embodiments, the baseband processor is further configured to, in response to determining that the make-before-break SCG parameter is configured to control the UE, perform the UL transmission and the DL reception with the source cell Transmission by a PRACH to the target PSCell if the RACH skip parameter is not configured, or to continue by a PUSCH to the target PSCell if the RACH skip parameter is configured.

2 illustrates a flowchart of a method 200 according to certain embodiments, for an eNB to perform a make-before-break handover where a UE-RF re-vote can occur. This method 200 can be used regardless of whether the RF re-tuning is needed or not.

An eNB receives measurement reports from a UE 202 , The eNB determines, based at least in part on a measurement report from an UE, to submit the UE to a destination eNB 204 , For example, the UE measurement reports may indicate that a target cell has a stronger signal at the location of the UE than a source cell, and determines the target cell that UE to pass to the cell with the stronger signal.

The eNB generates a handover request message for the destination eNB 206 , The handover request message passes information to the destination eNB to prepare for the handover on the destination page. For example, the handover request message may be a UE X2 Signaling context reference at the source eNB, a UE S1 EPC signaling context reference, a destination cell ID, an eNB handover transition key (KeNB *), RRC context including the C-RNTI of the UE in the source eNB, AS configuration, E-RAB context, and physical layer ID source cell + short MAC-I for possible radio link failure (RLF) fixes. UE X2 - or UE S1 Signaling references allow the destination eNB to address the source eNB and EPC. The E-RAB context includes RNL (Radio Network Layer) and Transport Network Layer (TNL) addressing information and QoS profiles of E-RABs.

The eNB processes a handover request acknowledgment message from the destination eNB in response to the handover request message 208 , The handoff request may include information for forwarding to the UE in a Radio Resource Control (RRC) message. In some embodiments, the handover request acknowledgment message comprises a transparent container to be sent to the UE as an RRC message for performing the handover. The container may include a new C-RNTI, target eNB security algorithm identifiers for the selected security algorithms, a dedicated RACH preamble, and possibly some other parameters, ie, access parameters, SIBs, and so forth. When a RACH-Iose handover is configured, the container may include a time setting indication and optionally a pre-assigned uplink permission. The handover request acknowledgment message may also include RNL / TNL information for the routing tunnels, if necessary.

The eNB generates the RRC message to configure the UE for make-before-break handover 210 , The eNB maintains a connection with the UE to allow Uplink (UL) and downlink (DL) communication with the UE during the make-before-break handover to the destination eNB without expectation 212 , For example, if RF tuning is performed by the UE, the eNB would continue to allow UL and DL communication, even if the UE could already have stopped communicating to tune. As another example, prior to a commit command, the eNB may configure certain reference signal monitoring for the UE (eg, probe reference signals or other reference signals). However, after configuring a make before break handoff, the eNB may receive probing or other feedback from the UE or not, because the UE autonomously decides when to stop communicating with the eNB to perform the RF re-tuning. Thus, the eNB may not be waiting for an answer or feedback that might otherwise be expected.

The eNB processes a UE context release message from the destination eNB to indicate the make-before-break handover success and to release resources associated with the UE 214 , This may not release the communication resources before the handover is complete. By sending the UE context release message, the destination eNB acknowledges the success of the handover to the source eNB and triggers the release of resources by the source eNB. In some embodiments, the eNB sends this message after receiving a PATH REVERSE CONFIRMATION message from the MME. Upon receiving the UE context release message, the source eNB may release resources related to radio and C-level associated with the UE context. Any continuous data forwarding can be continued.

3 illustrates a flowchart of a method 300 according to certain embodiments of a message flow that involves handing over a UE 302 from a source cell 304 to a target cell 306 is linked. In LTE systems, the handoff is a network-controlled, UE-assisted method, where the role of the UE is typically limited to performing measurements on adjacent E-UTRAN cells or frequencies. In addition, in the embodiments disclosed herein, the UE may additionally autonomously select a time to perform the UL transmission and the DL reception of the UE with the source cell to initiate the RF retune if a source eNB has a different bandwidth than a destination eNB has to stop.

As in 3 shown, the UE 302 packet data 307 with the source cell 304 communicate. After receiving a measurement report 308 from the UE 302 triggers the source cell 304 or a source eNB performs a handover preparation phase. For example, the source cell 304 via the X2 interface with the target cell 306 (or more precisely: the eNB in the case of an IntereNB transfer). The target cell 306 receives a transfer request 310 and respond positively (in the event that it is feasible to accommodate the additional user) by sending a handover request acknowledgment 312 to the source cell 304 , This in turn calls a submit command 314 from the source cell 304 to the UE 302 is sent. This time can mark the beginning of the handover execution phase.

For some transfers, the receipt of the submit command indicates 314 (ie, the RRC connection reconfiguration including the MobilityControllnfo information element) explicitly indicates the beginning of a data service interruption period. The UE 302 That is, discards the protocol stack that is with the source cell 304 and starts actions to synchronize with the target cell 306 while the source cell 304 a data forwarding 320 (eg for one or more data radio bearers) to the target cell 306 initiated. The data service interruption lasts as long as the RRC connection reconfiguration completion message 322 not correct from the target cell 306 is obtained. After receiving the handover message, the UE 302 try on the target cell 306 at the first available RACH opportunity according to random access resource selection (eg, by sending a random access preamble 324 and receiving a random access response 326 ) or at the first available PUSCH opportunity when RACH skipping is configured to access. Upon successful completion of the handover, the UE sends 302 A message "Passing Complete" (for example, the message "RRC Connection Reconfiguration Complete." 322 ) to the target cell 306 , The target cell 306 informs the source cell 304 on successful handover with a UE context release message 328 ,

In a make-before-break handover method according to certain embodiments disclosed herein, the UE performs 302 however, the downlink and the uplink of the packet data 318 with the source cell 304 continue until the UE 302 performs a first transmission through the PUSCH or the PRACH to the destination eNB. If the RF re-tuning is necessary, the UE selects 302 autonomously a time to stop the UL transmission and the DL reception of the UE 302 with the source cell 304 to initiate the RF retuning.

In one embodiment, a UE configured for dual connectivity, initiating a secondary cell group (SCG) reconfiguration process, and determining that the UE is configured for make before break SCG reconfiguration. In response to the determination, the UE syncing with a DL start a PSCell. The UE can perform at least part of the SCG reconfiguration procedure after the UE the UL transmission and DL reception with one or more source cells stops. For example, the UE may perform an SCG MAC reset after the UE the UL transmission and the DL reception with the one or more source cells stops.

In some embodiments, this selects UE autonomously a time to stop the UL transmission and the DL reception of the UE with the source cell for initiating the RF retune to connect to a target cell. The selected time to stop the UL transmission and receive the DL UE with the one or more source cells may be based on reducing the service interruption to a determination that the source cell and the target PSCell are communicating with the UE using different bandwidths.

The UE may decode an RRC connection reconfiguration message from a master evolved node B (MeNB) to obtain an SCG mobility control information parameter, and initiate the SCG reconfiguration procedure in response to the SCG mobility control information parameter and the SCG make-before-break parameter , In some embodiments, the UE also obtains an SCG make-before-break parameter based on the RRC connection reconfiguration message that is set to indicate that the UE is configured for make-before-break SCG reconfiguration.

In some embodiments, the UE obtains a random access channel (RACH) skip SCG parameter based on the RRC connection reconfiguration message to indicate whether a random access procedure for the target PSCell is skipped. In response to a determination that the make-before-break SCG parameter is configured, the UE may continue the UL transmission and the DL reception with the one or more source cells prior to transmission. For example, if the RACH skip SCG parameter is not configured, this will result UE the UL transmission and the DL reception with a PRACH to the destination PSCell through; and if the RACH skip SCG parameter is configured, the UE continues the UL transmission and the DL reception with a PUSCH to the target PSCell.

The following description provides non-limiting examples of transmission embodiments. At RRC_CONNECTED, the network controls the UE mobility; d. that is, the network decides when the UE connects to which E-UTRA cell (s) or inter-RAT cell. For network-controlled mobility at RRC_CONNECTED, the PCell can be switched using a message "RRC connection reconfiguration" including mobilityControlnfo (handover), while the SCell (s) are switched using either the "RRC connection reconfiguration" message with or without the mobilityControlnfo can / can.

It can set up an SCG using a "RRC connection reconfiguration" message with or without the mobilityControlnfo. be reconfigured or released. In the event that a direct access to the PSCell or an initial PUSCH to the PSCell when RACH skip SCG is configured is required in the SCG reconfiguration, the E-UTRAN will employ the SCG toggle (ie, a Message "RRC Connection Reconfiguration" including the mobilityControlnfoSCG). The PSCell can only be changed in certain embodiments using the SCG interchange method and by releasing and adding the PSCell.

The network solves the transfer procedure z. B. based on radio conditions, load, off. To enable this, the network may configure the UE to perform measurement reporting (possibly including the configuration of measurement gaps). The network can also blind the transfer, d. h., without having received measurement reports from the UE.

Prior to sending the handover message to the UE, the source eNB prepares one or more destination cells. The source eNB selects the destination PCell. The source eNB may also provide the destination eNB with a list of best cells on each frequency for which measurement information is available, in descending order of the received reference signal power (RSRP). The source eNB may also have available measurement information for the cells provided in the list. The target eNB decides which SCells will be configured for use after handover, which may include cells other than those specified by the source eNB. If an SCG is configured, the handover involves either an SCG release or an SCG change. In the event that the UE has been configured with DC, the destination eNB indicates in the commit message whether the UE can release the entire SCG configuration. After the connection rebuild, the UE releases the entire SCG configuration except for the data radio bearer (DRB) configuration, while the E-UTRAN in the first reconfiguration message following the recovery either releases the DRB (s). or reconfigures the DRB (s) to the MCG DRB (s).

The destination eNB generates the message that is used to perform the handoff, i. that is, the message having the AS configuration to be used in the target cell (s). The source eNB forwards the handover message / information received from the destination transparently (i.e., without changing values / content) to the UE. If appropriate, the source eNB may initiate data forwarding for the DRBs (a subset thereof).

After receiving the handover message, the UE attempts to access the target PCell on the first available RACH opportunity according to the random access resource selection defined in TS 36.321; that is, the handoff is asynchronous or at the first available PUSCH opportunity when RACH skip is configured. Thus, when a dedicated preamble is assigned for random access in the destination PCell, the E-UTRA is configured to retrieve it based on the first RACH opportunity that the UE can use to make available. Upon successful completion of the handover, the UE sends a message that is used to confirm the handover.

When the destination eNB releases the RRC protocol using the source eNB UE If not configured, the target eNB may not be able to understand the UE configuration provided by the source eNB. In this case, the destination eNB should use the full configuration option to do this UE to reconfigure for handover and recovery. The full configuration option includes an initialization of the radio configuration, which makes the method independent of the configuration used in the source cell (s), with the exception that the security algorithms for RRC recovery are continued.

Upon successful completion of the handover, PDCP SDUs may be forwarded in the target cell (s). In certain embodiments, this only applies to DRBs that use the RLC-AM mode and to handovers that do not include the full configuration option. Upon successful completion of the handover, which does not include the full configuration option, the SN and Hyper Frame Number (HFN) except the DRBs that use the RLC-AM mode (for which both the SN as well as the HFN persist) reset. For reconfigurations that include the full configuration option, the PDCP entities (the SN and HFN do not persist) are restored to the DRBs regardless of the RLC mode. Further details are specified in TS 36.323.

4 illustrates an exemplary flowchart of a method 400 according to certain embodiments of an intra-MME / service gateway handover. The figure is provided by way of example only and represents the basic handover scenario where neither the MME 408 still the service gateway 410 to change.

In the illustrated embodiment, the preparation and execution phase of the handover procedure is without the involvement of a advanced packet core (EPC, Evolved Packet Core); ie, preparation messages are sent directly between the eNBs 404 . 406 replaced. The release of resources at the source side during the handover completion phase is done by the source eNB 404 triggered. In the event that a forwarding node ( RN , Relay Node), its donor eNB (DeNB, Donor eNB) derives the appropriate S1 Messages between the RN and the MME 408 ( S1 -based transfer) and X2 Messages between the RN and the target eNB 406 ( X2 -based delivery); the DeNB is explicitly aware of a UE associated with the RN due to the S1 Proxy and X2 Proxy functionality.

The UE context 412 within the source eNB 404 Contains information regarding roaming and access restrictions provided by either the connection setup or the last timing advance (TA) update. The source eNB 404 configures the UE measurement methods in accordance with the roaming and access restriction information, and e.g. The available multiple frequency band information. The measurements 414 that from the source eNB 404 can be provided that support the connection mobility of the UE 402 controls. A measurement report 416 is thrown and to the source eNB 404 Posted.

The source eNB 404 make a handover decision 418 based on the measurement report 416 and radio resource management (RRM) information for passing the UE 402 , The source eNB 404 gives a message "transfer request" 420 to the target eNB 406 out the information for preparing the handover at the target eNB 406 (eg UE X2 Signaling context reference at the source eNB, UE S1 EPC signaling context reference, destination cell ID, KeNB * RRC context including the UE's C-RNTI in the source eNB, AS configuration, E-RAB context, and source cell physical layer ID + short MAC-I for possible RLF fix). The UE X2 / UE S1 Signaling references enable the target eNB 406 , the source eNB 404 and to address the EPC. The E-RAB context has RNL and TNL addressing information and QoS profiles of the E-RABs.

The admission control 422 can from the target eNB 406 depending on the received E-RAB QoS information to increase the likelihood of a successful handover when the resources from the target eNB 406 can be granted. The target eNB 406 configures the resources according to the obtained E-RAB QoS information and reserves a C-RNTI and optionally a RACH preamble. The AS configuration to be used at the target cell can be either independent (ie, a "setup") or as a delta compared to the AS configuration used in the source cell (ie, a "reconfiguration") to be specified.

The target eNB 406 prepares the handover L1 / L2 and sends the message TRANSFER REFUND 424 to the source eNB 404 , The message TRANSFER CONFIRMATION 424 has a transparent container leading to the UE 402 is to be sent as an RRC message to perform the handover. The container has a new C-RNTI and security algorithm identifiers of the target eNB 406 for the selected security algorithms and may have a dedicated RACH preamble and possibly some other parameters, ie access parameters, SIBs, etc. When a RACH-Iose handover is configured, the container has a time setting indication and optionally a pre-assigned uplink permission. The message TRANSFER CONFIRMATION 424 may also have RNL / TNL information for the routing tunnels, if needed. Once the source eNB 404 the message TRANSFER CONFIRMATION 424 or as soon as the transfer of the commit command is initiated in the downlink, data forwarding may be initiated.

The following description provides means for preventing data loss during handover. The target eNB 406 generates the RRC message 426 to perform the handover, that is, the message "RRC Connection Reconfiguration" including the mobilityConfirmnfo received from the source eNB 404 to the UE 402 to send. The source eNB 404 performs the integrity protection and encryption of the message. The UE 402 Receives the message "RRC connection reconfiguration" 426 with parameters (eg, new C-RNTI, target eNB security algorithm identifiers and optionally dedicated RACH preamble, target eNB SIBs, etc.) and is provided by the source eNB 404 instructed to perform the handover. When the RACH-Iose handoff is configured, the message "RRC connection reconfiguration" indicates 426 the time setting indication and optionally the pre-assigned uplink permission to access the destination eNB 406 on. If the pre-assigned uplink permit is not included, the UE may 402 the physical downlink control channel (PDCCH) of the destination eNB 406 to monitor for getting an uplink permit. In certain embodiments, the UE delays 402 the handover execution to provide the HARQ / ARQ responses to the source eNB 404 Not.

When the make-before-break handoff is configured, the connection is made to the source cell after receiving the message "RRC connection reconfiguration" 426 with the mobilityControllnfo maintained before the UE 402 performs the initial uplink transmission to the target cell. If make-before-break handover is configured, the source eNB will decide 404 or the UE 402 when the transmission to the UE 402 should be stopped. The UE 402 can be configured simultaneously with make-before-break handover and RACHeless handover.

If the make-before-break handoff is configured to change the bandwidth for the target cell, the RF chain could be adjusted to cover a different bandwidth. In addition to the RF chain setting or in other embodiments, automatic gain control (AGC) may be needed if the bandwidth is changed. Considering these bandwidth change factors, the interruption time is estimated to be up to 5 ms for certain embodiments. Thus, the UE 402 may not be able to obtain data from the source cell during up to 5 ms during this time. This problem can occur when the source cell bandwidth and the target cell bandwidth are different. Therefore, the embodiments disclosed herein provide methods for make-before-break solutions that reduce the handover delay.

In a make-before-break handover embodiment, the UE performs 402 a downlink and an uplink with the source eNB 404 continue until the UE 402 the RF vote on the eNB 406 performs. In this embodiment, the UE stops 402 communicating with the source eNB 404 when the UE 402 RF settings for the target eNB 406 performs. In the case of the same bandwidth, the UE 402 communicating with the source eNB 404 stop if it is ready for the first PUSCH or PRACH transmission.

In another make-before-break handover embodiment, it depends so much on the implementation of the UE 402 starting when communication with the source eNB 404 should be stopped if the bandwidth of the source and the destination is different, that the UE 402 implements the RF re-vote. In some embodiments, the current technical specifications may be updated to indicate that the UE implementation may determine when to stop the data from the source cell when the bandwidth of the source and the destination is different.

Continue with the procedure 400 , this in 4 is shown, the eNB sends 404 the message SN-STATUS TRANSMISSION 428 to the target eNB 406 for transmitting the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of the E-RABS to which the PDCP status maintenance applies (ie, for RLC AM). The uplink PDCP SN receiver status has at least the Packet Data Convergence Protocol Sequence Number (PDCP SN) of the first missing UL service data unit (SDU) and can take a bitmap of the reception status of the UL SDUs out of line for the UE 402 for forwarding in the target cell, if any such SDUs are present. The downlink PDCP SN transmitter status indicates the next PDCP SN, that of the destination eNB 406 assigns new SDUs that do not yet have PDCP SN. The source eNB 404 can skip sending this message if none of the E-RABs of the UE 402 treated with PDCP status maintenance.

If the RACH-Iose handoff is not configured, after receiving the "RRC connection reconfiguration" message 426 including the mobilityControlInformation the UE 402 the synchronization 430 with the target eNB 406 by accessing the target cell via the RACH for a contention-free procedure, if a dedicated RACH preamble was specified in the mobilityController information, or following a conflict-based procedure if no dedicated preamble was specified. The UE 402 directs target eNB 406 -specific keys and configures the selected security algorithms to be used in the target cell. When the RACH-Iose handover is configured, the UE performs 402 Synchronization with the destination eNB 406 by. The UE 402 directs target eNB 406 -specific keys and configures the selected security algorithms to be used in the target cell.

If the RACH-Iose transfer is not configured, the destination eNB will respond 406 with UL assignment and timing advance 432 , When the RACH-Iose handover is configured and the UE 402 the periodic preassigned uplink permit 434 in the message "RRC connection reconfiguration" 426 including the mobilityConfirmnfo received, the UE receives 402 the uplink permission over the PDCCH of the target cell. The UE 402 uses the first available uplink permission after synchronization with the target cell.

If the UE 402 successful on the target eNB 406 has accessed or has received the uplink permission when the RACH-Iose handoff is configured, the UE sends the message "RRC connection reconfiguration complete" 436 (C-RNTI) for confirming the handover together with an uplink buffer status report whenever possible to the target eNB 406 to indicate that the handover procedure for the UE 402 is completed. The target eNB 406 verifies the C-RNTI, in the message "RRC Connection Reconfiguration Completed" 436 was sent. The target eNB 406 can now begin to data to the UE 402 to send.

The target eNB 406 sends a message PATH CHANGE RECOVERY 438 to the MME 408 to inform them that the UE 402 the cell has changed. The MME 408 sends a message CARRIER CHANGE DEMAND 440 to the service gateway 410 , The service gateway 410 changes the downlink data path 442 on the landing page. The service gateway 410 sends one or more "endmarker" packets on the old path to the source eNB 404 and then can arbitrary U-plane / TNL resources to the source eNB 404 release. The service gateway 410 sends a message CARRIER CHANGE RESPONSE 444 to the MME 408 ,

The MME 408 confirms the message PATH CHANGE RECOVERY 438 with the message PATH REPLACEMENT CONFIRMATION 446 , By sending the message UE-KONTEXTREIGABE 448 informs the target eNB 406 on the success of the transfer to the source eNB 404 and solves the release of resources by the source eNB 404 out. The target eNB 406 sends this message after the message PATH CHANGE CONFIRMATION 446 from the MME 408 is obtained.

After receiving the message UE-KONTEXTFREIGABE 448 can the source eNB 404 resources 450 with respect to radio and the C-plane associated with the UE context. Any continuous data forwarding can be continued. When an X2 handoff is used that includes HeNBs, and when the source HeNB is connected to a HeNB GW, a UE CONTEXT ENTRY LICENSE message including an explicit GW context release indication is sent from the source HeNB to indicate that the HeNB GW can release the resources related to the UE context.

• Das Beispiel A kann ein UE aufweisen, das angepasst ist, um einen Downlink und einen Uplink mit einer Quellzelle fortzuführen, bis das UE die RF-Abstimmung mit der Zielzelle durchführt.
• Das Beispiel B kann das UE von Beispiel A und/oder einiger anderer Beispiele hierin aufweisen, wobei eine UE-Implementierung anzeigt, wann die Daten von der Quellzelle zu stoppen sind, wenn die Bandbreite der Quellzelle und der Zielzelle verschieden sind.
• Das Beispiel C kann das UE der Beispiele A-B und/oder einiger anderer Beispiele hierin aufweisen, wobei Make-before-break konfiguriert ist und sich die Zielzellenbandbreite von der Quellzellenbandbreite unterscheidet.
• Das Beispiel D kann eine Vorrichtung aufweisen, die Mittel zum Durchführen von einem oder mehreren Elementen eines Verfahrens, das in einem der Beispiele A-C beschrieben ist oder mit diesen in Verbindung steht, oder irgendeines anderen hierin beschriebenen Verfahrens oder Prozesses aufweist.
• Das Beispiel E kann ein oder mehrere nichtflüchtige computerlesbare Medien aufweisen, die Befehle aufweisen, um zu bewirken, dass eine elektronische Vorrichtung nach der Ausführung der Befehle durch einen oder mehrere Prozessoren der elektronischen Vorrichtung ein oder mehrere Elemente eines Verfahrens, das in einem der Beispiele A-C beschrieben ist oder mit diesen in Verbindung steht, oder irgendein anderes hierin beschriebenes Verfahren bzw. Prozess durchführt.
• Das Beispiel F kann eine Vorrichtung aufweisen, die eine Logik, Module und/oder eine Schaltungsanordnung zum Durchführen von einem oder mehreren Elementen eines Verfahrens, das in einem der Beispiele A-C beschrieben ist oder mit diesen in Verbindung steht, oder irgendeines anderen hierin beschriebenen Verfahrens oder Prozesses aufweist.
• Das Beispiel G kann ein Verfahren, eine Technik oder einen Prozess, wie in einem der Beispiele A-C beschrieben ist und in Verbindung mit diesen, oder Abschnitte oder Teile davon aufweisen.
• Das Beispiel H kann eine Vorrichtung aufweisen, die Folgendes aufweist: einen oder mehrere Prozessoren und ein oder mehrere computerlesbare Medien, die Befehle aufweisen, die, wenn sie von dem einen oder den mehreren Prozessoren ausgeführt werden, bewirken, dass der eine oder die mehreren Prozessoren das Verfahren, die Techniken oder den Prozess, wie in einem der Beispiele A-C beschrieben ist oder in Verbindung mit diesen, oder Teile davon durchführen.
• Das Beispiel I kann ein Verfahren zum Kommunizieren in einem Drahtlosnetzwerk aufweisen, wie hierin gezeigt und beschrieben ist.
• Das Beispiel J kann ein System zum Bereitstellen einer drahtlosen Kommunikation aufweisen, wie hierin gezeigt und beschrieben ist.
• Das Beispiel K kann eine Vorrichtung zum Bereitstellen einer drahtlosen Kommunikation aufweisen, wie hierin gezeigt und beschrieben ist.

The following are examples according to certain embodiments.

• Example A can be UE adapted to continue a downlink and an uplink with a source cell until the UE performs RF coordination with the target cell.
• Example B can do that UE Example A and / or some other examples herein, wherein a UE implementation indicates when to stop the data from the source cell when the bandwidth of the source cell and the target cell are different.
• Example C can do that UE Examples AB and / or some other examples herein, where make-before-break is configured and the target cell bandwidth differs from the source cell bandwidth.
• Example D may include an apparatus comprising means for performing one or more elements of a method described in or related to one of Examples AC, or any other method or process described herein.
• Example E may include one or more non-transitory computer-readable media having instructions for causing an electronic device to execute, after execution of the instructions by one or more processors of the electronic device, one or more elements of a method as set forth in one of Examples AC described or associated with, or any other process or process described herein.
• Example F may include an apparatus including logic, modules, and / or circuitry for performing one or more elements of a method described in or related to one of Examples AC, or any other method or method described herein Process has.
• Example G may include a method, technique, or process as described in and in conjunction with one of Examples AC, or portions or portions thereof.
• Example H may include an apparatus comprising: one or more processors and one or more computer-readable media having instructions that, when executed by the one or more processors, cause the one or more processors the method, techniques, or process as described in or in conjunction with one of Examples AC, or portions thereof.
• Example I may include a method for communicating in a wireless network, as shown and described herein.
• Example J may include a system for providing wireless communication as shown and described herein.
• Example K may include an apparatus for providing wireless communication as shown and described herein.

• 1 >den Zeitgeber T310 stoppen, wenn er läuft;
• 1 >den Zeitgeber T312 stoppen, wenn er läuft;
• 1>den Zeitgeber T304 mit dem Zeitgeberwert auf t304 festgelegt, wie in den mobilityControllnfo enthalten, starten;
• 1 >den Zeitgeber T370 stoppen, wenn er läuft;
• 1>wenn die Trägerfrequenz enthalten ist:
  • 2>erachten, dass die Ziel-PCell eine auf der Frequenz ist, die durch die Trägerfrequenz mit einer physischen Zellidentität angegeben ist, die durch die physische Ziel-PhysCell-ld angegeben ist;
• 1>ansonsten:
  • 2>erachten, dass die Ziel-PCell eine auf der Frequenz der Quell-PCell mit einer physischen Zellidentität ist, die durch die Ziel-PhysCell-ld angegeben ist;
• 1>das Synchronisieren mit dem DL der Ziel-PCell starten; ANMERKUNG 1: Das UE sollte die Übergabe so früh wie möglich auf den Erhalt der RRC-Nachricht durchführen, die die Übergabe auslöst, was vor dem Bestätigen des erfolgreichen Erhalts (HARQ und ARQ) dieser Nachricht sein könnte.
• 1>wenn BL UE oder UE in CE:
  • 2>den Masterinformationsblock in der Ziel-PCell erhalten;
• 1>wenn makeBeforeBreak konfiguriert ist:
  • 2> das Synchronisieren mit dem DL der Ziel-PSCell starten, wenn die mobilityControllnfoSCG enthalten ist;
  • 2>den Rest dieses Verfahrens einschließlich der Rücksetzung der MAC, nachdem das UE die Uplink-Übertragung/den Downlink-Empfang mit der/den Quellzelle(n) stoppt, und auf dieses folgend durchführen;
  ANMERKUNG 1a: Es hängt von der Implementierung des UE ab, wann die Uplink-Übertragung/der Downlink-Empfang mit der/den Quellzelle(n) gestoppt werden soll, um die Neuabstimmung zur Verbindung mit der Zielzelle zu initiieren, wenn Make-before-break konfiguriert ist.
• 1 >die MCG MAC und die SCG MAC zurücksetzen, wenn konfiguriert;
• 1 >das PDCP für alle RBs, die eingerichtet sind, wiederherstellen; ANMERKUNG 2: Die Handhabung der Funkträger nach dem erfolgreichen Abschluss der PDCP-Wiederherstellung, z. B. die Weiterleitung von nicht bestätigten PDCP SDUs (sowie der zugehörigen Statusberichterstattung).
• 1 >die MCG RLC und die SCG RLC wiederherstellen, wenn konfiguriert, für alle RBs, die eingerichtet sind;
• 1 >die unteren Schichten konfigurieren, um die SCell(s) zu berücksichtigen, die sich von der PSCell unterscheiden, wenn konfiguriert, um im deaktivierten Zustand vorzuliegen;
• 1 >den Wert der neuen UE-Identität als die C-RNTI anwenden;
• 1 >wenn die Nachricht „RRC-Verbindungsneukonfiguration“ die fullConfig aufweist:
  • 2>das Funkkonfigurationsverfahren durchführen;
• 1 >die unteren Schichten gemäß der erhaltenen radioResourceConfigCommon konfigurieren;
• 1 >wenn die erhaltene Nachricht „RRC-Verbindungsneukonfiguration“ das RACH-Überspringen einschließt:
  • 2>den N_TA-Wert für das Ziel-MCG PTAG anwenden, wie durch das targetTA bei dem RACH-Überspringen angegeben;
• 1 >die unteren Schichten gemäß beliebigen zusätzlichen Feldern konfigurieren, die nicht in dem vorherigen abgedeckt sind, wenn sie in den erhaltenen mobilityControllnfo enthalten sind;
• 1 >wenn die erhaltene „RRC-Verbindungsneukonfiguration“ die sCellToReleaseList aufweist:
  • 2>die SCell-Freigabe durchführen;
• 1 >wenn die erhaltene „RRC-Verbindungsneukonfiguration“ die scg-Konfiguration einschließt: oder
• 1 >wenn die aktuelle UE-Konfiguration eine oder mehrere Split-DRBs aufweist und die erhaltene „RRC-Verbindungsneukonfiguration“ radioResourceConfigDedicated einschließlich drb-ToAddModList aufweist:
  • 2>die SCG-Neukonfiguration durchführen;
• 1 >wenn die Nachricht „RRC-Verbindungsneukonfiguration“ die radioResourceConfigDedicated aufweist:
  • 2>das Funkressourcenkonfigurationsverfahren durchführen;
  • 2>das Verfahren endet.

For an example handover method, the receipt of an "RRC connection reconfiguration" including the mobilityControlnfo may be performed by the UE according to the example pseudocode shown below. In some embodiments, additional security and sidelink functionality may be included. If the message "RRC Connection Reconfiguration" has the mobilityControlnfo and the UE is able to conform to the configuration contained in this message, the UE should:

• 1> the timer T310 stop when he is running;
• 1> the timer T312 stop when he is running;
• 1> the timer T304 start with the timer value set to t304 as contained in the mobilityControlfo;
• 1> the timer T370 stop when he is running;
• 1> if the carrier frequency is included:
  • 2> consider that the target PCell is one at the frequency indicated by the carrier frequency with a physical cell identity indicated by the physical target PhysCell-ld;
• 1> otherwise:
  • 2> consider that the target PCell is one at the frequency of the source PCell with a physical cell identity specified by the target PhysCell-ld;
• 1> start the synchronization with the DL of the target PCell; NOTE 1: The UE should perform the handover as early as possible upon receipt of the RRC message triggering the handover, which could be before confirming the successful receipt (HARQ and ARQ) of this message.
• 1> if BL UE or UE in CE:
  • 2> get the master information block in the target PCell;
• 1> if makeBeforeBreak is configured:
  • 2> start syncing with the DL of the target PSCell if the mobilityControlnfoSCG is included;
  • 2> the remainder of this procedure, including the reset of the MAC, after the UE stops the uplink transmission / downlink reception with the source cell (s) and following this;
  NOTE 1a: It depends on the implementation of the UE when the uplink transmission / downlink reception with the source cell (s) should be stopped in order to initiate the retune to connect to the target cell, if make-before break is configured.
• 1> reset the MCG MAC and the SCG MAC if configured;
• 1> restore the PDCP for all RBs that are set up; NOTE 2: The handling of radio bearers after the successful completion of the PDCP recovery, e.g. Eg the forwarding of unacknowledged PDCP SDUs (as well as the related status reporting).
• 1> restore the MCG RLC and the SCG RLC, if configured, for all RBs that are set up;
• 1> configure the lower layers to account for the SCell (s) that differ from the PSCell when configured to be in the disabled state;
• 1> apply the value of the new UE identity as the C-RNTI;
• 1> If the message "RRC connection reconfiguration" has the fullConfig:
  • 2> carry out the radio configuration procedure;
• 1> configure the lower layers according to the received radioResourceConfigCommon;
• 1> if the received message "RRC connection reconfiguration" includes RACH skipping:
  • 2> Apply the N _TA value for the target MCG PTAG as indicated by the targetTA in the RACH skipping;
• 1> configure the lower layers according to any additional fields not covered in the previous one if they are included in the obtained mobilityConffo;
• 1> if the obtained "RRC connection reconfiguration" has the sCellToReleaseList:
  • 2> perform the SCell release;
• 1> if the obtained "RRC connection reconfiguration" includes the scg configuration: or
• 1> if the current UE configuration has one or more split DRBs and the obtained "RRC connection reconfiguration" has radioResourceConfigDedicated including drb-ToAddModList:
  • 2> perform the SCG reconfiguration;
• 1> If the message "RRC connection reconfiguration" shows the radioResourceConfigDedicated:
  • 2> perform the radio resource configuration procedure;
  • 2> the procedure ends.

• 1 >wenn makeBeforeBreakSCG konfiguriert ist:
  • 2>den Zeitgeber T313 stoppen, wenn er läuft;
  • 2>den Zeitgeber T307 mit dem Zeitgeberwert auf t307 festgelegt, wie in mobilityControllnfoSCG enthalten, starten;
  • 2>das Synchronisieren mit dem DL der Ziel-PSCell starten, falls benötigt;
  • 2>den Rest dieses Verfahrens einschließlich der Rücksetzung der MAC, nachdem das UE die Uplink-Übertragung/den Downlink-Empfang mit der/den Quellzelle(n) stoppt, und auf dieses folgend durchführen;
  ANMERKUNG 0a: Es hängt von der Implementierung des UE ab, wann die Uplink-Übertragung/der Downlink-Empfang mit der/den Quellzelle(n) gestoppt werden soll, um die Neuabstimmung zur Verbindung mit der Zielzelle zu starten, wenn makeBeforeBreakSCG konfiguriert ist.
• 1 >wenn RACH-SkipSCG konfiguriert ist:
  • 2>den N_TA -Wert für das SCG PTAG anwenden, wie durch das targetTA bei RACH-SkipSCG angegeben;
• 1 >wenn die erhaltene SCG-Konfiguration derart festgelegt ist, dass sie die mobilityControllnfoSCG freigibt oder einschließt (d. h. SCG-Freigabe/- Wechsel):
  • 2>wenn mobilityControllnfo nicht erhalten wird (d. h. SCG-Freigabe/-Wechsel ohne Übergabe):
    • 3>die SCG MAC zurücksetzen, wenn konfiguriert;
    • 3>für jeden drb-Identitätswert, der Teil der aktuellen UE-Konfiguration ist:
      • 4>wenn der DRB, der durch die drb-Identität angegeben ist, ein SCG DRB ist:
        • 5>die PDCP-Entität und die SCG RLC-Entität oder -Entitäten wiederherstellen;
      • 4>wenn der DRB, der durch die drb-Identität angegeben ist, ein Split-DRB ist:
        • 5>eine PDCP-Datenwiederherstellung durchführen und die SCG RLC-Entität wiederherstellen;
      • 4>wenn der DRB, der durch die drb-Identität angegeben ist, ein MCG DRB ist; und
      • 4>drb-ToAddModListSCG erhalten wird und den drb-Identitätswert aufweist, während für diesen Eintrag der drb-Typ enthalten und auf scg festgelegt ist (d. h. MCG zu SCG):
        • 5>die PDCP-Entität und die MCG RLC-Entität oder -Entitäten wiederherstellen;
    • 3>die unteren Schichten konfigurieren, um die SCG SCell(s) zu berücksichtigen, mit Ausnahme der PSCell, um im deaktivierten Zustand vorzuliegen...

In some embodiments, an example SCG reconfiguration method may operate in accordance with the following pseudocode. The UE should:

• 1> if makeBeforeBreakSCG is configured:
  • 2> the timer T313 stop when he is running;
  • 2> the timer T307 start with the timer value set to t307 as contained in mobilityControllnfoSCG;
  • 2> start syncing with the DL of the target PSCell if needed;
  • 2> the remainder of this procedure, including the reset of the MAC, after the UE stops the uplink transmission / downlink reception with the source cell (s) and following this;
  NOTE 0a: It depends on the implementation of the UE when the uplink transmission / downlink reception with the source cell (s) should be stopped in order to start the retune to connect to the target cell if makeBeforeBreakSCG is configured.
• 1> if RACH-SkipSCG is configured:
  • 2> the N _TA Apply value for the SCG PTAG as indicated by the targetTA at RACH-SkipSCG;
• 1> if the obtained SCG configuration is set to enable or include the mobilityControlnfoSCG (ie SCG release / change):
  • 2> if mobilityControllnfo is not received (ie SCG release / change without transfer):
    • 3> reset the SCG MAC if configured;
    • 3> for each drb identity value that is part of the current UE configuration:
      • 4> if the DRB indicated by the drb identity is an SCG DRB:
        • 5> restore the PDCP entity and the SCG RLC entity or entities;
      • 4> if the DRB specified by the drb identity is a split DRB:
        • 5> Perform a PDCP data recovery and restore the SCG RLC entity;
      • 4> if the DRB indicated by the drb identity is an MCG DRB; and
      • 4> drb-ToAddModListSCG and has the drb identity value, while this entry contains the drb type and is set to scg (ie, MCG to SCG):
        • 5> restore the PDCP entity and the MCG RLC entity or entities;
    • 3> configure the lower layers to consider the SCG SCell (s), except the PSCell, to be in the disabled state ...

5 illustrates an architecture of a system 500 a network according to some embodiments. The system 500 is shown to be a user equipment (UE) 501 and a UE 502 having. The UEs 501 and 502 are illustrated as smartphones (eg, hand held mobile touch screen computing devices that can be connected to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as personal data assistants (PDAs), pagers, Laptop computer, desktop computer, wireless handsets, or any computing device having a wireless communication interface.

In some embodiments, any of the UEs 501 and 502 an Internet of Things (loT) -UE, which may have a network access layer designed for low-power loT applications that use short duration UE connections. An IoT UE may implement technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or MTC device public land mobile network (PLMN), proximity-based service (ProSe), or device-to-device (D2D) communication, sensor networks, or IoT networks. M2M or MTC data exchange can be machine initiated data exchange. An IoT network describes the interconnection of IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with connections of short duration. The IoT UEs can run background applications (eg, keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

The UEs 501 and 502 can be configured to connect to a radio access network (RAN, Radio access network) 510 to connect, z. B. to communicate with this communicatively. The RAN 510 For example, it may be an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network, a NextGen RAN, or any other type of RAN. The UEs 501 and 502 use each connections 503 and 504 each having a physical communication interface or layer (discussed in more detail below); in this example are the links 503 and 504 As an air interface for enabling communicative coupling, cellular communication protocols, such as a GSM (Global System for Mobile Communications) protocol, a code-division multiple access (CDMA) network protocol, a push -to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a UMTS (Universal Mobile Telecommunications System) protocol, a 3GPP long-term development (LTE, Long Term Evolution) protocol, a 5G (fifth generation) protocol, an NR (New Radio, Neufunk) protocol, and the like.

In this embodiment, the UEs 501 and 502 Furthermore, communication data directly via a ProSe interface 505 change. The ProSe interface 505 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including a physical sidelink control channel (PSCCH), a shared physical link channel (PSSCH), a physical sidelink Physical Sidelink Discovery Channel (PSDCH) and physical Sidelink Broadcast Channel (PSBCH), but without being limited to these.

The UE 502 is shown as being configured to access an access point (AP). 506 about the connection 507 access. The connection 507 may comprise a local wireless connection, such as a connection that complies with any IEEE 802.11 protocol, where the AP 506 a wireless fidelity (WiFi®) router. In this example, the AP is 506 shown connected to the Internet without being connected to the core network of the wireless system (described in more detail below).

The RAN 510 may have one or more access nodes containing the connections 503 and 504 enable. These Access Nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs, evolved NodeBs), next generation NodeBs (gNBs), RAN nodes, and so forth, and may include ground stations (e.g. terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN 510 may include one or more RAN nodes for providing macrocells, e.g. For example, the macro RAN node 511 , and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity or greater bandwidth as compared to macrocells), e.g. As the low-current (LP, low power) RAN node 512 , respectively.

Any of the RAN nodes 511 and 512 may terminate the air interface protocol and may be the first contact point for the UEs 501 and 502 his. In some embodiments, any one of the RAN nodes 511 and 512 different logical functions for the RAN 510 including Radio Network Controller (RNC) functions such as, but not limited to, radio bearer management, dynamic uplink and downlink radio resource management and data packet scheduling, and mobility management.

According to some embodiments, the UEs 501 and 502 be configured to communicate with one another or with any of the RAN nodes using Orthogonal Frequency Division Multiplexing (OFDM) communication signals 511 and 512 via a multi-carrier communication channel according to various communication techniques, such as orthogonal frequency-division multiple access (OFDMA) communication technology (e.g., for downlink communications) or single carrier frequency-division multiple access (SC-FDMA) communication technology (eg, for uplink and ProSe or Sidelink communications), but are not limited to communicating, although the scope of the embodiments is not limited in this respect. The OFDM signals may include a plurality of orthogonal subcarriers.

In some embodiments, a downlink resource lattice for downlink transmissions may be from any of the RAN nodes 511 and 512 to the UEs 501 and 502 while uplink transmissions may use similar techniques. The grid may be a time-frequency grid called a resource grid or time-frequency resource grid, which is the physical one Resource is in the downlink in each slot. Such a time-frequency-level representation is a common practice for OFDM systems, making them intuitive for radio resource allocation. Each column and row of the resource grid correspond to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource lattice in the time domain corresponds to a slot in a radio frame. The smallest time-frequency unit in a resource grid is called a resource element. Each resource grid element has a number of resource blocks describing the mapping of specific physical channels to resource elements. Each resource block has a collection of resource elements; in the frequency domain, this can represent the smallest amount of resources that can currently be allocated. There are several different physical downlink channels that are transmitted using such resource blocks.

The shared physical downlink channel (PDSCH) may include user data and higher layer signaling to the UEs 501 and 502 to transfer. The physical downlink control channel (PDCCH) may, among other things, convey information about the transport format and resource allocations with respect to the PDSCH channel. He can also use the UEs 501 and 502 provide information about the transport format, resource allocation, and Hybrid Automatic Repeat Request (H-ARQ) information regarding the shared uplink channel. Typically, downlink scheduling (assignment of control and shared channel resource blocks to the UE 502 within a cell) at any of the RAN nodes 511 and 512 based on channel quality information provided by one of the UEs 501 and 502 be returned. The downlink resource allocation information may be stored on the PDCCH corresponding to each of the UEs 501 and 502 is being used (eg assigned to it).

The PDCCH may use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the complex-valued PDCCH symbols may first be organized into groups of four, which are then permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. The PDCCH may be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel state. There may be four or more different PDCCH formats defined in LTE, with different numbers of CCEs (e.g., aggregation level L = 1, 2, 4, or 8).

Some embodiments may use resource allocation schemes for control channel information that is an extension of the concepts described above. For example, some embodiments may use an Enhanced Physical Downlink Control Channel (EPDCCH) that uses PDSCH resources for control information transfer. The EPDCCH may be transmitted using one or more Enhanced Control Channel Elements (ECCEs). Similar as before, each ECCE may correspond to nine sets of four physical resource elements known as Enhanced Resource Element Groups (EREGs). An ECCE may have different numbers of EREGs in some situations.

The RAN 510 is shown as having an S1 interface 513 - communicative with a core network (CN, Core Network) 520 is coupled. In embodiments, the CN 520 be an evolved packet core (EPC) network, a NextGen packet core (NPC, NextGen Packet Core) network, or any other type of CN. In this embodiment, the S1 -Interface 513 divided into two parts: the S1 -U interface 514 which traffic data is between the RAN nodes 511 and 512 and a service gateway (S-GW) 522 and an S1 Mobility Management Entity (MME) interface 515 which provides a signaling interface between the RAN nodes 511 and 512 and the MMEs 521 is.

In this embodiment, the CN 520 the MMEs 521 , the S-GW 522 , a packet data network (PDN) gateway (P-GW) 523 and a Home Subscriber Server (HSS) 524 on. The MMEs 521 may be similar in function to the control plane of older service GPRS support nodes (SGSN). The MMEs 521 can manage mobility aspects of the access, such as gateway selection and tracking list management. The HSS 524 may include a database for network users including subscription related information for assisting the handling of the network entities of communication sessions. The CN 520 can one or more HSSs 524 Depending on the number of mobile subscribers, the capacity of the devices, the organization of the network, etc. For example, the HSS 524 Support for routing / roaming, authentication, authorization, name / address resolution, location dependencies, etc.

The S-GW 522 can the S1 -Interface 513 to the RAN 510 terminate and route data packets between the RAN 510 and the CN 520 , In addition, the S-GW 522 be a local mobility anchor point for inter-RAN node handoffs and also provide an anchor for inter-3GPP mobility. Other competences may include lawful interception, billing and some policy enforcement.

The P-GW 523 can terminate an SGi interface with a PDN. The P-GW 523 can data packets between the CN 520 (eg an EPC network) and external networks, such as a network including the application server 530 (alternatively referred to as Application Function (AF)) via an Internet Protocol (IP) interface 525 conduct. In general, an application server 530 be an element that provides applications that use IP carrier resources with the core network (e.g., UMTS packet service (PS, Packet Services) domain, LTE PS data services, etc.). In this embodiment, the P-GW 523 shown to be communicative with an application server 530 via an IP communication interface 525 is coupled. The application server 530 may also be configured to provide one or more communication services (eg, Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) to the UEs 501 and 502 over the CN 520 to support.

The P-GW 523 may also be a node for policy enforcement and billing of a data collection. A Policy and Charging Enforcement Function (PCRF) 526 is the policy and billing control of the CN 520 , In a non-roaming scenario, a single PCRF may be present in the Home Public Land Mobile Network (HPLMN) connected to the Internet Protocol Connectivity Access Network (IP-CAN) session of a UE. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of a UE: a home PCRF (H-PCRF) within an HPLMN and a visited PCRF (V-PCRF, Visited PCRF) within a visited public terrestrial mobile network (VPLMN, Visited Public Land Mobile Network). The PCRF 526 Can be communicative with the application server 530 about the P-GW 523 be coupled. The application server 530 can the PCRF 526 signal a new service flow and select the appropriate QoS (Quality of Service) and billing parameters. The PCRF 526 may provide this rule in a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate Traffic Flow Template (TFT) and QoS Class of Identifier (QCI) Classification Identifier (QoS) and billing begins, as by the application server 530 is specified.

6 illustrates exemplary components of a device 600 according to some embodiments. In some embodiments, the device may 600 an application circuitry 602 , a baseband circuitry 604 , Radio Frequency (RF) circuitry 606 , a front end module (FEM) circuitry 608 , one or more antennas 610 and Power Management Circuitry (PMC) 612 have at least as shown coupled together. The components of the illustrated device 600 may be included in a UE or a RAN node. In some embodiments, the device may 600 have fewer elements (eg, a RAN node may not use application circuitry 602 and instead has processor (s) for handling IP data obtained from an EPC). In some embodiments, the device may 600 additional items such as a storage / storage, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (eg, the circuitry may be included separately in more than one device for cloud RAN (C-RAN) implementations).

The application circuitry 602 may include one or more application processors. For example, the application circuitry 602 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 (eg, graphics processors, application processors, etc.). The processors may be coupled to or include the memory / repository and may be configured to execute instructions contained in the memory Storage / storage are provided to enable various applications or operating systems on the device 600 to be executed. In some embodiments, the processors may be the application circuitry 602 Edit IP data packets received from an EPC.

The baseband circuitry 604 For example, circuitry may include, but is not limited to, one or more single-core or multi-core processors. The baseband circuitry 604 may include one or more baseband processors or control logic for processing baseband signals received from a receive signal path of the RF circuitry 606 and for generating baseband signals for a transmit signal path of the RF circuitry 606 respectively. The baseband processing circuitry 604 can with the application circuitry 602 for generating and processing the baseband signals and for controlling operations of the RF circuitry 606 be connected. For example, in some embodiments, the baseband circuitry may be 604 a baseband processor of the third generation ( 3G) 604A , a fourth generation baseband processor ( 4G) 604B , a fifth generation baseband processor ( 5G) 604C or another baseband processor (s) 604D for other existing generations, generations in development or to be developed in the future (eg second generation ( 2G) sixth generation ( 6G) etc.).

The baseband circuitry 604 (eg, one or more of the baseband processors 604A-D) can handle various radio control functions that require communication with one or more wireless networks via the RF circuitry 606 enable. In other embodiments, some or all functionality of the baseband processors may be part of the functionality 604A-D contained in modules that are in memory 604G are stored and executed by a central processing unit (CPU) 604E. The radio control functions may include, but are not limited to, signal modulation / demodulation, coding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry may be the baseband circuitry 604 Fast Fourier transform, precoding or constellation mapping / demapping functionality. In some embodiments, the encoding / decoding circuitry may be the baseband circuitry 604 Convolutional, tail-biting convolution, turbo, Viterbi, or low density parity check (LDPC) encoder-decoder functionality. The embodiments of the modulation / demodulation and encoder / decoder functionality are not limited to these examples and may have other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry may 604 one or more audio digital signal processor (s) (DSP) 604F respectively. The audio DSP (s) 604F may include elements for compression / decompression and echo cancellation, and other suitable processing elements in other embodiments. The 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. In some embodiments, some or all of the constituent components of the baseband circuitry may be 604 and the application circuitry 602 be implemented together, such as on a system-on-a-chip (SOC).

In some embodiments, the baseband circuitry may 604 provide communication that is compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry may be 604 communication with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), a Wireless Local Area Network (WLAN), or a Wireless Personal Network (WPAN) , Wireless Personal Area Network). Embodiments in which the baseband circuitry 604 is configured to support radio communications from more than one wireless protocol, may be referred to as multi-mode baseband circuitry.

The RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 606 Having switches, filters, amplifiers, etc. for enabling communication with the wireless network. The RF circuitry 606 may comprise a receive signal path comprising circuitry for downconverting RF signals received from the FEM circuitry 608 and providing baseband signals for the baseband circuitry 604 can have. The RF circuitry 606 may also comprise a transmit signal path comprising circuitry for upconverting baseband signals received from the baseband circuitry 604 and providing RF output signals to the FEM circuitry 608 can have for transmission.

In some embodiments, the receive signal path of the RF circuitry 606 a mixer circuit arrangement 606A , an amplifier circuit arrangement 606B and filter circuitry 606C respectively. In some embodiments, the transmit signal path of the RF circuitry 606 a filter circuit arrangement 606C and a mixer circuit arrangement 606A respectively. The RF circuitry 606 may also be a synthesizer circuitry 606D for synthesizing a frequency for use by the mixer circuitry 606A the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 606A The receive signal path may be configured to receive RF signals from the FEM circuitry 608 based on the synthesized frequency provided by the synthesizer circuitry 606D is downsized. The amplifier circuit arrangement 606B may be configured to amplify the downconverted signals, and the filter circuitry 606C may be a low pass filter (LPF) or band pass filter (BPF) configured to remove unwanted signals from the downconverted signals to produce output baseband signals. The output baseband signals may be baseband circuitry 604 be provided for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, the mixer circuitry 606A have the receiver signal path passive mixer, although the scope of the embodiments is not limited in this regard.

In some embodiments, the mixer circuitry 606A of the transmit signal path to input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606D is provided to upconvert to RF output signals for the FEM circuitry 608 to create. The baseband signals may be from the baseband circuitry 604 be provided and by the filter circuitry 606C be filtered.

In some embodiments, the mixer circuitry may 606A the receive signal path and the mixer circuitry 606A of the transmit signal path each comprise two or more mixers and be configured for a quadrature downconversion and upconversion. In some embodiments, the mixer circuitry may 606A the receive signal path and the mixer circuitry 606A of the transmit signal path have two or more mixers and be configured for image suppression (eg Hartley image suppression). In some embodiments, the mixer circuitry may 606A the receive signal path and the mixer circuitry 606A each set up for direct down-conversion and direct up-conversion. In some embodiments, the mixer circuitry may 606A the receive signal path and the mixer circuitry 606A the transmit signal path for superheterodyne operation.

In some embodiments, 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. In some alternative embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternative embodiments, the RF circuitry 606 an analog-to-digital converter (ADC) - and a digital-to-analog converter (DAC) circuitry and may include the baseband circuitry 604 a digital baseband interface for communicating with the RF circuitry 606 respectively.

In some dual-mode embodiments, a radio IC (Integrated Circuit) circuitry may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this regard.

In some embodiments, the synthesizer circuitry 606D a fractional N synthesizer or a fractional N / N + 1 synthesizer, although the scope of the embodiments is not limited in this respect since other types of frequency synthesizers may be suitable. For example, the synthesizer circuitry 606D a delta sigma synthesizer, a frequency multiplier or a synthesizer having a phase locked loop with a frequency divider.

The synthesizer circuitry 606D can be configured to have an output frequency for use by the mixer circuitry 606A the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606D a fractional N / N + 1 synthesizer.

In some embodiments, frequency input may be provided by a Voltage Controlled Oscillator (VCO), although this is not a requirement. The divider control input can be either through baseband circuitry 604 or the application circuitry 602 (such as an application processor) depending on the desired output frequency. In some embodiments, a divider control input (eg, N) may be based on a look-up table based on a channel selected by the application circuitry 602 is determined.

The synthesizer circuitry 606D the RF circuitry 606 may include a divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N + 1 (eg, based on an implementation) to provide a fractional split ratio. In some example embodiments, the DLL may include a group of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to divide a VCO period into Nd equal phase packets, where Nd is the number of delay elements in the delay line. This provides the DLL with negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuitry 606D may be configured to produce 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 a quadrature generator and divider circuitry can to generate multiple signals at the carrier frequency with several different phases to each other. In some embodiments, the output frequency may be a local oscillator (LO) frequency (fLO). In some embodiments, the RF circuitry may be 606 have an IQ / Polar converter.

The FEM circuitry 608 may include a receive signal path that may include circuitry configured to process RF signals received from one or more antennas 610 are received to amplify the received signals and the amplified versions of the received signals of the RF circuitry 606 to provide for further processing. The FEM circuitry 608 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission sent by the RF circuitry 606 for transmission through one or more of the one or more antennas 610 to be provided. In various embodiments, the gain through the transmit or receive signal paths may only be in the RF circuitry 606 , only in the FEM circuitry 608 or both in the RF circuitry 606 as well as the FEM circuitry 608 respectively.

In some embodiments, the FEM circuitry 608 a transmit / receive switch for switching between transmit mode and receive mode operation. The FEM circuitry 608 may include a receive signal path and a transmit signal path. The received signal path of the FEM circuitry 608 may include a low noise amplifier (LNA) for amplifying the received RF signals and providing the amplified received RF signals as an output (eg, to the RF circuitry) 606 ) respectively. The transmission signal path of the FEM circuitry 608 may include a power amplifier (PA) for amplifying the input RF signals (eg, through the RF circuitry 606 provided) and one or more filters for generating RF signals for subsequent transmission (eg, through one or more of the one or more antennas 610 ) respectively.

In some embodiments, the PMC 612 Manage power, the baseband circuitry 604 provided. In particular, the PMC 612 control the current source selection, voltage scaling, battery charge or DC-DC conversion. The PMC 612 can often be included when the device 600 is able to be powered by a battery, for example when the device 600 contained in an UE. The PMC 612 can increase the power conversion efficiency while desired Implementation size and heat dissipation characteristics are provided.

6 shows the PMC 612 that only works with the baseband circuitry 604 is coupled. In other embodiments, the PMC 612 however, additionally or alternatively with other components, such as the application circuitry 602 , the RF circuitry 606 or the FEM circuitry 608 but not limited to, and perform similar power management operations for them.

In some embodiments, the PMC 612 various power saving mechanisms of the device 600 control or otherwise be part of it. If, for example, the device 600 is in a state RRC_Connected, where it is still connected to the RAN node, as it expects to receive traffic soon, then it may go into a state known as Discontinuous Reception Mode (DRX) after a Inactivity period occur. During this condition, the device can 600 Shut down for short periods of time, saving electricity.

If there is no data traffic activity for a longer period, then the device may 600 transition to a state RRC_Idle where it disconnects from the network and does no operations such as channel quality feedback, handover, and so on. The device 600 enters a state of very low power and pages, where it is periodically activated again to poll the network and then shut down again. The device 600 may not receive data in this state and return to a RRC_Connected state to receive data.

An additional power-saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (from seconds to a few hours). During this time, the device is completely out of reach of the network and can shut down completely. Any data sent during this time will result in a large delay and it is assumed that the delay is acceptable.

The processors of the application circuitry 602 and the processors of the baseband circuitry 604 can be used to execute elements of one or more instances of a protocol stack. For example, the processors may be baseband circuitry 604 Used alone or in combination with the layers 3 -, the layer 2 or perform the layer 1 functionality while the processors of the application circuitry 602 Can use data (e.g., packet data) obtained from these layers, and also Layer 4 functionality (e.g., Transmission Communication Protocol (TCP) and User Datagram Protocol (UDP) layers) ) To run. As described herein, the layer may 3 a radio resource control (RRC) layer, which will be described in more detail below. As described herein, the layer may 2 a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer layer, which are described in more detail below. As described herein, the layer may 1 a physical (PHY) layer of a UE / RAN node, which will be described in more detail below.

7 FIG. 10 illustrates exemplary interfaces of the baseband circuitry according to some embodiments. FIG. As previously discussed, the baseband circuitry may 604 from 6 processors 604A - 604E and a memory 604G that is used by the processors. Each of the processors 604A - 604E can each have a memory interface 704A - 704E for sending / receiving data to / from the memory 604G respectively.

The baseband circuitry 604 may further include one or more interfaces for communicatively coupling to other circuitry / devices, such as a memory interface 712 (eg, an interface for sending / receiving data to / from the memory related to the baseband circuitry 604 external), an application circuitry interface 714 (eg, an interface for sending / receiving data to / from the application circuitry 602 from 6 ), an RF circuit arrangement interface 716 (eg, an interface for sending / receiving data to / from the RF circuitry 606 from 6 ), a wireless hardware connectivity interface 718 (eg, an interface for sending / receiving data to / from Near Field Communication (NFC) components, Bluetooth® components (eg, Bluetooth® Low Energy), Wi-Fi® components, and others Communication components) and a power management interface 720 (eg, an interface to send / receive power or control signals to / from the PMC 612 ), respectively.

8th FIG. 5 is a block diagram illustrating components in accordance with some example embodiments that are capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing one or more of the methodologies discussed herein. In particular shows 8th a schematic representation of hardware resources 800 including one or more processors (or processor cores) 810 , one or more storage / storage devices 820 and one or more communication resources 830 each communicatively via a bus 840 can be coupled. For embodiments where node virtualization (eg, NFV) is used, a hypervisor may be used 802 to execute an execution environment for one or more network sections / sections to use the hardware resources 800 provide.

The processors 810 (eg, a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC), a Graphics Processing Unit (GPU, Graphics Processing Unit), a Digital Signal Processor (DSP), such as a baseband processor, an Application Specific Integrated Circuit (ASIC), a Radio Frequency Integrated Circuit (RFIC), another processor, or any combination thereof) For example, you can have a processor 812 and a processor 814 include.

The storage / storage devices 820 may include random access memory, floppy disk storage, or any suitable combination thereof. The storage / storage devices 820 may include any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), erasable programmable read-only memory ), electrically erasable programmable read only memory (EEPROM), flash memory, solid state memory, etc., including but not limited to.

The communication resources 830 For example, interconnect or network interface components or other suitable devices may communicate with one or more peripheral devices 804 or one or more databases 806 over a network 808 respectively. For example, the communication resources 830 Wireless communication components (eg, for connection via a universal serial bus (USB)), cellular communication components, NFC components, Bluetooth® components (eg, Bluetooth® Low Energy), Wi-Fi® components, and other communication components ,

The commands 850 may be software, a program, an application, an applet, an app, or other executable code that effects at least one of the processors 810 one or more of the methodologies discussed herein. The commands 850 may be completely or partially within at least one of the processors 810 (eg within the cache memory of the processor), the storage / storage devices 820 or any suitable combination thereof. Furthermore, any part of the commands 850 to the hardware resources 800 from any combination of peripheral devices 804 or the databases 806 be transmitted. Accordingly, the memory of the processors 810 , the storage / storage devices 820 , the peripheral devices 804 and the databases 806 Examples of computer-readable and machine-readable media.

• Das Beispiel 1 ist eine Vorrichtung für ein Benutzergerät (UE), die eine Speicherschnittstelle und einen Basisbandprozessor aufweist. Die Speicherschnittstelle sendet oder empfängt zu oder von einer Speichervorrichtung eine Funkressourcensteuerungs(RRC)-Verbindungsneukonfigurationsnachricht von einer Quellzelle in einem Drahtlosnetzwerk. Der Basisbandprozessor führt Folgendes durch: Decodieren der RRC-Verbindungsneukonfigurationsnachricht, um ein Mobilitätssteuerinformationselement zu erhalten, das Parameter für netzwerkgesteuerte Mobilität des UE zu dem Drahtlosnetzwerk oder innerhalb des Drahtlosnetzwerks aufweist; als Reaktion auf das Mobilitätssteuerinformationselement Initiieren eines Übergabeverfahrens von der Quellzelle zu einer Zielzelle, wobei ein erster Teil des Übergabeverfahrens eine Bestimmung, dass eine Make-before-break-Übergabe konfiguriert ist, einschließt; und als Reaktion auf die Bestimmung, dass die Make-before-break-Übergabe konfiguriert ist: Bewirken, dass das UE die Uplink(UL)-Übertragung und den Downlink(DL)-Empfang mit der Quellzelle bis zu einer Initiierung der Funkfrequenz(RF)-Neuabstimmung des UE zur Verbindung mit der Zielzelle fortführt; Auswählen einer Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle zum Initiieren der RF-Neuabstimmung; und nachdem die UL-Übertragung und der DL-Empfang des UE mit der Quellzelle stoppen, Durchführen eines zweiten Teils des Übergabeverfahrens zum Verbinden mit der Zielzelle.
• Das Beispiel 2 ist die Vorrichtung von Beispiel 1, wobei der zweite Teil des Übergabeverfahrens eine Medienzugriffssteuer(MAC)-Rücksetzung, nachdem das UE die UL-Übertragung und den DL-Empfang mit der Quellzelle stoppt, einschließt.
• Das Beispiel 3 ist die Vorrichtung von einem der Beispiele 1-2, wobei der Basisbandprozessor konfiguriert ist, um die Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle basierend auf einer Bestimmung, dass die Quellzelle und die Zielzelle verschiedene Bandbreiten aufweisen, auszuwählen.
• Das Beispiel 4 ist die Vorrichtung von einem der Beispiele 1-2, wobei der Basisbandprozessor konfiguriert ist, um die Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle zum Verringern der Dienstunterbrechung auszuwählen.
• Das Beispiel 5 ist die Vorrichtung von einem der Beispiele 1-4, wobei das Mobilitätssteuerinformationselement ferner einen Direktzugriffskanal(RACH)-Überspringungsparameter aufweist, um anzuzeigen, ob ein Direktzugriffsverfahren für eine Zielprimärzelle (PCell) übersprungen wird; und wobei der Basisbandprozessor ferner konfiguriert ist, um als Reaktion auf die Bestimmung, dass die Make-before-break-Übergabe konfiguriert ist, das UE zu steuern, um die UL-Übertragung und den Downlink-Empfang mit der Quellzelle vor einer Übertragung durch Folgendes fortzuführen: wenn der RACH-Überspringungsparameter nicht konfiguriert ist, einen physischen Direktzugriffskanal (PRACH) zu der Ziel-PCell; und wenn der RACH-Überspringungsparameter konfiguriert ist, einen gemeinsam genutzten physischen Uplink-Kanal (PUSCH) zu der Ziel-PCell.
• Das Beispiel 6 ist die Vorrichtung von einem der Beispiele 1-5, wobei das Mobilitätssteuerinformationselement einen Make-before-break-Parameter aufweist, der bei der Bestimmung, dass die Make-before-break-Übergabe konfiguriert ist, verwendet wird.
• Das Beispiel 7 ist die Vorrichtung von einem der Beispiele 1-6, wobei das UE für duale Konnektivität konfiguriert ist, und wobei der Basisbandprozessor ferner konfiguriert ist, um: zu bestimmen, dass die RRC-Verbindungsneukonfigurationsnachricht einen Sekundärzellgruppen(SCG)-Neukonfigurationsparameter aufweist; und als Reaktion auf den SCG-Neukonfigurationsparameter die Synchronisierung mit einem DL einer primären Zielsekundärzelle (PSCell) in dem ersten Teil des Übergabeverfahrens zu starten.
• Das Beispiel 8 ist die Vorrichtung von Beispiel 7, wobei der Basisbandprozessor ferner konfiguriert ist, um: zu bestimmen, dass das Mobilitätssteuerinformationselement anzeigt, dass ein Make-before-break-SCG-Parameter konfiguriert ist; und als Reaktion auf die Bestimmung, dass der Make-before-break-SCG-Parameter konfiguriert ist, mindestens einen Teil eines SCG-Neukonfigurationsverfahrens durchzuführen, nachdem die UL-Übertragung und der DL-Empfang des UE mit der Quellzelle stoppen.
• Das Beispiel 9 ist die Vorrichtung von Beispiel 8, wobei das Mobilitätssteuerinformationselement ferner einen Direktzugriffskanal(RACH)-Überspringungs-SCG-Parameter aufweist, um anzuzeigen, ob ein Direktzugriffsverfahren für die Ziel-PSCell übersprungen wird; und wobei der Basisbandprozessor ferner konfiguriert ist, um als Reaktion auf die Bestimmung, dass der Make-before-break-SCG-Parameter konfiguriert ist, das UE zu steuern, um die UL-Übertragung und den Downlink-Empfang mit der Quellzelle vor einer Übertragung durch Folgendes fortzuführen: wenn der RACH-Überspringungs-SCG-Parameter nicht konfiguriert ist, einen physischen Direktzugriffskanal (PRACH) zu der Ziel-PSCell; und wenn der RACH-Überspringungs-SCG-Parameter konfiguriert ist, einen gemeinsam genutzten physischen Uplink-Kanal (PUSCH) zu der Ziel-PSCell.
• Das Beispiel 10 ist ein maschinenlesbares Speichermedium, das maschinenlesbare Befehle aufweist, um, wenn sie von einem oder mehreren Prozessoren eines weiterentwickelten Node B (eNB) ausgeführt werden: basierend mindestens zum Teil auf einem Messbericht von einem Benutzergerät (UE) zu bestimmen, das UE an einen Ziel-eNB zu übergeben; eine Übergabeaufforderungsnachricht für den Ziel-eNB zu erzeugen; als Reaktion auf die Übergabeaufforderungsnachricht eine Übergabeaufforderungsbestätigungsnachricht von dem Ziel-eNB zu bearbeiten, die Informationen zum Weiterleiten an das UE in einer Funkressourcensteuerungs(RRC)-Nachricht aufweist; die RRC-Nachricht zum Konfigurieren des UE für die Make-before-break-Übergabe zu erzeugen, wobei der eNB eine Verbindung mit dem UE aufrechterhält, um ohne Erwartung die Uplink(UL)- und Downlink(DL)-Kommunikation mit dem UE während der Make-before-break-Übergabe an den Ziel-eNB zu erlauben; und eine UE-Kontextfreigabenachricht von dem Ziel-eNB zum Anzeigen des Erfolgs der Make-before-break-Übergabe und zum Freigeben von Ressourcen, die mit dem UE verknüpft sind, zu bearbeiten.
• Das Beispiel 11 ist das maschinenlesbare Speichermedium von Beispiel 10, wobei die maschinenlesbaren Befehle ferner eine Zeit während der Make-before-break-Übergabe bestimmen, um die DL-Kommunikation zu dem UE zu stoppen.
• Das Beispiel 12 ist das maschinenlesbare Speichermedium von einem der Beispiele 10-11, wobei zum Konfigurieren des UE für die Make-before-break-Übergabe die maschinenlesbaren Befehle ferner: die RRC-Nachricht als eine RRC-Verbindungsneukonfigurationsnachricht einschließlich eines Mobilitätssteuerinformationselements, das Parameter für netzwerkgesteuerte Mobilität des UE zu dem Ziel-eNB aufweist, zu codieren; und einen Make-before-break-Parameter in dem Mobilitätssteuerinformationselement festzulegen, um dem UE anzuzeigen, dass die Make-before-break-Übergabe konfiguriert ist.
• Das Beispiel 13 ist das maschinenlesbare Speichermedium von Beispiel 12, wobei die maschinenlesbaren Befehle ferner einen Direktzugriffskanal(RACH)-Überspringungsparameter in dem Mobilitätssteuerinformationselement festlegen, um dem UE anzuzeigen, ob ein Direktzugriffsverfahren für eine Zielprimärzelle (PCell) zu überspringen ist.
• Das Beispiel 14 ist ein maschinenlesbares Speichermedium, das maschinenlesbare Befehle aufweist, um, wenn sie von einem oder mehreren Prozessoren eines Benutzergeräts (UE) ausgeführt werden, das für duale Konnektivität konfiguriert ist: ein Sekundärzellgruppen(SCG)-Neukonfigurationsverfahren zu initiieren; zu bestimmen, dass das UE für Make-before-break-SCG-Neukonfiguration konfiguriert ist; und als Reaktion auf die Bestimmung: die Synchronisierung mit einem Downlink (DL) einer primären Zielsekundärzelle (PSCell) zu starten; und mindestens einen Teil des SCG-Neukonfigurationsverfahrens durchzuführen, nachdem das UE die Uplink(UL)-Übertragung und den DL-Empfang mit einer oder mehreren Quellzellen stoppt.
• Das Beispiel 15 ist das maschinenlesbare Speichermedium von Beispiel 14, wobei die maschinenlesbaren Befehle ferner autonom eine Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle zum Initiieren einer Funkfrequenz(RF)-Neuabstimmung zur Verbindung mit einer Zielzelle auswählen.
• Das Beispiel 16 ist das maschinenlesbare Speichermedium von einem der Beispiele 14-15, wobei zum Initiieren des SCG-Neukonfigurationsverfahrens die maschinenlesbaren Befehle ferner: eine Funkressourcensteuerungs(RRC)-Verbindungsneukonfigurationsnachricht von einem Master evolved Node B (MeNB) zum Erhalten eines SCG-Mobilitätssteuerinformationsparameters decodieren; und als Reaktion auf den SCG-Mobilitätssteuerinformationsparameter und den SCG-Make-before-break-Parameter das SCG-Neukonfigurationsverfahren starten.
• Das Beispiel 17 ist das maschinenlesbare Speichermedium von Beispiel 16, wobei die maschinenlesbaren Befehle ferner anhand der RRC-Verbindungsneukonfigurationsnachricht einen SCG-Make-before-break-Parameter erhalten, der festgelegt ist, um anzuzeigen, dass das UE für die Make-before-break-SCG-Neukonfiguration konfiguriert ist.
• Das Beispiel 18 ist das maschinenlesbares Speichermedium von Beispiel 16, wobei die maschinenlesbaren Befehle ferner: anhand der RRC-Verbindungsneukonfigurationsnachricht einen Direktzugriffskanal(RACH)-Überspringungs-SCG-Parameter erhalten, um anzuzeigen, ob ein Direktzugriffsverfahren für die Ziel-PSCell übersprungen wird; und als Reaktion auf die Bestimmung, dass der Make-before-break-SCG-Parameter konfiguriert ist, das UE steuern, um die UL-Übertragung und den Downlink-Empfang mit der einen oder den mehreren Quellzellen vor einer Übertragung durch Folgendes fortzuführen: wenn der RACH-Überspringungs-SCG-Parameter nicht konfiguriert ist, einen physischen Direktzugriffskanal (PRACH) zu der Ziel-PSCell; und wenn der RACH-Überspringungs-SCG-Parameter konfiguriert ist, einen gemeinsam genutzten physischen Uplink-Kanal (PUSCH) zu der Ziel-PSCell.
• Das Beispiel 19 ist das maschinenlesbare Speichermedium von einem der Beispiele 14-18, wobei zum Durchführen mindestens des Teils des SCG-Neukonfigurationsverfahrens, nachdem das UE stoppt, die maschinenlesbaren Befehle ferner eine SCG-Medienzugriffssteuer(MAC)-Rücksetzung durchführen, nachdem das UE die UL-Übertragung und den DL-Empfang mit der einen oder den mehreren Quellzellen stoppt.
• Das Beispiel 20 ist das maschinenlesbare Speichermedium von einem der Beispiele 14-19, wobei die maschinenlesbaren Befehle ferner eine Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der einen oder den mehreren Quellzellen basierend auf einer Bestimmung, dass die Quellzelle und die Ziel-PSCell mit dem UE unter Verwendung verschiedener Bandbreiten kommunizieren, auswählen.
• Das Beispiel 21 ist ein Verfahren für ein Benutzergerät (UE), das Folgendes umfasst: Bearbeiten einer Funkressourcensteuerungs(RRC)-Nachricht, die von einer Quellzelle in einem Drahtlosnetzwerk erhalten wird, die eine Übergabe des UE von der Quellzelle zu einer Zielzelle impliziert; als Reaktion auf die RRC-Nachricht Initiieren eines Make-before-break-Übergabeverfahrens von der Quellzelle zu der Zielzelle; Bewirken, dass das UE die Uplink(UL)-Übertragung und den Downlink(DL)-Empfang mit der Quellzelle bis zu einer Initiierung der Funkfrequenz(RF)-Neuabstimmung des UE zur Verbindung mit der Zielzelle fortführt; und Auswählen einer Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle zum Initiieren der RF-Neuabstimmung.
• Das Beispiel 22 ist das Verfahren von Beispiel 21, ferner umfassend das Auswählen der Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle basierend auf einer Bestimmung, dass die Quellzelle und die Zielzelle verschiedene Bandbreiten aufweisen.
• Das Beispiel 23 ist das Verfahren von Beispiel 21, ferner umfassend das Auswählen der Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle zum Verringern der Dienstunterbrechung.
• Das Beispiel 24 ist das Verfahren von einem der Beispiele 21-23, wobei das Auswählen der Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs das Auswählen der Zeit während eines Sekundärzellgruppen(SCG)-Wechsels umfasst.
• Das Beispiel 25 ist das Verfahren von einem der Beispiele 21-24, ferner umfassend das Durchführen einer direktzugriffskanal(RACH)-losen Verbindung mit der Zielzelle.
• Das Beispiel 26 ist ein Verfahren für ein Benutzergerät (UE), das Folgendes umfasst: Decodieren der Funkressourcensteuerungs(RRC)-Verbindungsneukonfigurationsnachricht zum Erhalten eines Mobilitätssteuerinformationselements, das Parameter für netzwerkgesteuerte Mobilität des UE zu oder innerhalb eines Drahtlosnetzwerks aufweist; als Reaktion auf das Mobilitätssteuerinformationselement Initiieren eines Übergabeverfahrens von einer Quellzelle zu einer Zielzelle, wobei ein erster Teil des Übergabeverfahrens eine Bestimmung, dass eine Make-before-break-Übergabe konfiguriert ist, einschließt; und als Reaktion auf die Bestimmung, dass die Make-before-break-Übergabe konfiguriert ist: Bewirken, dass das UE die Uplink(UL)-Übertragung und den Downlink(DL)-Empfang mit der Quellzelle bis zu einer Initiierung der Funkfrequenz(RF)-Neuabstimmung des UE zur Verbindung mit der Zielzelle fortführt; Auswählen einer Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle zum Initiieren der RF-Neuabstimmung; und nachdem die UL-Übertragung und der DL-Empfang des UE mit der Quellzelle stoppen, Durchführen eines zweiten Teils des Übergabeverfahrens zum Verbinden mit der Zielzelle.
• Das Beispiel 27 ist das Verfahren von Beispiel 26, wobei der zweite Teil des Übergabeverfahrens eine Medienzugriffssteuer(MAC)-Rücksetzung, nachdem das UE die UL-Übertragung und den DL-Empfang mit der Quellzelle stoppt, einschließt.
• Das Beispiel 28 ist das Verfahren von einem der Beispiele 26-27, ferner umfassend das Auswählen der Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle basierend auf einer Bestimmung, dass die Quellzelle und die Zielzelle verschiedene Bandbreiten aufweisen.
• Das Beispiel 29 ist das Verfahren von einem der Beispiele 26-27, ferner umfassend das Auswählen der Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle zum Verringern der Dienstunterbrechung.
• Das Beispiel 30 ist das Verfahren von einem der Beispiele 26-29, wobei das Mobilitätssteuerinformationselement ferner einen Direktzugriffskanal(RACH)-Überspringungsparameter aufweist, um anzuzeigen, ob ein Direktzugriffsverfahren für eine Zielprimärzelle (PCell) übersprungen wird; und wobei das Verfahren ferner als Reaktion auf die Bestimmung, dass die Make-before-break-Übergabe konfiguriert ist, das Steuern des UE umfasst, um die UL-Übertragung und den Downlink-Empfang mit der Quellzelle vor einer Übertragung durch Folgendes fortzuführen: wenn der RACH-Überspringungsparameter nicht konfiguriert ist, einen physischen Direktzugriffskanal (PRACH) zu der Ziel-PCell; und wenn der RACH-Überspringungsparameter konfiguriert ist, einen gemeinsam genutzten physischen Uplink-Kanal (PUSCH) zu der Ziel-PCell.
• Das Beispiel 31 ist das Verfahren von einem der Beispiele 26-30, wobei das Mobilitätssteuerinformationselement einen Make-before-break-Parameter aufweist, der bei der Bestimmung, dass die Make-before-break-Übergabe konfiguriert ist, verwendet wird.
• Das Beispiel 32 ist das Verfahren von einem der Beispiele 26-31, wobei das UE für duale Konnektivität konfiguriert ist, und wobei das Verfahren ferner Folgendes umfasst: Bestimmen, dass die RRC-Verbindungsneukonfigurationsnachricht einen Sekundärzellgruppen(SCG)-Neukonfigurationsparameter aufweist; und als Reaktion auf den SCG-Neukonfigurationsparameter Starten der Synchronisierung mit einem DL einer primären Zielsekundärzelle (PSCell) in dem ersten Teil des Übergabeverfahrens.
• Das Beispiel 33 ist das Verfahren von Beispiel 32,ferner umfassend: Bestimmen, dass das Mobilitätssteuerinformationselement anzeigt, dass ein Make-before-break-SCG-Parameter konfiguriert ist; und als Reaktion auf die Bestimmung, dass der Make-before-break-SCG-Parameter konfiguriert ist, Durchführen mindestens eines Teils eines SCG-Neukonfigurationsverfahrens, nachdem die UL-Übertragung und der DL-Empfang des UE mit der Quellzelle stoppen.
• Das Beispiel 34 ist das Verfahren von Beispiel 33, wobei das Mobilitätssteuerinformationselement ferner einen Direktzugriffskanal(RACH)-Überspringungs-SCG-Parameter aufweist, um anzuzeigen, ob ein Direktzugriffsverfahren für die Ziel-PSCell übersprungen wird; und wobei das Verfahren ferner als Reaktion auf die Bestimmung, dass der Make-before-break-SCG-Parameter konfiguriert ist, das Steuern des UE umfasst, um die UL-Übertragung und den Downlink-Empfang mit der Quellzelle vor einer Übertragung durch Folgendes fortzuführen: wenn der RACH-Überspringungs-SCG-Parameter nicht konfiguriert ist, einen physischen Direktzugriffskanal (PRACH) zu der Ziel-PSCell; und wenn der RACH-Überspringungs-SCG-Parameter konfiguriert ist, einen gemeinsam genutzten physischen Uplink-Kanal (PUSCH) zu der Ziel-PSCell.
• Das Beispiel 35 ist ein Verfahren für einen weiterentwickelten Node B (eNB), das Folgendes umfasst: basierend mindestens zum Teil auf einem Messbericht von einem Benutzergerät (UE), Bestimmen, das UE an einen Ziel-eNB zu übergeben; Erzeugen einer Übergabeaufforderungsnachricht für den Ziel-eNB; als Reaktion auf die Übergabeaufforderungsnachricht, Bearbeiten einer Übergabeaufforderungsbestätigungsnachricht von dem Ziel-eNB, die Informationen zum Weiterleiten an das UE in einer Funkressourcensteuerungs(RRC)-Nachricht aufweist; Erzeugen der RRC-Nachricht zum Konfigurieren des UE für die Make-before-break-Übergabe, wobei der eNB eine Verbindung mit dem UE aufrechterhält, um ohne Erwartung die Uplink(UL)- und Downlink(DL)-Kommunikation mit dem UE während der Make-before-break-Übergabe an den Ziel-eNB zu erlauben; und Bearbeiten einer UE-Kontextfreigabenachricht von dem Ziel-eNB zum Anzeigen des Erfolgs der Make-before-break-Übergabe und zum Freigeben von Ressourcen, die mit dem UE verknüpft sind.
• Das Beispiel 36 ist das Verfahren von Beispiel 35, ferner umfassend das Bestimmen einer Zeit während der Make-before-break-Übergabe, um die DL-Kommunikation mit dem UE zu stoppen.
• Das Beispiel 37 ist das Verfahren von einem der Beispiele 35-36, wobei zum Konfigurieren des UE für die Make-before-break-Übergabe das Verfahren ferner Folgendes umfasst: Codieren der RRC-Nachricht als eine RRC-Verbindungsneukonfigurationsnachricht einschließlich eines Mobilitätssteuerinformationselements, das Parameter für netzwerkgesteuerte Mobilität des UE zu dem Ziel-eNB aufweist; und Festlegen eines Make-before-break-Parameters in dem Mobilitätssteuerinformationselement, um dem UE anzuzeigen, dass die Make-before-break-Übergabe konfiguriert ist.
• Das Beispiel 38 ist das Verfahren von Beispiel 37, ferner umfassend das Festlegen eines Direktzugriffskanal(RACH)-Überspringungsparameters in dem Mobilitätssteuerinformationselement, um dem UE anzuzeigen, ob ein Direktzugriffsverfahren für eine Zielprimärzelle (PCell) zu überspringen ist.
• Das Beispiel 39 ist ein Verfahren für ein Benutzergerät (UE), das für duale Konnektivität konfiguriert ist, umfassend: Initiieren eines Sekundärzellgruppen(SCG)-Neukonfigurationsverfahrens; Bestimmen, dass das UE für Make-before-break-SCG-Neukonfiguration konfiguriert ist; und als Reaktion auf die Bestimmung: Starten der Synchronisierung mit einem Downlink (DL) einer primären Zielsekundärzelle (PSCell); und Durchführen mindestens eines Teils des SCG-Neukonfigurationsverfahrens, nachdem das UE die Uplink(UL)-Übertragung und den DL-Empfang mit einer oder mehreren Quellzellen stoppt.
• Das Beispiel 40 ist das Verfahren von Beispiel 39, ferner umfassend das autonome Auswählen einer Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle zum Initiieren der Funkfrequenz(RF)-Neuabstimmung zur Verbindung mit einer Zielzelle.
• Das Beispiel 41 ist das Verfahren von einem der Beispiele 39-40, wobei zum Initiieren des SCG-Neukonfigurationsverfahrens das Verfahren ferner Folgendes umfasst: Decodieren einer Funkressourcensteuerungs(RRC)-Verbindungsneukonfigurationsnachricht von einem Master evolved Node B (MeNB) zum Erhalten eines SCG-Mobilitätssteuerinformationsparameters; und als Reaktion auf den SCG-Mobilitätssteuerinformationsparameter und den SCG-Make-before-break-Parameter Initiieren des SCG-Neukonfigurationsverfahrens.
• Das Beispiel 42 ist das Verfahren von Beispiel 41, wobei das Verfahren ferner das Erhalten anhand der RRC-Verbindungsneukonfigurationsnachricht eines SCG-Make-before-break-Parameters, der festgelegt ist, um anzuzeigen, dass das UE für die Make-before-break-SCG-Neukonfiguration konfiguriert ist, umfasst.
• Das Beispiel 43 ist das Verfahren von Beispiel 41, das ferner Folgendes umfasst: Erhalten anhand der RRC-Verbindungsneukonfigurationsnachricht eines Direktzugriffskanal(RACH)-Überspringungs-SCG-Parameters, um anzuzeigen, ob ein Direktzugriffsverfahren für die Ziel-PSCell übersprungen wird; und als Reaktion auf die Bestimmung, dass der Make-before-break-SCG-Parameter konfiguriert ist, Steuern des UE, um die UL-Übertragung und den Downlink-Empfang mit der einen oder den mehreren Quellzellen vor einer Übertragung durch Folgendes fortzuführen: wenn der RACH-Überspringungs-SCG-Parameter nicht konfiguriert ist, einen physischen Direktzugriffskanal (PRACH) zu der Ziel-PSCell; und wenn der RACH-Überspringungs-SCG-Parameter konfiguriert ist, einen gemeinsam genutzten physischen Uplink-Kanal (PUSCH) zu der Ziel-PSCell.
• Das Beispiel 44 ist das Verfahren von einem der Beispiele 39-43, wobei zum Durchführen mindestens des Teils des SCG-Neukonfigurationsverfahrens, nachdem das UE stoppt, das Verfahren ferner das Durchführen einer SCG-Medienzugriffssteuer(MAC)-Rücksetzung, nachdem das UE die UL-Übertragung und den DL-Empfang mit der einen oder den mehreren Quellzellen stoppt, umfasst.
• Das Beispiel 45 ist das Verfahren von einem der Beispiele 39-44, ferner umfassend das Auswählen einer Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der einen oder den mehreren Quellzellen basierend auf einer Bestimmung, dass die Quellzelle und die Ziel-PSCell mit dem UE unter Verwendung verschiedener Bandbreiten kommunizieren.
• Das Beispiel 46 ist eine Vorrichtung, die ein Mittel zum Durchführen eines Verfahrens, wie in einem der Beispiele 21-45 beispielhaft dargestellt, aufweist.
• Das Beispiel 47 ist ein maschinenlesbares Medium, das Code aufweist, der, wenn er ausgeführt wird, bewirkt, dass eine Maschine das Verfahren von einem der Beispiele 21-45 durchführt.
• Das Beispiel 48 ist eine Vorrichtung für einen weiterentwickelten Node B (eNB), die Folgendes aufweist: eine Speichervorrichtung zum Speichern eines Messberichts von einem Benutzergerät (UE); und einen oder mehrere Basisbandprozessoren, um: basierend mindestens zum Teil auf einem Messbericht von einem Benutzergerät (UE) zu bestimmen, das UE an einen Ziel-eNB zu übergeben; eine Übergabeaufforderungsnachricht für den Ziel-eNB zu erzeugen; als Reaktion auf die Übergabeaufforderungsnachricht eine Übergabeaufforderungsbestätigungsnachricht von dem Ziel-eNB zu erzeugen, die Informationen zum Weiterleiten an das UE in einer Funkressourcensteuerungs(RRC)-Nachricht aufweist; die RRC-Nachricht zum Konfigurieren des UE für die Make-before-break-Übergabe zu erzeugen, wobei der eNB eine Verbindung mit dem UE aufrechterhält, um die Uplink(UL)- und Downlink(DL)-Kommunikation mit dem UE während der Make-before-break-Übergabe an den Ziel-eNB zu erlauben, wobei der eNB nicht auf eine Antwort oder Feedback von dem UE während der Make-before-break-Übergabe wartet; und eine UE-Kontextfreigabenachricht von dem Ziel-eNB zum Anzeigen des Erfolgs der Make-before-break-Übergabe und zum Freigeben von Ressourcen, die mit dem UE verknüpft sind, zu bearbeiten.
• Das Beispiel 49 ist die Vorrichtung von Beispiel 48, wobei der eine oder die mehreren Basisbandprozessoren ferner eine Zeit während der Make-before-break-Übergabe bestimmen, um die DL-Kommunikation mit dem UE zu stoppen.
• Das Beispiel 50 ist das die Vorrichtung von einem der Beispiele 48-49, wobei zum Konfigurieren des UE für die Make-before-break-Übergabe der eine oder die mehreren Basisbandprozessoren ferner: die RRC-Nachricht als eine RRC-Verbindungsneukonfigurationsnachricht einschließlich eines Mobilitätssteuerinformationselements, das Parameter für netzwerkgesteuerte Mobilität des UE zu dem Ziel-eNB aufweist, codieren; und einen Make-before-break-Parameter in dem Mobilitätssteuerinformationselement festlegen, um dem UE anzuzeigen, dass die Make-before-break-Übergabe konfiguriert ist.
• Das Beispiel 51 ist die Vorrichtung von Beispiel 50, wobei der eine oder die mehreren Basisbandprozessoren ferner einen Direktzugriffskanal(RACH)-Überspringungsparameter in dem Mobilitätssteuerinformationselement festlegen, um dem UE anzuzeigen, ob ein Direktzugriffsverfahren für eine Zielprimärzelle (PCell) zu überspringen ist.
• Das Beispiel 52 ist eine Vorrichtung für ein Benutzergerät (UE), das für duale Konnektivität konfiguriert ist, die Folgendes aufweist: einen Speicher zum Speichern einer Sekundärzellgruppen(SCG)-kennung; und einen oder mehrere Basisbandprozessoren, um: ein Sekundärzellgruppen(SCG)-Neukonfigurationsverfahren zu initiieren; zu bestimmen, dass das UE für die Make-before-break-Sekundärzellgruppen(SCG)-neukonfiguration konfiguriert ist; und als Reaktion auf die Bestimmung: die Synchronisierung mit einem Downlink (DL) einer primären Zielsekundärzelle (PSCell) zu starten; und mindestens einen Teil des SCG-Neukonfigurationsverfahrens durchzuführen, nachdem das UE die Uplink(UL)-Übertragung und den DL-Empfang mit einer oder mehreren Quellzellen stoppt.
• Das Beispiel 53 ist die Vorrichtung von Beispiel 52, wobei der eine oder die mehreren Basisbandprozessoren ferner autonom eine Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der Quellzelle zum Initiieren der Funkfrequenz(RF)-Neuabstimmung zur Verbindung mit einer Zielzelle auswählen.
• Das Beispiel 54 ist die Vorrichtung von einem der Beispiele 52-53, wobei zum Initiieren des SCG-Neukonfigurationsverfahrens der eine oder die mehreren Basisbandprozessoren ferner Folgendes durchführen: Decodieren einer Funkressourcensteuerungs(RRC)-Verbindungsneukonfigurationsnachricht von einem Master evolved Node B (MeNB) zum Erhalten eines SCG-Mobilitätssteuerinformationsparameters; und als Reaktion auf den SCG-Mobilitätssteuerinformationsparameter und den SCG-Make-before-break-Parameter Initiieren des SCG-Neukonfigurationsverfahrens.
• Das Beispiel 55 ist die Vorrichtung von Beispiel 54, wobei der eine oder die mehreren Basisbandprozessoren ferner anhand der RRC-Verbindungsneukonfigurationsnachricht einen SCG-Make-before-break-Parameter erhalten, der festgelegt ist, um anzuzeigen, dass das UE für die Make-before-break-SCG-Neukonfiguration konfiguriert ist.
• Das Beispiel 56 ist die Vorrichtung von Beispiel 54, wobei der eine oder die mehreren Basisbandprozessoren ferner: anhand der RRC-Verbindungsneukonfigurationsnachricht einen Direktzugriffskanal(RACH)-Überspringungs-SCG-Parameter erhalten, um anzuzeigen, ob ein Direktzugriffsverfahren für die Ziel-PSCell übersprungen wird; und als Reaktion auf die Bestimmung, dass der Make-before-break-SCG-Parameter konfiguriert ist, das UE steuern, um die UL-Übertragung und den Downlink-Empfang mit der einen oder den mehreren Quellzellen vor einer Übertragung durch Folgendes fortzuführen: wenn der RACH-Überspringungs-SCG-Parameter nicht konfiguriert ist, einen physischen Direktzugriffskanal (PRACH) zu der Ziel-PSCell; und wenn der RACH-Überspringungs-SCG-Parameter konfiguriert ist, einen gemeinsam genutzten physischen Uplink-Kanal (PUSCH) zu der Ziel-PSCell.
• Das Beispiel 57 ist die Vorrichtung von einem der Beispiele 52-56, wobei zum Durchführen mindestens des Teils des SCG-Neukonfigurationsverfahrens, nachdem das UE stoppt, der eine oder die mehreren Basisbandprozessoren ferner eine SCG-Medienzugriffssteuer(MAC)-Rücksetzung durchführen, nachdem das UE die UL-Übertragung und den DL-Empfang mit der einen oder den mehreren Quellzellen stoppt.
• Das Beispiel 58 ist die Vorrichtung von einem der Beispiele 52-57, wobei der eine oder die mehreren Basisbandprozessoren ferner eine Zeit zum Stoppen der UL-Übertragung und des DL-Empfangs des UE mit der einen oder den mehreren Quellzellen basierend auf einer Bestimmung, dass die Quellzelle und die Ziel-PSCell mit dem UE unter Verwendung verschiedener Bandbreiten kommunizieren, auswählen.

The following are examples of further embodiments.

• Example 1 is a User Equipment (UE) device having a memory interface and a baseband processor. The memory interface sends or receives to or from a storage device a Radio Resource Control (RRC) connection reconfiguration message from a source cell in a wireless network. The baseband processor performs: decoding the RRC connection reconfiguration message to obtain a mobility control information item having parameters for network-controlled mobility of the UE to the wireless network or within the wireless network; in response to the mobility control information element, initiating a handover procedure from the source cell to a destination cell, wherein a first part of the handover procedure includes a determination that a make before break handoff is configured; and in response to the determination that make-before-break handoff is configured: causing the UE to perform uplink (UL) transmission and downlink (DL) reception with the source cell until initiation of the radio frequency (RF ) Resetting the UE to connect to the target cell; Selecting a time to stop the UL transmission and the DL reception of the UE with the source cell to initiate the RF retune; and after the stopping the UL transmission and the DL reception of the UE with the source cell, performing a second part of the handover procedure for connecting to the target cell.
• Example 2 is the device of Example 1, wherein the second part of the handoff procedure includes a media access control (MAC) reset after the UE stops UL transmission and DL reception with the source cell.
• Example 3 is the apparatus of any one of Examples 1-2, wherein the baseband processor is configured to set the time for stopping the UL transmission and the DL reception of the UE with the source cell based on a determination that the source cell and the target cell different bandwidths to select.
• Example 4 is the apparatus of any of Examples 1-2, wherein the baseband processor is configured to select the time to stop the UL transmission and the DL reception of the UE with the source cell to reduce the service interruption.
• Example 5 is the apparatus of any one of Examples 1-4, wherein the mobility control information element further comprises a random access channel (RACH) skip parameter to indicate whether a random access method for a target primary cell (PCell) is skipped; and wherein the baseband processor is further configured to control the UE in response to the determination that the make-before-break handoff is configured to prevent UL transmission and downlink receipt with the source cell prior to transmission by continue: if the RACH skip parameter is not configured, a physical random access channel (PRACH) to the target PCell; and if the RACH skip parameter is configured, a shared physical uplink (PUSCH) channel to the destination PCell.
• Example 6 is the apparatus of any of Examples 1-5, wherein the mobility control information item has a make-before-break parameter used in determining that make-before-break handoff is configured.
• Example 7 is the apparatus of any one of Examples 1-6, wherein the UE is configured for dual connectivity, and wherein the baseband processor is further configured to: determine that the RRC connection reconfiguration message has a secondary cell group (SCG) reconfiguration parameter; and in response to the SCG reconfiguration parameter, start synchronization with a DL of a primary target secondary cell (PSCell) in the first part of the handoff procedure.
• Example 8 is the apparatus of Example 7, wherein the baseband processor is further configured to: determine that the mobility control information item indicates that a make before break SCG parameter is configured; and in response to the determination that the make-before-break SCG parameter is configured to perform at least a portion of an SCG reconfiguration procedure after the UL transmission and DL reception of the UE with the source cell stop.
• Example 9 is the device of Example 8, wherein the mobility control information element further comprises a random access channel (RACH) skip SCG parameter to indicate whether a random access procedure for the target PSCell is skipped; and wherein the baseband processor is further configured to, in response to the determination that the make-before-break SCG parameter is configured, control the UE for UL transmission and downlink reception with the source cell prior to transmission by continuing: if the RACH skip SCG parameter is not configured, a physical random access channel (PRACH) to the target PSCell; and if the RACH skip SCG parameter is configured, a shared physical uplink channel (PUSCH) to the target PSCell.
• Example 10 is a machine readable storage medium having machine readable instructions for, when executed by one or more enhanced Node B (eNB) processors: based at least in part on a measurement report from a user equipment (UE), determining the UE to hand over to a target eNB; create a handover request message for the destination eNB; in response to the handover request message, processing a handover request acknowledgment message from the target eNB having information for forwarding to the UE in a Radio Resource Control (RRC) message; to generate the RRC message for configuring the make-before-break handover UE, wherein the eNB maintains a connection with the UE to unintentionally uplink (UL) and downlink (DL) communicate with the UE during allow make-before-break handover to the target eNB; and process a UE context release message from the destination eNB to indicate the make-before-break handover success and to release resources associated with the UE.
• Example 11 is the machine-readable storage medium of Example 10, wherein the machine-readable instructions further determine a time during make-before-break handoff to stop the DL communication with the UE.
• Example 12 is the machine-readable storage medium of any of Examples 10-11, wherein to configure the make-before-break handover UE, the machine-readable instructions further include: the RRC message as an RRC connection reconfiguration message including a mobility control information item defining parameters for network-controlled mobility of the UE to the destination eNB to encode; and set a make-before-break parameter in the mobility control information item to indicate to the UE that the make-before-break handover is configured.
• Example 13 is the machine-readable storage medium of Example 12, wherein the machine-readable instructions further define a random access channel (RACH) skip parameter in the mobility control information element to indicate to the UE whether to skip a random access method for a target primary cell (PCell).
• Example 14 is a machine-readable storage medium having machine-readable instructions for, when executed by one or more processors of a user equipment (UE) configured for dual connectivity: to initiate a secondary cell group (SCG) reconfiguration process; determine that the UE is configured for make-before-break SCG reconfiguration; and in response to the determination: to start synchronization with a downlink (DL) of a primary target secondary cell (PSCell); and perform at least a portion of the SCG reconfiguration procedure after the UE stops uplink (UL) transmission and DL reception with one or more source cells.
• Example 15 is the machine-readable storage medium of Example 14, wherein the machine-readable instructions further autonomously select a time to stop the UL transmission and the DL reception of the UE with the source cell to initiate radio frequency (RF) retune for connection to a target cell ,
• Example 16 is the machine-readable storage medium of any one of Examples 14-15, wherein to initiate the SCG reconfiguration process, the machine-readable instructions further decode: a Radio Resource Control (RRC) connection reconfiguration message from a master evolved Node B (MeNB) to obtain an SCG mobility control information parameter ; and start the SCG reconfiguration process in response to the SCG mobility control information parameter and the SCG make-before-break parameter.
• Example 17 is the machine-readable storage medium of Example 16, wherein the machine-readable instructions further obtain an SCG make-before-break parameter based on the RRC connection reconfiguration message that is set to indicate that the UE is for make-before-break -SCG reconfiguration is configured.
• Example 18 is the machine-readable storage medium of Example 16, wherein the machine-readable instructions further: obtain a random access channel (RACH) skip SCG parameter from the RRC connection reconfiguration message to indicate whether a random access procedure for the target PSCell is skipped; and in response to the determination that the make-before-break SCG parameter is configured, controlling the UE to continue the UL transmission and downlink reception with the one or more source cells prior to transmission by: when the RACH skip SCG parameter is not configured, a physical random access channel (PRACH) to the target PSCell; and if the RACH skip SCG parameter is configured, a shared physical uplink channel (PUSCH) to the target PSCell.
• Example 19 is the machine-readable storage medium of any one of Examples 14-18, wherein after performing at least the portion of the SCG reconfiguration process, after the UE stops, the machine-readable instructions further perform an SCG Media Access Control (MAC) reset after the UE releases the UL transmission and DL reception with the one or more source cells stops.
• Example 20 is the machine-readable storage medium of any one of Examples 14-19, wherein the machine-readable instructions further include a time for stopping the UL transmission and the DL reception of the UE with the one or more source cells based on a determination that the source cell and the target PSCell communicate with the UE using different bandwidths.
• Example 21 is a method for a user device ( UE ), comprising: editing a Radio Resource Control (RRC) message received from a source cell in a wireless network that has a radio resource control (RRC) message Handover of the UE implies from the source cell to a target cell; in response to the RRC message, initiating a make-before-break handoff procedure from the source cell to the target cell; Causing the UE to perform uplink (UL) transmission and downlink (DL) reception with the source cell until initiation of radio frequency (RF) re-tuning of the UE continues to connect to the target cell; and selecting a time to stop the UL transmission and the DL reception of the UE with the source cell to initiate the RF retune.
• Example 22 is the method of Example 21, further comprising selecting the time to stop the UL transmission and the DL reception of the UE with the source cell based on a determination that the source cell and the target cell have different bandwidths.
• Example 23 is the method of Example 21, further comprising selecting the time to stop the UL transmission and the DL reception of the UE with the source cell to reduce the service interruption.
• Example 24 is the method of one of Examples 21-23, wherein selecting the time to stop the UL transmission and the DL reception includes selecting the time during a secondary cell group (SCG) change.
• Example 25 is the method of any of Examples 21-24, further comprising performing a direct access channel (RACH) -less connection to the target cell.
• Example 26 is a method for a user equipment (UE), comprising: decoding the radio resource control (RRC) connection reconfiguration message to obtain a mobility control information item having parameters for network-controlled mobility of the UE to or within a wireless network; in response to the mobility control information item, initiating a handover procedure from a source cell to a target cell, wherein a first part of the handover procedure includes a determination that a make before break handoff is configured; and in response to the determination that make-before-break handoff is configured: causing the UE to perform uplink (UL) transmission and downlink (DL) reception with the source cell until initiation of the radio frequency (RF ) Resetting the UE to connect to the target cell; Selecting a time to stop the UL transmission and the DL reception of the UE with the source cell to initiate the RF retune; and after the UL transmission and the DL reception of the UE stop with the source cell, performing a second part of the handover process to connect to the target cell.
• Example 27 is the method of Example 26, wherein the second part of the handoff procedure includes a media access control (MAC) reset after the UE stops UL transmission and DL reception with the source cell.
• Example 28 is the method of any one of Examples 26-27, further comprising selecting the time to stop the UL transmission and the DL reception of the UE with the source cell based on a determination that the source cell and the target cell have different bandwidths ,
• Example 29 is the method of any of Examples 26-27, further comprising selecting the time to stop the UL transmission and the DL reception of the UE with the source cell to reduce the service interruption.
• Example 30 is the method of any of Examples 26-29, wherein the mobility control information element further comprises a random access channel (RACH) skip parameter to indicate whether a random access method for a target primary cell (PCell) is skipped; and wherein the method further comprises, in response to the determination that make-before-break handoff is configured, controlling the UE to continue UL transmission and downlink reception with the source cell prior to transmission by: the RACH skip parameter is not configured, a physical random access channel (PRACH) to the target PCell; and if the RACH skip parameter is configured, a shared physical uplink (PUSCH) channel to the destination PCell.
• Example 31 is the method of one of Examples 26-30, wherein the mobility control information item has a make-before-break parameter used in determining that make-before-break handoff is configured.
• Example 32 is the method of any one of Examples 26-31, wherein the UE is configured for dual connectivity, and wherein the method further comprises: determining that the RRC connection reconfiguration message has a secondary cell group (SCG) reconfiguration parameter; and in response to the SCG reconfiguration parameter, starting synchronization with a DL of a primary target secondary cell (PSCell) in the first part of the handoff procedure.
• Example 33 is the method of Example 32, further comprising: determining that the mobility control information item indicates that a make-before-break SCG parameter is configured; and in response to determining that the make-before-break SCG parameter is configured, performing at least a portion of an SCG reconfiguration procedure after the UL transmission and DL reception of the UE with the source cell stop.
• Example 34 is the method of Example 33, wherein the mobility control information element further comprises a random access channel (RACH) skip SCG parameter to indicate whether a random access procedure for the target PSCell is skipped; and wherein the method further comprises, in response to the determination that the make-before-break SCG parameter is configured, controlling the UE to continue the UL transmission and the downlink reception with the source cell prior to transmission by the following if the RACH skip SCG parameter is not configured, a physical random access channel (PRACH) to the target PSCell; and if the RACH skip SCG parameter is configured, a shared physical uplink channel (PUSCH) to the target PSCell.
• Example 35 is a method for a refined Node B (eNB) comprising: based at least in part on a measurement report from a user equipment (UE), determining to transfer the UE to a destination eNB; Generating a handover request message for the destination eNB; in response to the handover request message, processing a handover request acknowledgment message from the destination eNB having information for forwarding to the UE in a Radio Resource Control (RRC) message; Generating the RRC message for configuring the make-before-break handover UE, the eNB maintaining a connection with the UE to unintentionally uplink (UL) and downlink (DL) communicate with the UE during the Allow make-before-break handover to the target eNB; and processing a UE context release message from the destination eNB to indicate the success of the make-before-break handover and to release resources associated with the UE.
• Example 36 is the method of Example 35, further comprising determining a time during make-before-break handoff to stop DL communication with the UE.
• Example 37 is the method of any one of Examples 35-36, wherein for configuring the make-before-break handover UE, the method further comprises: encoding the RRC message as an RRC connection reconfiguration message including a mobility control information item containing parameters for network-controlled mobility of the UE to the destination eNB; and setting a make before break parameter in the mobility control information item to indicate to the UE that the make before break handover is configured.
• Example 38 is the method of Example 37, further comprising determining a random access channel (RACH) skip parameter in the mobility control information element to indicate to the UE whether to skip a random access method for a target primary cell (PCell).
• Example 39 is a procedure for a user device ( UE ) configured for dual connectivity, comprising: initiating a secondary cell group (SCG) reconfiguration process; Determine that UE configured for make-before-break SCG reconfiguration; and in response to the determination: starting synchronization with a downlink ( DL ) a primary target secondary cell (PSCell); and performing at least a portion of the SCG reconfiguration procedure after the UE uplink (UL) transmission and DL reception with one or more source cells stops.
• Example 40 is the method of Example 39, further comprising autonomously selecting a time to stop the UL transmission and the DL reception of the UE with the source cell to initiate radio frequency (RF) retune for connection to a target cell.
• Example 41 is the method of any of Examples 39-40, wherein to initiate the SCG reconfiguration method, the method further comprises: decoding a Radio Resource Control (RRC) connection re-configuration message from a Master Evolved Node B (MeNB) to obtain an SCG mobility control information parameter ; and in response to the SCG mobility control information parameter and the SCG make-before-break parameter, initiating the SCG reconfiguration process.
• Example 42 is the method of Example 41, wherein the method further includes obtaining based on the RRC connection reconfiguration message of an SCG make-before-break parameter that is set to indicate that the UE is configured for make-before-break SCG reconfiguration.
• Example 43 is the method of Example 41, further comprising: obtaining, based on the RRC connection reconfiguration message, a random access channel (RACH) skip SCG parameter to indicate whether a random access procedure for the target PSCell is skipped; and in response to determining that the make-before-break SCG parameter is configured, controlling the UE to continue UL transmission and downlink reception with the one or more source cells prior to transmission by: when the RACH skip SCG parameter is not configured, a physical random access channel (PRACH) to the target PSCell; and if the RACH skip SCG parameter is configured, a shared physical uplink channel (PUSCH) to the target PSCell.
• Example 44 is the method of any one of Examples 39-43, wherein performing at least the portion of the SCG reconfiguration method after the UE stops, the method further comprises performing an SCG Media Access Control (MAC) reset after the UE sets the UL Transmission and the DL reception stops with the one or more source cells.
• Example 45 is the method of any of Examples 39-44, further comprising selecting a time to stop the UL transmission and the DL reception of the UE with the one or more source cells based on a determination that the source cell and the source Target PSCell communicate with the UE using different bandwidths.
• Example 46 is an apparatus having means for performing a method as exemplified in any of Examples 21-45.
• Example 47 is a machine-readable medium having code that, when executed, causes a machine to perform the method of any one of Examples 21-45.
• Example 48 is an advanced Node B (eNB) device, comprising: a memory device for storing a measurement report from a user device ( UE ); and one or more baseband processors to: at least partially based on a measurement report from a user device ( UE ) to commit the UE to a destination eNB; create a handover request message for the destination eNB; in response to the handover request message, generate a handover request acknowledgment message from the destination eNB containing the information to be forwarded to UE in a Radio Resource Control (RRC) message; the RRC message to configure the UE for the make-before-break handoff, wherein the eNB maintains a connection with the UE to forward the uplink (UL) and downlink (DL) communications with the UE during make-before-break handoff to the UE Target eNB, whereby the eNB does not request or feedback from the eNB UE during make-before-break handoff waiting; and a UE context release message from the target eNB for indicating the success of the make-before-break handover and releasing resources associated with the UE are linked to edit.
• Example 49 is the device of Example 48, wherein the one or more baseband processors further determine a time during make-before-break handoff to initiate the DL communication with the UE to stop.
• Example 50 is that of the apparatus of any one of Examples 48-49, wherein for configuring the make-before-break handover UE of the one or more baseband processors further comprises: the RRC message as an RRC connection reconfiguration message including a mobility control information item, encode the network-controlled mobility parameter of the UE to the destination eNB; and set a make before break parameter in the mobility control information item to indicate to the UE that the make before break handover is configured.
• Example 51 is the apparatus of Example 50, wherein the one or more baseband processors further define a random access channel (RACH) skip parameter in the mobility control information element to indicate to the UE whether to skip a random access method for a target primary cell (PCell).
• Example 52 is a user equipment device (UE) configured for dual connectivity, comprising: memory for storing a secondary cell group (SCG) identifier; and one or more baseband processors to: initiate a secondary cell group (SCG) reconfiguration process; determine that the UE is configured for make-before-break secondary cell group (SCG) reconfiguration; and in response to the determination: to start synchronization with a downlink (DL) of a primary target secondary cell (PSCell); and perform at least a portion of the SCG reconfiguration procedure after the UE stops uplink (UL) transmission and DL reception with one or more source cells.
• Example 53 is the apparatus of Example 52, wherein the one or more baseband processors further autonomously include a time to stop the UL transmission and the DL reception of the UE with the source cell to initiate radio frequency (RF) retune for connection to a source cell Select target cell.
• Example 54 is the apparatus of any one of Examples 52-53, wherein for initiating the SCG reconfiguration process, the one or more baseband processors further perform: decoding a Radio Resource Control (RRC) connection reconfiguration message from a Master Evolved Node B (MeNB) to obtain an SCG mobility control information parameter; and in response to the SCG mobility control information parameter and the SCG make-before-break parameter, initiating the SCG reconfiguration process.
• Example 55 is the apparatus of Example 54, wherein the one or more baseband processors further obtain from the RRC connection reconfiguration message an SCG make-before-break parameter set to indicate that the UE is configured for make-before-break SCG reconfiguration.
• Example 56 is the apparatus of Example 54, wherein the one or more baseband processors further: obtain a random access channel (RACH) skip SCG parameter from the RRC connection reconfiguration message to indicate whether a random access procedure for the target PSCell is skipped ; and in response to the determination that the make-before-break SCG parameter is configured, controlling the UE to continue the UL transmission and downlink reception with the one or more source cells prior to transmission by: when the RACH skip SCG parameter is not configured, a physical random access channel (PRACH) to the target PSCell; and if the RACH skip SCG parameter is configured, a shared physical uplink channel (PUSCH) to the target PSCell.
• Example 57 is the apparatus of any one of Examples 52-56, wherein after performing at least the portion of the SCG reconfiguration method after the UE stops, the one or more baseband processors further perform an SCG Media Access Control (MAC) reset after that UE stops UL transmission and DL reception with the one or more source cells.
• Example 58 is the apparatus of any one of Examples 52-57, wherein the one or more baseband processors further include a time to stop the UL transmission and the DL reception of the UE with the one or more source cells based on a determination that the source cell and the target PSCell communicate with the UE using different bandwidths.

One skilled in the art will understand that many changes may be made in the details of the embodiments described above without departing from the underlying principles of the disclosure. The scope of the present disclosure is therefore determined only by the following claims.

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited patent literature

• US 62417701 [0001]

Claims (27)

Device for a User Equipment (UE), comprising: a memory interface for sending or receiving to or from a storage device of a Radio Resource Control (RRC) connection reconfiguration message from a source cell in a wireless network; and a baseband processor for: Decoding the RRC connection reconfiguration message to obtain a mobility control information item having network-controlled mobility parameters of the UE to the wireless network or within the wireless network; in response to the mobility control information item, starting a handover method from the source cell to a target cell, wherein a first part of the handover method includes a determination that a make before break handoff is configured; and in response to the determination that make-before-break handover is configured: Causing the UE to continue uplink (UL) transmission and downlink (DL) reception with the source cell until initiation of radio frequency (RF) re-tuning of the UE for connection to the target cell; Selecting a time to stop the UL transmission and the DL reception of the UE with the source cell to initiate the RF retune; and after the UL transmission and the DL reception of the UE stop with the source cell, performing a second part of the handover process to connect to the target cell. Device after Claim 1 wherein the second part of the handover procedure includes a media access control (MAC) reset after the UE stops the UL transmission and the DL reception with the source cell. Device after Claim 1 wherein the baseband processor is configured to select the time to stop the UL transmission and the DL reception of the UE with the source cell based on a determination that the source cell and the target cell have different bandwidths. Device after Claim 1 wherein the baseband processor is configured to select the time to stop the UL transmission and the DL reception of the UE with the source cell to reduce the service interruption. Device according to one of Claims 1 - 4 wherein the mobility control information element further comprises a random access channel (RACH) skip parameter to indicate whether a random access method for a target primary cell (PCell) is skipped; and wherein the baseband processor is further configured to control the UE in response to the determination that the make-before-break handoff is configured to prevent UL transmission and downlink receipt with the source cell prior to transmission by continue: if the RACH skip parameter is not configured, a physical random access channel (PRACH) to the target PCell; and if the RACH skip parameter is configured, a shared physical uplink (PUSCH) channel to the destination PCell. Device according to one of Claims 1 - 4 wherein the mobility control information element has a make-before-break parameter used in determining that make-before-break handoff is configured. Device according to one of Claims 1 - 4 wherein the UE is configured for dual connectivity, and wherein the baseband processor is further configured to: determine that the RRC connection reconfiguration message has a secondary cell group (SCG) reconfiguration parameter; and in response to the SCG reconfiguration parameter, start synchronization with a DL of a primary target secondary cell (PSCell) in the first part of the handoff procedure. Device after Claim 7 wherein the baseband processor is further configured to: determine that the mobility control information item indicates that a make-before-break SCG parameter is configured; and in response to the determination that the make-before-break SCG parameter is configured to perform at least a portion of the SCG reconfiguration procedure after the UL transmission and the DL reception of the UE with the source cell stop. Device after Claim 8 wherein the mobility control information element further comprises a random access channel (RACH) skip SCG parameter to indicate whether a random access procedure for the target PSCell is skipped; and wherein the baseband processor is further configured to, in response to the determination that the make-before-break SCG parameter is configured, control the UE for UL transmission and downlink reception with the source cell prior to transmission continue by: if the RACH skip SCG parameter is not configured, a physical random access channel (PRACH) to the target PSCell; and if the RACH skip SCG parameter is configured, a shared physical uplink channel (PUSCH) to the target PSCell. A machine-readable storage medium having machine-readable instructions for being executed by one or more advanced Node B (eNB) processors: based at least in part on a measurement report from a user equipment (UE) to determine to transfer the UE to a destination eNB; create a handover request message for the destination eNB; in response to the handover request message, processing a handover request acknowledgment message from the target eNB having information for forwarding to the UE in a Radio Resource Control (RRC) message; to generate the RRC message for configuring the make-before-break handover UE, wherein the eNB maintains a connection with the UE to unintentionally uplink (UL) and downlink (DL) communicate with the UE during allow make-before-break handover to the target eNB; and process a UE context release message from the destination eNB to indicate the make-before-break handover success and to release resources associated with the UE. Machine-readable storage medium after Claim 10 wherein the machine-readable instructions further determine a time during make-before-break handoff to stop the DL communication with the UE. Machine-readable storage medium according to one of Claims 10 - 11 wherein for configuring the make-before-break handover UE, the machine-readable instructions further encode: the RRC message as an RRC connection reconfiguration message including a mobility control information element having network-controlled mobility parameters of the UE to the destination eNB; and set a make before break parameter in the mobility control information item to indicate to the UE that the make before break handover is configured. Machine-readable storage medium after Claim 12 wherein the machine-readable instructions further define a random access channel (RACH) skip parameter in the mobility control information element to indicate to the UE whether to skip a random access method for a target primary cell (PCell). A machine-readable storage medium having machine-readable instructions for being executed by one or more processors of a user equipment (UE) configured for dual-connectivity: initiate a secondary cell group (SCG) reconfiguration process; determine that the UE is configured for make-before-break SCG reconfiguration; and in response to the determination: start synchronization with a downlink (DL) of a primary target secondary cell (PSCell); and perform at least part of the SCG reconfiguration procedure after the UE stops uplink (UL) transmission and DL reception with one or more source cells. Machine-readable storage medium after Claim 14 wherein the machine-readable instructions further autonomously select a time to stop the UL transmission and the DL reception of the UE with the source cell to initiate radio frequency (RF) retune for connection to a target cell. Machine-readable storage medium according to one of Claims 14 - 15 wherein, to initiate the SCG reconfiguration method, the machine-readable instructions further: decode a Radio Resource Control (RRC) connection re-configuration message from a master evolved node B (MeNB) to obtain an SCG mobility control information parameter; and in response to the SCG mobility control information parameter and the SCG make-before-break parameter, initiate the SCG reconfiguration process. Machine-readable storage medium after Claim 16 wherein the machine-readable instructions further receive an SCG make-before-break parameter based on the RRC connection reconfiguration message that is set to indicate that the UE is configured for make-before-break SCG reconfiguration. Machine-readable storage medium after Claim 16 wherein the machine-readable instructions further: obtain from the RRC connection reconfiguration message a random access channel (RACH) skip SCG parameter for indicating whether a random access procedure for the target PSCell is skipped; and in response to the determination that the make-before-break SCG parameter is configured, controlling the UE to continue the UL transmission and downlink reception with the one or more source cells prior to transmission by: if the RACH skip SCG parameter is not configured, a physical random access channel (PRACH) to the target PSCell; and if the RACH skip SCG parameter is configured, a shared physical uplink channel (PUSCH) to the target PSCell. Machine-readable storage medium according to one of Claims 14 - 15 wherein, after performing at least the portion of the SCG reconfiguration method, after the UE stops, the machine-readable instructions further perform an SCG Media Access Control (MAC) reset after the UE transmits the UL transmission and the DL reception with the one or more Source cells stops. Machine-readable storage medium according to one of Claims 14 - 15 wherein the machine-readable instructions further include a time for stopping the UL transmission and the DL reception of the UE with the one or more source cells based on a determination that the source cell and the target PSCell communicate with the UE using different bandwidths, choose. A user equipment (UE) method comprising: Processing a Radio Resource Control (RRC) message received from a source cell in a wireless network that implies handover of the UE from the source cell to a destination cell; in response to the RRC message, initiating a make-before-break handoff procedure from the source cell to the target cell; Causing the UE to continue uplink (UL) transmission and downlink (DL) reception with the source cell until initiation of radio frequency (RF) re-tuning of the UE for connection to the target cell; and Selecting a time to stop the UL transmission and the DL reception of the UE with the source cell to initiate the RF retune. Method according to Claim 21 further comprising selecting the time to stop the UL transmission and the DL reception of the UE with the source cell based on a determination that the source cell and the target cell have different bandwidths. Method according to Claim 21 further comprising selecting the time to stop the UL transmission and the DL reception of the UE with the source cell to reduce the service interruption. Method according to Claim 21 wherein selecting the time to stop the UL transmission and the DL reception comprises selecting the time during a secondary cell group (SCG) change. Method according to Claim 21 further comprising performing a direct access channel (RACH) -less connection with the target cell. Apparatus comprising means for carrying out a method according to any one of Claims 21 - 25 having. Machine-readable medium having code that, when executed, causes a machine to perform the method of any of Claims 21 - 25 performs.

Images