[go: up one dir, main page]

WO2018013110A1 - Support multiconnectivité et commutation rapide de cellules pour technologies d'accès radio cellulaire à ondes millimétriques - Google Patents

Support multiconnectivité et commutation rapide de cellules pour technologies d'accès radio cellulaire à ondes millimétriques Download PDF

Info

Publication number
WO2018013110A1
WO2018013110A1 PCT/US2016/042134 US2016042134W WO2018013110A1 WO 2018013110 A1 WO2018013110 A1 WO 2018013110A1 US 2016042134 W US2016042134 W US 2016042134W WO 2018013110 A1 WO2018013110 A1 WO 2018013110A1
Authority
WO
WIPO (PCT)
Prior art keywords
enb
communications
link
communications link
loss detection
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2016/042134
Other languages
English (en)
Inventor
Jing Zhu
Nageen Himayat
Wook Bong Lee
Sarabjot SINGH
Ehsan ARYAFAR
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Priority to CN201680086744.7A priority Critical patent/CN109314901B/zh
Priority to PCT/US2016/042134 priority patent/WO2018013110A1/fr
Publication of WO2018013110A1 publication Critical patent/WO2018013110A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022—Site diversity; Macro-diversity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443—Reselecting a network or an air interface over a different radio air interface technology between licensed networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • UMTS Telecommunications System
  • LTE Long-Term Evolution
  • LTE-Advanced 3GPP Long-Term Evolution-Advanced
  • 5G 5th Generation mobile networks
  • NR 5th Generation new radio
  • Some proposed cellular communication systems may incorporate radio frequencies including one or more frequency bands between 30 gigahertz and 300 gigahertz.
  • millimeter wave (mmWave) systems Corresponding with radio wavelengths from 10 mm to 1 mm, such communication systems may sometimes be referred to as millimeter wave (mmWave) systems.
  • mmWave millimeter wave
  • Figure 1 shows a proposed multi-connectivity network architecture according to examples
  • Figure 2 shows an example of a possible end to end (e2e) user-plane protocol stack for the proposed multi-connectivity network architecture of Figure 1;
  • Figure 3 shows an example of a possible end to end (e2e) control-plane protocol stack for the proposed multi-connectivity network architecture of Figure 1;
  • Figure 4 shows a first optional example of how PSS/SSS/SLS synchronization signals from neighboring cells may be distributed in a frame
  • Figure 5 shows a second optional example of how PSS/SSS/SLS synchronization signals from neighboring cells may be distributed in a frame
  • Figure 6 shows how a short broadcast (sBCH) according to examples may be allocated in a subframe with three sectors: A, B, and C;
  • sBCH short broadcast
  • Figure 7 shows how a persistent Scheduling Request request message (pSR-REQ) and a persistent Scheduling Request response message (pSR-RSP) may be allocated in a special subframe, around the existing content;
  • Figure 8 shows how the pSR-REQ and pSR-RSP messages may be allocated in a normal subframe, around the existing content
  • Figure 9 shows a high level flow diagram of a method of detecting communications link loss according to an example
  • Figure 10 shows a portion of a method for a UE to detect the loss of a primary communications link and the resultant switch of its primary cell, according to some examples
  • Figure 11 illustrates hardware processing circuitries for a UE and eNB, in accordance with some examples
  • Figure 12 shows an example implementation of an electronic device (e.g. UE or eNB) in accordance with some examples
  • Figure 13 shows a diagrammatic representation of hardware resources in accordance with some examples.
  • Millimeter wave (mmWave) systems have a potential to provide enormous bandwidth.
  • mmWave systems may also be called high frequency band systems, or extremely high frequency band systems. Due to the potential bandwidth, mmWave systems are a candidate for supporting future 5G systems.
  • mmWave small cells may be deployed in an LTE-assisted“anchor booster” mode. In other cases, mmWave small cells may be deployed to operate in a standalone manner (e.g., without assistance from an LTE macro cell).
  • a cell is a logical concept, and may be referenced as a Radio Access Network (or part thereof).
  • a cell may be provided by a single evolved Node-B (eNB) and Radio head end, or multiple radio head ends of an eNB, dependent on the particular cell provision architecture.
  • eNB evolved Node-B
  • Radio head end or multiple radio head ends of an eNB, dependent on the particular cell provision architecture.
  • an eNB is a physical equipment, and an eNB may operate one, or multiple cells.
  • High frequency band systems such as mmWave systems may require directional beamforming on the part of both an Evolved Node-B (eNB) (or Access Point (AP)/Base Station (BS)) and a User Equipment (UE) (or Station (STA)) in order to achieve a Signal-to- Noise Ratio (SNR) conducive to establishing a communication link at the frequencies used.
  • eNB Evolved Node-B
  • UE User Equipment
  • STA Station
  • an initial acquisition procedure or access procedure may be used to allow an eNB and a UE to determine the best transmission (TX) and/or receiving (RX) beamforming directions (or beams) for establishing directional connections. Since a mmWave
  • a communications link is highly directional and sensitive to the environment, it can therefore be easily blocked (where blocked includes any way in which a communication link between a UE and eNB may be broken or lost– i.e. including where the UE is no longer able to communicate with a eNB (or vice versa) at all, or simply not at a level with sufficient pre- determined performance).
  • examples include total blockages, as well as deemed blockages where communication performance falls below an acceptable (i.e. pre-determined) performance level.
  • a fast cell switching procedure may be provided to temporarily transition to an alternative (i.e.
  • the primary or secondary communications links may be Radio Access Technology (RAT) other than a mmWave RAT.
  • RAT Radio Access Technology
  • the described fast cell switching procedure(s) may therefore be advantageous in designing an mmWave system or other high frequency band system that is more resilient.
  • the described fast cell switching procedure(s) may utilise a dual-connectivity (DC) procedure to use the (more robust) LTE communications link as the anchor, and the 5G mmWave communications link as the booster.
  • DC dual-connectivity
  • the“hot standby” alternative communications link may be another mmWave communications link, or a completely different radio access technology type communications link.
  • the UE may maintain both communications links such that whenever the 5G mmWave communications link is temporarily lost, the UE’s data traffic can be seamlessly moved to the LTE communications link.
  • the described fast cell switching procedure(s) may also utilise multiple communications links (e.g. >2) simultaneously, in which situation it may be called a multi- connectivity (MC) procedure, to allow for fast switching among the multiple communications links.
  • MC multi- connectivity
  • mmWave cells may be similar in terms of coverage and reliability (to each other).
  • advantages include the maximisation of the use of the mmWave Radio Access Technology (RAT)/cells.
  • RAT Radio Access Technology
  • examples may also provide further optimizations within the radio network to address issues arising from the directional access nature of mmWave based RATs.
  • optimizations provided may support dual/multi-connectivity for mmWave based radio networks, which may include extensions to the dual connectivity architecture.
  • examples provide a new multi-connectivity network architecture which is based on dual connectivity principles but extends this to multi-connectivity by including some key changes that address switching of both the control plane and user plane traffic to a secondary cell/eNB, when the primary mmWave communications link is blocked.
  • the secondary cell(s)/eNB(s) advantageously serve(s) in a“hot standby” mode (i.e. in a mode where they can be utilised immediately).
  • Examples also provide a new method to coordinate DownLink (DL) synchronization and/or broadcast channel(s) and/or Sector Level Sweep (SLS) among neighboring cells.
  • DL DownLink
  • SLS Sector Level Sweep
  • this may advantageously provide a loose (i.e. only operational at symbol- level time frames) time synchronization.
  • Examples also provide any one or more of: a new DL broadcast channel, a new DL control channel, or a DL reference signal. Any one or more of these may be advantageously used as a fast communications link loss detection mechanism.
  • Examples also provide a new method to maintain a low overhead control link with any secondary cells/eNBs put into use that advantageously allows for fast switching when the control link with the primary cell is lost (noting that, typically, if the control link is lost, whether data link is still connected does not matter much, because a UE will lose the connection anyway).
  • the term‘low-overhead’ may be considered to mean any system that uses a minimised (or near minimised) level of wireless resources available in respective the Radio Access Network (RAN) or RAT.
  • Examples also provide a UE-based fast cell switching procedure.
  • LTE terminology for the entities involved are used (e.g. UE, eNB, etc.). This is done mainly to identify a node from 4G/LTE which may share similar logical/conceptual functionalities in 5G, however, it will be appreciated that the actual (accurate) name for those nodes in a 5G system has not been finalized in 3GPP standards yet, and so the present disclosure is not limited in any way to the specific terms used.
  • signals are represented with lines. Some lines may be thicker, to indicate a greater number of constituent signal paths, and/or have arrows at one or more ends, to indicate a direction of information flow. Such indications are not intended to be limiting. Rather, the lines are used in connection with one or more exemplary embodiments to facilitate easier understanding of a circuit or a logical unit. Any represented signal, as dictated by design needs or preferences, may actually comprise one or more signals that may travel in either direction and may be implemented with any suitable type of signal scheme. Throughout the specification, and in the claims, the term "connected" means a direct electrical, mechanical, or magnetic connection between the things that are connected, without any intermediary devices.
  • Coupled means either a direct electrical, mechanical, or magnetic connection between the things that are connected or an indirect connection through one or more passive or active intermediary devices.
  • circuit or “module” may refer to one or more passive and/or active components that are arranged to cooperate with one another to provide a desired function.
  • signal may refer to at least one current signal, voltage signal, magnetic signal, or data/clock signal.
  • the transistors in various circuits, modules, and logic blocks are Tunneling FETs (TFETs).
  • Some transistors of various embodiments may comprise metal oxide semiconductor (MOS) transistors, which include drain, source, gate, and bulk terminals.
  • MOS metal oxide semiconductor
  • the transistors may also include Tri-Gate and FinFET transistors, Gate All Around Cylindrical Transistors, Square Wire, or Rectangular Ribbon Transistors or other devices implementing transistor functionality like carbon nanotubes or spintronic devices.
  • MOSFET symmetrical source and drain terminals i.e., are identical terminals and are interchangeably used here.
  • a TFET device on the other hand, has asymmetric Source and Drain terminals.
  • the phrases “A and/or B” and “A or B” mean (A), (B), or (A and B).
  • the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).
  • combinatorial logic and sequential logic discussed in the present disclosure may pertain both to physical structures (such as AND gates, OR gates, or XOR gates), or to synthesized or otherwise optimized collections of devices implementing the logical structures that are Boolean equivalents of the logic under discussion.
  • the terms“eNB,”“AP,”“5G eNB,” “mmWave eNB,”“mmWave small cell,” and“base station” may be substantially
  • “UE,”“STA,”“5G UE,” and “mmWave UE,” and“mobile equipment” may be substantially interchangeable.
  • an eNB and/or a UE may be calibrated for directional reciprocity. Accordingly, the same beam (and/or sector) may be both a best TX beam (and/or sector) and a best RX beam (and/or sector), and may have substantially the same Angle of Departure and Angle of Arrival. Moreover, some embodiments discussed below may employ a Time-Division Duplex (TDD) scheme, but other embodiments may employ another scheme such as a Frequency-Division Duplex (FDD) scheme.
  • TDD Time-Division Duplex
  • FDD Frequency-Division Duplex
  • Figure 1 shows the proposed multi-connectivity network architecture 100 according to examples.
  • the examples are described in terms of the entities and links used in the 4G/LTE standards, but the principles may equally be applied to any other similar function entities in existing or newly proposed 5G systems and mmWave systems in particular.
  • a UE 110 connectable to eNBs 120-140 via Uu links 115, where Uu is the name for the standard radio interface between the UE and the eNode B.
  • the eNBs are connect to one another, for example via X2 interfaces 135, where X2 is the name for the standard radio interface between the eNode Bs.
  • the eNBs are connected to the serving gateway (S- GW) 150 of the core network via respective S1 links 145.
  • the S-GW 150 is connected to the rest of the core network via the Packet Data Network (PDN) - Gateway, P-GW 160 via suitable links, such as the S5 or S8 links 155.
  • PDN Packet Data Network
  • a UE 110 may connect to multiple eNBs simultaneously, in this case eNBs #A 120, #B 130 and #C 140.
  • eNBs #A 120, #B 130 and #C 140 there is shown a multi- connectivity arrangement where there is a single anchor eNB (eNB #A 120) and two booster eNBs (eNBs #B 130 and #C 140).
  • the UE 110 only has one anchor eNB, and all other eNBs are booster, however other arrangements with multiples of each eNB type (anchor or booster), or a multiple of at least one type (e.g. boosters), may also be provided in other examples.
  • the anchor eNB #A 120 is responsible for all (i.e. both user-plane and control-plane) communications between the UE 110 and the core network (S-GW//P- GW/MME, etc.). This is shown in Figure 1 by the bold line for the central S1 interface between anchor eNB #A 120 and the S-GW 150.).
  • the booster eNBs (#B 130/#C 140) is/are only responsible for communications with UE in the RAN (i.e. responsible only for UE to eNB communications).
  • the UE 110 may have multiple RAN connections, where a RAN connection is a communications link from the UE to a (possibly different) eNB. Whilst the anchor eNB will always control the UE’s main link to the core network, the UE’s RAN communications links may be classified as either a primary communications link 180 or a secondary communications link 190.
  • the UE 110 uses its primary communications links 180 to send and receive data traffic, and its secondary communications links 190 as back-up in case if/when (any of its primary communications links are lost). If UE 110 has multiple primary communications links, UE’s 110 data traffic may be split over these primary communications links, i.e. a form of bearer splitting may be implemented. Where a secondary communications link is used by a UE 110, the respective user-plane/control-plane data may be sent to the anchor eNB 120 via a respective X2 link (i.e. forming an indirect link from the UE 110 to the core network)
  • a way to view the newly proposed system of Figure 1, as described above, is that it decouples the traditional anchor functionality to connect to the core network from the traditional anchor functionality of providing the air interface to the UE (as per the usual anchor-booster type arrangement).
  • multiple secondary communications (air interface) links between the UE 110 and respective (secondary, booster type) eNBs e.g. #B 130, #C 140
  • Another way to view this is that there is a single point/path of entry to/from the UE 110 from the core network point of view, but multiple points/paths of entry to/from the UE 110, from the UE point of view.
  • Figure 2 shows an example of a possible end to end (e2e) user-plane protocol stack 200 for the proposed multi-connectivity network architecture of Figure 1.
  • a UE 110 connected to three eNBs– an anchor eNB #A 120, and two booster eNBs - #B 130 and #C 140.
  • the anchor eNB #A 120 acts as the UE’s main/only link to the core network (i.e. all other UE traffic, which may be served in the RAN by the other booster eNBs, must still route through this anchor eNB).
  • the booster eNBs - #B 130 and #C 140 act to only provide RAN access to the UE and sends all the UE traffic to/from the core network via the anchor eNB #A 120 (via, e.g. the X2 interfaces 135).
  • the UE connects to each of the eNBs via a respective one of the usual UE-eNB interfaces (often referenced the Uu interface) 115.
  • the eNBs connect to each other over the usual eNB to eNB interfaces (often referenced the X2 interface).
  • a new multi- connectivity control entity in the protocol stack which is being called the Multi-Connectivity Convergence Protocol.
  • This is shown, for the UE (for user-plane portion) as entity MCCP-u 111.
  • entity MCCP-u 111 This is located in the UE’s protocol stack between the IP layer, and the PDCP layer for each connection in use (three are shown in this figure, but there could be more or less in other implementations).
  • a similar complementary eNB-side MCCP-u entity 121 is shown in the anchor eNB #A 120.
  • the user-plane i.e. user data
  • the rest of the disclosed protocol entities e.g. the PDCP, RLC, PHY/MAC, GTP-U, UDP and IP entities all operate in their usual way, and are therefore not described in any further detail here.
  • Figure 3 shows an example of a possible end to end (e2e) control-plane protocol stack 300 for the proposed multi-connectivity network architecture of Figure 1.
  • each of the eNBs and the UE 110 now also include a Multi- Connectivity Convergence Protocol control-plane layer entity (MCCP-c), which are shown as items UE MCCP-c 112, eNB #A MCCP-c 122, eNB #B MCCP-c 132, and eNB #C MCCP-c 142, respectively. These are provided at each location, because control of data and control flow may be carried out (or at least implemented) at any or all of their locations.
  • the rest of the disclosed protocol entities e.g. the NAS, PDCP, RLC, PHY/MAC, GTP-U, UDP, IP, and RRC entities all operate in their usual way, and are therefore again not described in any further detail here.
  • the UE 110 may send or receive data traffic via its anchor eNB 120 directly, or via its booster eNB (130, 150), which then communicate with the anchor eNB 20 over the X2 interface 135.
  • the proposed multi-connectivity convergence u-plane protocol (MCCP-u) operates above/over the individual RAN stacks (above PDCP), and it may manage how a UE’s 110 data traffic are routed over multiple primary links 180.
  • all communications links between the UE and the respective eNBs i.e. both primary and secondary Uu links
  • support for above PDCP bearer splitting in the proposed MCCP may be provided.
  • neighboring eNBs may coordinate with each other, for example via the X2 Application Protocol, that may be run over the X2 interface between eNBs.
  • the eNB should broadcast the parameters (k, N, T offset ) to the UE 110 as part of the system information sent in the DL control channel, so that the UE 110 knows in which superframe/frame/subframe a respective synchronization signal (e.g. Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS)/ Sector Level Sweep (SLS) signal) may be transmitted in its neighboring cells.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • SLS Sector Level Sweep
  • Tight synchronization may be defined as any timing difference between cells/eNBs of a symbol or less, such as 10% of a symbol transmission time.
  • T offset may be configured to be a value > 0 such that the UE 110 can perform SLS for different cells at different times, i.e. this may provide a form of Time Division Multiplex (TDM) of the SLS process.
  • TDM Time Division Multiplex
  • N determines the maximum number of eNBs that a UE 110 can connect to simultaneously.
  • Figure 4 shows a timeline for how PSS, SSS, and SLS signals may be allocated in neighboring cells.
  • SLS system level sweep
  • UE receiveriver
  • eNB transmitter
  • PSS 422/432/442 and SLS 428/438/448 are the eNB (transmitter) sector sweep signals (TXSS)
  • SSS 424/434/444 and SLS 426/436/446 are UE
  • RXSS sector sweep signals
  • the PSS and SSS signals are used for initial acquisition, and the SLS signal are used after initial acquisition is completed successfully and respective UE is attached.
  • all the PSS signals e.g. PSS 422/432/442
  • the SSS signals e.g. SSS 424/434/444.
  • the UE RXSS would occur during SSS and eNB TXSS would occur during PSS.
  • all PSS or SSS in neighboring cells occurs at the same time, while respective SLS occurs with a fixed time offset, T offset 435 (or multiples thereof for higher numbered cells, e.g.2T offset 445).
  • PSS/SSS signals are only needed during initial acquisition, and this is why they may occur in the same (e.g. first) subframe.
  • SLS 528/538/548 are eNB TXSS, while SSS 524/534/544 and SLS
  • 526/536/546 are UE RXSS.
  • Figure 5 shows a timeline for offsetting the PSS, SSS, and SLS signals in neighboring cells.
  • T offset 535 (or multiples thereof for higher numbered cells, e.g. 2T offset 545), is simply being applied to the entire frame, which is a simpler arrangement to that shown in Figure 4.
  • the Physical Downlink Control Channel occupies the first few symbols of a subframe, and so it can be used by the UE 110 to detect communications link loss.
  • the eNB may not be able to send the PDCCH sufficiently often to prevent a link loss being assumed detected at the UE 110 when using the PDCCH alone to detect communications link loss.
  • the eNB may not be able to send the PDCCH over all its sectors simultaneously due to the link budget (i.e. wireless resources) constraints.
  • some examples may provide that the eNB may use all its RF chains together to send the PDCCH signal over each sector, one at a time.
  • the eNB may have two sectors: A and B, and two UEs: a and b.
  • UE #a may connect to eNB via sector #A;
  • UE #b may connect to eNB via sector #B.
  • the eNB can only send the PDCCH over sector A or B at a time, but not both.
  • eNB will send the PDCCH over sector #A in consecutive frames to schedule UE #a’s traffic.
  • eNB won’t send the PDCCH over sector #B for a period of time, so that the UE may mistakenly detect communications link loss if it only relies on the receipt of the PDCCH.
  • a new downlink broadcast channel (or another control channel, such as a Beam Reference Signal (BRS)) may be used.
  • BRS Beam Reference Signal
  • the sBCH may be allocated to the available wireless resources, such as subframe, after the PDCCH (if indeed it is allocated).
  • the actual allocation of the sBCH in time and frequency within a subframe may be configured through the (e.g. broadcasted) system information.
  • the length of the sBCH may vary, but, the maximum may be fixed (denoted as N), and provided to UEs as part of system information.
  • the sBCH may indicate the Cell ID and other resource parameter, such as the relevant sector index.
  • the relevant eNB may send the same symbol repeatedly, for example over the selected sectors.
  • T sBCH the sBCH/BRS interval
  • K the number of symbols in the PDCCH
  • N the maximum number of symbols of the sBCH/BRS
  • Figure 6 shows how the sBCH may be allocated 600 in a subframe with three sectors: A, B, and C.
  • PDCCH 610 is sent over sector #A to schedule the UE’s traffic on this sector (i.e. the PDCCH is only to schedule for the sector which it is using) and the sBCH 620 is sent over sectors #B and #C for link loss detection.
  • Step 1 If the primary eNB #A 120 has not sent the PDCCH or sBCH over a sector in the last T sBCH subframes, the eNB 120 may send the PDCCH over the sector if nothing prevents it from doing so; otherwise, the eNB 120 may send sBCH over the sector after the first K symbols, and the PDCCH (sent over a different sector) may also indicate that the first n symbols (where n ⁇ N) after the PDCCH (i.e. after the end of the PDCCH) is reserved for the sBCH;
  • Step 2 the UE 110 receives the first K symbols of every subframe for PDCCH from its respective primary eNBs. If the UE 110 does not receive these first K symbols of every subframe for PDCCH from its primary eNBs correctly, it may continue to receive the next N symbols for the sBCH. If the UE 110 has not received the PDCCH or sBCH from its primary eNB in last m x T sBCH subframes, then the UE 110 can assume its connection to the respective primary eNB is lost.
  • the primary eNB #A 120 may broadcast (m, K, N, T sBCH ) to the UE 110 as part of system information.
  • a new enhanced (cell-specific) Reference Signal may be persistently allocated for every Transmit Time Interval (TTI).
  • TTI Transmit Time Interval
  • the eRS’s time and frequency allocation information may also be provided in the system information, and may be mapped to a sector index, and the eRS itself may also carry the Cell ID information.
  • the UE 110 can detect communications link loss directly by measuring eRS. If the UE has not received eRS from its last m x T eRS subframes, then the UE 110 can assume its connection to the respective primary eNB is lost.
  • pSR persistent Scheduling Request allocation for secondary control link
  • the UE 110 detects link loss in its primary cell (i.e. as being served by eNB #A 120)
  • the UE 110 needs to switch over to one of its secondary cells (e.g. as served by eNBs #B 130 or #C 140) as quickly as possible.
  • This may be achieved using a light-weight scheduling request procedure as now described, according to examples of the present disclosure.
  • the proposed light-weight scheduling request procedure may provide the advantage that the UE 110 may maintain UpLink (UL) synchronization with its secondary cell, and also send out the request to switch the primary cell via the secondary control link.
  • the UE’s 110 persistent Scheduling Request (pSR) in the secondary cell may also be persistently allocated.
  • the pSR may be sent every Transmit Time Interval (TTI), although in other examples the pSR may be sent less regularly, e.g. at/on intervals of more than one TTI. Altering the regularity of sending the pSR may affect time to detection, but less regular sending is more wireless resource efficient. Thus, the pSR transmission interval may be use-case specific.
  • TTI Transmit Time Interval
  • the UE’s 110 primary eNB may coordinate with its secondary eNB (e.g. eNB #B 130) to reconfigure the UE’s 110 pSR in the secondary cell.
  • a new way to indicate how the pSR is allocated may be provided, which can be used for a normal subframe or a special subframe in which Downlink (DL) synchronization or a broadcast channel (e.g. the PSS/SSS/ Broadcast Channel (BCH)) occupies the last few symbols of a subframe.
  • DL Downlink
  • BCH Broadcast Channel
  • dpSR-REQ the offset in terms of symbols between the first symbols of the persistent Scheduling Request message sent on the Uplink (i.e. pSR REQ message (UL)) and the last symbol that can be used for DL/UL allocation (excluding PSS/SSS/BCH allocation) in the respective subframe;
  • d pSR-RSP the offset in terms of symbols between the first symbols of the pSR REQ message (UL) and the first symbol of the pSR RSP message (DL);
  • T pSR the cycle time of the persistent Scheduling Request (in terms of
  • FIG. 7 shows how the pSR-REQ and pSR-RSP messages may be allocated in a subframe, around the PDCCH, PSS/SSS/BCH, etc of a special subframe, while Figure 8 shows how the pSR-REQ and pSR-RSP messages may be allocated in a normal subframe.
  • the persistent Scheduling Request is scheduling in a persistent place in the respective subframe, set by the parameters: d pSR-REQ 730, d pSR-RSP 740, and T pSR .
  • the persistent scheduling seeks to place the pSR at a point referenced from the last symbol that can be used for UE-specific resource allocation, which is from the end of the respective subframe (for normal subframe), or from the last N + 1 symbol of the subframe if the last N symbols are used for PSS, SSS, BCH, or SLS, or any other signals (for special subframe)
  • the UE’s 110 primary eNB e.g.
  • eNB #A 120 may coordinate with a secondary eNB(s) (e.g. eNB #B 130 or #C 140) to reconfigure UE’s pSR (d pSR-REQ, d pSR-RSP, T pSR ).
  • a secondary eNB(s) e.g. eNB #B 130 or #C 140
  • Figure 9 shows a high level flow diagram of a method 900 of detecting
  • the method may be preceded by a respective primary eNB sending 905 the sBCH broadcast parameters discussed above to the UE, for example in the system information.
  • the UE can seek to detect whether its (respective, or at least a one of its respective) primary communications link(s) with the primary eNB has been lost (i.e. blocked) through use of the PDCCH, sBCH or the eRS signals, as discussed in detail above.
  • the loss of a communications link may be determined by the incorrect or non- receipt of the respective control signal (PDCCH, sBCH or eRS). If this happens, the result of the‘correct receipt test’ is negative 925, so the method moves to step 930, which determines the respective primary communications link is lost, and so instigates the fast switching cell procedure, for example, as discussed in detail below, with respect to Figure 10.
  • the primary connection is OK 920 and may continue to be used.
  • the test 910 may then repeat in due course.
  • Figure 10 shows, in more detail, some key steps in a method 1000 for the UE 110 to switch its primary cell, according to a FCS procedure according to some example embodiments.
  • the UE 110 is connected to one anchor eNB (#A) 120 (i.e. the eNB currently primary) and two booster eNBs– eNB #B 130 (i.e. a first currently secondary eNB) and eNB #C 140 (i.e. a second currently secondary eNB), and that the secondary eNB that will be made the primary is eNB #B 130.
  • the anchor eNB (#A) 120 is primary
  • the booster eNB (#B) 130 is secondary.
  • the UE 110 is configured with the periodic pSR 1010 from eNB #B 130 so that it can maintain UL synchronization in the secondary cell while transferring data in the primary cell.
  • the UE transfers data in the primary cell using communications links provided to the UE by the primary cell eNB.
  • the periodicity of the periodic pSR is set by the parameter T pSR .
  • the PDCCH/sBCH/eRS are transmitted 1020 by the primary eNB #A 120 and correctly received by the UE 110. This is to say the UE 110 continues to receive the PDCCH or the sBCH, or the eRS, from its primary eNB (#A) 120 and the pSR from the secondary eNB (#B) 130.
  • the primary communications links between the UE and the primary eNB are considered lost or broken. This is shown by the crosses 1025 for the second and third PDCCH/sBCH/eRS transmissions 1020. This may be carried out within a time frame defined by m x T sBCH , as shown, and discussed in detail above.
  • the UE 110 detects communications link loss, it may trigger the FCS procedure 1040 (see more details in the above section 3).
  • the UE 110 continues to receive the pSR signals from the secondary cell eNB, but can only act to request a transfer of the data being sent over the (now lost) primary communication link to a working‘hot swap’ secondary communications link provided by a secondary eNB (e.g. eNB #B 130) at the next allocated pSR transmission.
  • a secondary eNB e.g. eNB #B 130
  • the UE 110 selects one of its secondary eNBs (in this case, as noted above, eNB #B 130) as its new primary eNB based on for example received signal strength or other measurements, and go to step 4.
  • eNB #B 130 the secondary eNBs
  • the UE 110 can send out the FCS REQ message (e.g. as part of pSR-REQ) to the selected secondary eNB (eNB #B 130) at 1050.
  • the FCS REQ message e.g. as part of pSR-REQ
  • the selected secondary eNB eNB #B 130
  • the selected eNB (eNB #B 130) will respond to the FCS REQ message received from the UE 110 with the FCS RSP message (e.g. as part of pSR-RSP) to confirm the switching at 1060.
  • the old secondary eNB #B 130 is now the new primary eNB.
  • the new primary eNB will now be sent to the new primary eNB, and that may be routed to the core-network via the anchor eNB if the new primary is not the anchor eNB.
  • the new primary eNB (eNB #B 130) will send the FCS notification message to the anchor eNB (eNB #A 120) at 1070, so that it can update its information and start to forward DL traffic to the new primary eNB (eNB #B 130), e.g. via the X2 interface.
  • the new primary eNB (eNB #B 130) may initiate a sector selection procedure so that the UE 110 can select the most appropriate sector of eNB #b 130 to use for data transfer in the new primary cell.
  • selection methodology may include, but not be limited to: cell capacity, cell signal quality, cell signal strength, cell distance, cell frequency, etc.
  • Figure 11 illustrates an eNB and a UE, in accordance with some embodiments of the disclosure.
  • Figure 11 includes block diagrams of an eNB 1110 and a UE 1130 which are operable to co-exist with each other and other elements of an LTE network. High-level, simplified architectures of eNB 1110 and UE 1130 are described so as not to obscure the embodiments. It should be noted that in some embodiments, eNB 1110 may be a stationary non-mobile device.
  • eNB 1110 is coupled to one or more antennas 1105, and UE 1130 is similarly coupled to one or more antennas 1125.
  • eNB 1110 may incorporate or comprise antennas 1105, and UE 1130 in various embodiments may incorporate or comprise antennas 1125.
  • antennas 1105 and/or antennas 1125 may comprise one or more directional or omni-directional antennas, including monopole antennas, dipole antennas, loop antennas, patch antennas, microstrip antennas, coplanar wave antennas, or other types of antennas suitable for transmission of RF signals.
  • antennas 1105 are separated to take advantage of spatial diversity.
  • eNB 1110 and UE 1130 are operable to communicate with each other on a network, such as a wireless network.
  • eNB 1110 and UE 1130 may be in communication with each other over a wireless communication channel 1150, which has both a downlink path from eNB 1110 to UE 1130 and an uplink path from UE 1130 to eNB 1110.
  • eNB 1110 may include a physical layer circuitry 1112, a MAC (media access control) circuitry 1114, a processor 1116, a memory 1118, and a hardware processing circuitry 1120.
  • MAC media access control
  • physical layer circuitry 1112 includes a transceiver 1113 for providing signals to and from UE 1130.
  • Transceiver 1113 provides signals to and from UEs or other devices using one or more antennas 1105.
  • MAC circuitry 1114 controls access to the wireless medium.
  • Memory 1118 may be, or may include, a storage media/medium such as a magnetic storage media (e.g., magnetic tapes or magnetic disks), an optical storage media (e.g., optical discs), an electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory-based storage media), or any tangible storage media or non-transitory storage media.
  • Hardware processing circuitry 1120 may comprise logic devices or circuitry to perform various operations.
  • processor 1116 and memory 1118 are arranged to perform the operations of hardware processing circuitry 1120, such as operations described herein with reference to logic devices and circuitry within eNB 1110 and/or hardware processing circuitry 1120.
  • eNB 1110 may be a device comprising an application processor, a memory, one or more antenna ports, and an interface for allowing the application processor to communicate with another device.
  • UE 1130 may include a physical layer circuitry 1132, a MAC circuitry 1134, a processor 1136, a memory 1138, a hardware processing circuitry 1140, a wireless interface 1142, and a display 1144.
  • a physical layer circuitry 1132 may include a physical layer circuitry 1132, a MAC circuitry 1134, a processor 1136, a memory 1138, a hardware processing circuitry 1140, a wireless interface 1142, and a display 1144.
  • a person skilled in the art would appreciate that other components not shown may be used in addition to the components shown to form a complete UE.
  • physical layer circuitry 1132 includes a transceiver 1133 for providing signals to and from eNB 1110 (as well as other eNBs). Transceiver 1133 provides signals to and from eNBs or other devices using one or more antennas 1125.
  • MAC circuitry 1134 controls access to the wireless medium.
  • Memory 1138 may be, or may include, a storage media/medium such as a magnetic storage media (e.g., magnetic tapes or magnetic disks), an optical storage media (e.g., optical discs), an electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory- based storage media), or any tangible storage media or non-transitory storage media.
  • Wireless interface 1142 may be arranged to allow the processor to communicate with another device.
  • Display 1144 may provide a visual and/or tactile display for a user to interact with UE 1130, such as a touch-screen display.
  • Hardware processing circuitry 1140 may comprise logic devices or circuitry to perform various operations.
  • processor 1136 and memory 1138 may be arranged to perform the operations of hardware processing circuitry 1140, such as operations described herein with reference to logic devices and circuitry within UE 1130 and/or hardware processing circuitry 1140.
  • UE 1130 may be a device comprising an application processor, a memory, one or more antennas, a wireless interface for allowing the application processor to communicate with another device, and a touch-screen display.
  • eNB 1110 and UE 1130 are each described as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements and/or other hardware elements.
  • the functional elements can refer to one or more processes operating on one or more processing elements. Examples of software and/or hardware configured elements include Digital Signal Processors (DSPs), one or more microprocessors, DSPs, Field-Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Radio-Frequency Integrated Circuits (RFICs), and so on.
  • DSPs Digital Signal Processors
  • FPGAs Field-Programmable Gate Arrays
  • ASICs Application Specific Integrated Circuits
  • RFICs Radio-Frequency Integrated Circuits
  • An eNB may include various hardware processing circuitries discussed herein, which may in turn comprise logic devices and/or circuitry operable to perform various operations.
  • eNB 1110 (or various elements or components therein, such as hardware processing circuitry 1120, or combinations of elements or components therein) may include part of, or all of, these hardware processing circuitries.
  • one or more devices or circuitries within these hardware processing circuitries may be implemented by combinations of software-configured elements and/or other hardware elements.
  • processor 1116 and/or one or more other processors which eNB 1110 may comprise
  • memory 1118 and/or other elements or components of eNB 1110 (which may include hardware processing circuitry 1120) may be arranged to perform the operations of these hardware processing circuitries, such as operations described herein with reference to devices and circuitry within these hardware processing circuitries.
  • processor 1116 (and/or one or more other processors which eNB 1110 may comprise) may be a baseband processor.
  • a UE may include various hardware processing circuitries discussed herein, which may in turn comprise logic devices and/or circuitry operable to perform various operations.
  • UE 1130 (or various elements or components therein, such as hardware processing circuitry 1140, or combinations of elements or components therein) may include part of, or all of, these hardware processing circuitries.
  • one or more devices or circuitries within these hardware processing circuitries may be implemented by combinations of software-configured elements and/or other hardware elements.
  • processor 1136 (and/or one or more other processors which UE 1130 may comprise), memory 1138, and/or other elements or components of UE 1130 (which may include hardware processing circuitry 1140) may be arranged to perform the operations of these hardware processing circuitries, such as operations described herein with reference to devices and circuitry within these hardware processing circuitries.
  • processor 1136 (and/or one or more other processors which UE 1130 may comprise) may be a baseband processor.
  • Various methods described herein may relate to eNB 1110 and hardware processing circuitry 1120. Although the actions in the herein described methods are shown in a particular order, the order of the actions can be modified. Thus, the illustrated embodiments can be performed in a different order, and some actions may be performed in parallel. Some of the actions and/or operations listed may be optional in accordance with certain
  • machine readable storage media may have executable instructions that, when executed, cause eNB 1110 and/or hardware processing circuitry 1120 to perform an operation comprising any of the described methods.
  • Such machine readable storage media may include any of a variety of storage media, like magnetic storage media (e.g., magnetic tapes or magnetic disks), optical storage media (e.g., optical discs), electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory- based storage media), or any other tangible storage media or non-transitory storage media.
  • an apparatus may comprise means for performing various actions and/or operations of the methods.
  • UE 1130 and hardware processing circuitry 1140 are also described herein.
  • the actions may be shown in a particular order, the order of the actions can be modified.
  • the illustrated embodiments can be performed in a different order, and some actions may be performed in parallel.
  • Some of the actions and/or operations carried out by the UE are optional in accordance with certain embodiments.
  • the numbering of the actions presented is for the sake of clarity and is not intended to prescribe an order of operations in which the various actions must occur.
  • machine readable storage media may have executable instructions that, when executed, cause UE 1130 and/or hardware processing circuitry 1140 to perform an operation comprising any of the disclosed methods.
  • Such machine readable storage media may include any of a variety of storage media, like magnetic storage media (e.g., magnetic tapes or magnetic disks), optical storage media (e.g., optical discs), electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory-based storage media), or any other tangible storage media or non-transitory storage media.
  • FIG. 12 shows, for one embodiment, example components of an electronic device 1200.
  • the electronic device 1200 may be, implement, be incorporated into, or otherwise be a part of a user equipment (UE), an evolved NodeB (eNB), or another network component (e.g. a network component corresponding to a network virtualization device and/or a software defined network device).
  • the electronic device 1200 may include application circuitry 1210, baseband circuitry 1220, Radio Frequency (RF) circuitry 1230, front-end module (FEM) circuitry 1240 and one or more antennas 1250, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • the application circuitry 1210 may include one or more application processors.
  • the application circuitry 1210 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.
  • the baseband circuitry 1220 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 1220 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 1230 and to generate baseband signals for a transmit signal path of the RF circuitry 1230.
  • Baseband processing circuitry 1220 may interface with the application circuitry 1210 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1230.
  • the baseband circuitry 1220 may include a second generation (2G) baseband processor 1221, third generation (3G) baseband processor 1222, fourth generation (4G) baseband processor 1223, and/or other baseband processor(s) 1224 for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 1220 e.g., one or more of baseband processors 1221-1224
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 1220 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 1220 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 1220 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC) elements and/or the disclosed MCCP layer protocol.
  • EUTRAN evolved universal terrestrial radio access network
  • a central processing unit (CPU) 1225 of the baseband circuitry 1220 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP, RRC and/or MCCP Layers.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 1226.
  • the audio DSP(s) 1226 may be include elements for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC) elements and/or the disclosed MCCP layer protocol.
  • compression/decompression and echo cancellation may include other suitable processing elements in other embodiments.
  • the baseband circuitry 1220 may further include memory/storage 1227.
  • the memory/storage 1227 may be used to load and store data and/or instructions for operations performed by the processors of the baseband circuitry 1220.
  • Memory/storage for one embodiment may include any combination of suitable volatile memory and/or non- volatile memory.
  • the memory/storage 1227 may include any combination of various levels of memory/storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache , buffers, etc.
  • ROM read-only memory
  • DRAM dynamic random access memory
  • the memory/storage 1227 may be shared among the various processors or dedicated to particular processors.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 1220 and the application circuitry 1210 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 1220 may provide for
  • the baseband circuitry 1220 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 1220 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 1230 may enable communication with wireless networks
  • the RF circuitry 1230 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 1230 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1240 and provide baseband signals to the baseband circuitry 1220.
  • RF circuitry 1230 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1220 and provide RF output signals to the FEM circuitry 1240 for transmission.
  • the RF circuitry 1230 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 1230 may include mixer circuitry 1231, amplifier circuitry 1232 and filter circuitry 1233.
  • the transmit signal path of the RF circuitry 1230 may include filter circuitry 1233 and mixer circuitry 1231.
  • RF circuitry 1230 may also include synthesizer circuitry 1234 for synthesizing a frequency for use by the mixer circuitry 1231 of the receive signal path and the transmit signal path.
  • the mixer circuitry 1231 of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 1240 based on the synthesized frequency provided by synthesizer circuitry 1234.
  • the amplifier circuitry 1232 may be configured to amplify the down-converted signals and the filter circuitry 1233 may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down- converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 1220 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 1231 of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 1231 of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1232 to generate RF output signals for the FEM circuitry 1240.
  • the baseband signals may be provided by the baseband circuitry 1220 and may be filtered by filter circuitry 1233.
  • the filter circuitry 1233 may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • LPF low-pass filter
  • the mixer circuitry 1231 of the receive signal path and the mixer circuitry 1231 of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively.
  • the mixer circuitry 1231 of the receive signal path and the mixer circuitry 1231 of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 1231 of the receive signal path and the mixer circuitry 1231 may be arranged for direct
  • the mixer circuitry 1231 of the receive signal path and the mixer circuitry 1231 of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 1230 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1220 may include a digital baseband interface to communicate with the RF circuitry 1230.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 1234 may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 1234 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 1234 may be configured to synthesize an output frequency for use by the mixer circuitry 1231 of the RF circuitry 1230 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1234 may be a fractional N/N+1 synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 1220 or the applications processor 1210 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1210.
  • Synthesizer circuitry 1234 of the RF circuitry 1230 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 1234 may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 1230 may include an IQ/polar converter.
  • FEM circuitry 1240 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1250, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1230 for further processing.
  • FEM circuitry 1240 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1230 for transmission by one or more of the one or more antennas 1250.
  • the FEM circuitry 1240 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1230).
  • the transmit signal path of the FEM circuitry 1240 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1230), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1250).
  • PA power amplifier
  • network interface controller (NIC) circuitry 1260 may include one or more transmission and reception (TX/RX) signal paths, which may connect to one or more data packet networks via network interface circuitry 1265.
  • TX/RX transmission and reception
  • NIC circuitry 1260 may connect to the data packet networks via multiple network interface circuitries 1265.
  • the NIC circuitry 1260 may support one or more data link Layer standards, such as Ethernet, Fiber, Token Ring, asynchronous transfer mode (ATM), and/or any other suitable data link Layer standard(s).
  • each network element that the electronic device 1200 may connect to may contain a same or similar network interface circuitry 1265.
  • RAN radio access network
  • NIC circuitry 1260 may include, or may be associated with processing circuitry, such as one or more single-core or multi-core processors and/or logic circuits, to provide processing techniques suitable to carry out communications according to the one or more data link Layer standards used by the NIC circuitry.
  • processing circuitry such as one or more single-core or multi-core processors and/or logic circuits, to provide processing techniques suitable to carry out communications according to the one or more data link Layer standards used by the NIC circuitry.
  • the electronic device 1200 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.
  • additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.
  • the electronic device of Figure 12 may be configured to perform one or more processes, techniques, and/or methods as described herein, or portions thereof.
  • Figure 13 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 13 shows a diagrammatic
  • hardware resources 1300 including one or more processors (or processor cores) 1310, one or more memory/storage devices 1320, and one or more communication resources 1330, each of which are communicatively coupled via a bus 1340.
  • the processors 1310 may include, for example, a processor 1312 and a processor 1314.
  • the memory/storage devices 1320 may include main memory, disk storage, or any suitable combination thereof.
  • the communication resources 1330 may include interconnection and/or network interface components or other suitable devices to communicate with one or more peripheral devices 1304 and/or one or more databases 1306 via a network 1308.
  • the communication resources 1330 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low
  • Instructions 1350 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1310 to perform any one or more of the methodologies discussed herein.
  • the instructions 1350 may reside, completely or partially, within at least one of the processors 1310 (e.g., within the processor’s cache memory), the memory/storage devices 1320, or any suitable combination thereof.
  • any portion of the instructions 1350 may be transferred to the hardware resources 1300 from any combination of the peripheral devices 1304 and/or the databases 1306. Accordingly, the memory of processors 1310, the memory/storage devices 1320, the peripheral devices 1304, and the databases 1306 are examples of computer-readable and machine-readable media.
  • examples of the present disclosure may be applied to alternate mmWave access systems such as WiGig/802.11ay or potentially to any other massive Multiple-Input-Multiple-Output (MIMO) systems, particularly those utilizing directional acquisition/any signals (control or data) of a directional nature.
  • MIMO Multiple-Input-Multiple-Output
  • a new Multi- Connectivity network architecture and c-plane/u-plane protocol stack operable to support an efficient“hot standby” configuration between primary and secondary cells, the“hot standby” configuration allowing for fast transitions of control and data traffic between cells upon communications link loss of a main (i.e. primary) communications link.
  • a new broadcast channel e.g. shortened BCH
  • eRS enhanced reference signal
  • Specific examples may utilize more than one of the new broadcast channels or reference signals, or even the PDCCH to detect communications link loss.
  • PSS/SSS/SLS/BCH i.e. normal or special subframes. According to examples described herein, there may be provided a new SR
  • Examples of the present disclosure may be used in future 3GPP standards (R14 and beyond).
  • first embodiment may be combined with a second embodiment anywhere the particular features, structures, functions, or characteristics associated with the two embodiments are not mutually exclusive.
  • DRAM Dynamic RAM
  • Example 1 may include an apparatus of a User Equipment (UE) operable to communicate with an Evolved Node-B (eNB) on a wireless network, comprising: one or more processors to: maintain a plurality of radio access network communications links between the UE and at least two eNBs of a radio access network of the wireless network, wherein at least a first eNB is an anchor eNB and wherein at least a second eNB is a booster eNB, said plurality of radio access network communications links between the UE and a radio access network of the wireless network comprising at least one primary communications link and at least one secondary communications link; and switch between actively using the at least one primary communications link for sending and receiving data of the UE to actively using the at least one secondary communications link for sending and receiving data of the UE when the at least one primary communications link is determined to be lost; wherein the anchor eNB is operable to provide both communications between the UE and a core network serving the wireless network, and communications between the UE and a radio access network providing the wireless network
  • Example 2 may include the apparatus of example 1 or any other example herein, wherein the anchor eNB provides both user-plane and control-plane communications between the UE and the core network.
  • Example 3 may include the apparatus of example 1 or 2, or any other example herein, wherein the booster eNB provides both user-plane and control-plane communications between the UE and the anchor eNB.
  • Another example may include the apparatus of any other example, wherein the booster eNB provides both user-plane and control-plane communications between the UE and the core network.
  • Example 4 may include the apparatus of any of examples 1 to 3, or any other example herein, wherein the booster eNB communicates with the anchor eNB over an eNB to eNB communications link interface, optionally an X2 interface.
  • Example 5 may include the apparatus of any of examples 1 to 4, or any other example herein, wherein the UE maintains at least two primary communications links, and wherein the one or more processors are further to split traffic to be sent between the at least two primary communications links.
  • Example 6 may include the apparatus of example 5, or any other example herein, wherein to split traffic to be sent between the at least two primary communications links comprises providing at least two bearer links, wherein a bearer link is assigned to each primary communications link.
  • Example 7 may include the apparatus of any of examples 1 to 6, or any other example herein, wherein the one or more processors are further to: provide a multi-connectivity convergence protocol (MCCP) stack entity, wherein the MCCP stack entity operates above individual radio access network protocol sub-stacks, and wherein the MCCP stack entity manages how the UE data traffic is routed over the primary and secondary communications links.
  • MCCP multi-connectivity convergence protocol
  • Example 8 may include the apparatus of any of examples 1 to 7, or any other example herein, wherein to operate above individual radio access network protocol sub-stacks comprises operating above the packet data convergence protocol (PDCP) stack entity of each wireless communications link(s) operating in the UE.
  • PDCP packet data convergence protocol
  • Example 9 may include the apparatus of any of examples 1 to 8, or any other example herein, wherein each wireless communications link(s) operating in the UE comprises an independent user-plane and control-plane stack to provide operation independent from each other wireless communications link(s) operating in the UE.
  • Example 10 may include the apparatus of any of examples 1 to 9, or any other example herein, wherein the one or more processors are further to provide PDCP bearer splitting by the MCCP stack entity.
  • Example 11 may include the apparatus of any of examples 7 to 10, or any other example herein, wherein the MCCP stack entity comprises a user-plane portion, MCCP-u, and a control-plane portion, MCCP-c.
  • Example 12 may include a UE device comprising an application processor, a memory, one or more antennas, a wireless interface for allowing the application processor to communicate with another device, and a touch-screen display, the UE device including the apparatus of any of examples 1 to 11.
  • Example 13 may include a machine readable storage media having machine executable instructions that, when executed, cause one or more processors to perform an operation in a User Equipment (UE) operable to communicate with an Evolved Node-B (eNB) on a wireless network, comprising: maintaining a plurality of radio access network communications links between the UE and at least two eNBs of a radio access network of the wireless network, wherein at least a first eNB is an anchor eNB and wherein at least a second eNB is a booster eNB, said plurality of radio access network communications links between the UE and a radio access network of the wireless network comprising at least one primary
  • UE User Equipment
  • eNB Evolved Node-B
  • Example 14 may include the machine readable storage media of example 13, or any other example herein, further comprising: maintaining at least two primary communications links; and splitting traffic to be sent between the at least two primary communications links.
  • Example 15 may include the machine readable storage media of example 13 or 14, or any other example herein, further comprising providing at least two bearer links, wherein a bearer link is assigned to each primary communications link.
  • Example 16 may include the machine readable storage media of any of examples 13 to 15, or any other example herein, further comprising: providing a multi-connectivity convergence protocol (MCCP) stack entity operating above individual radio access network protocol sub- stacks; and managing how the UE data traffic is routed over the primary and secondary communications links using the MCCP stack entity.
  • MCCP multi-connectivity convergence protocol
  • Example 17 may include the machine readable storage media of example 16, or any other example herein, wherein operating above individual radio access network protocol sub-stacks comprises operating above the packet data convergence protocol (PDCP) stack entity of each wireless communications link(s) provided in the UE.
  • PDCP packet data convergence protocol
  • Example 18 may include the machine readable storage media of any of examples 13 to 17, or any other example herein, further comprising providing an independent user-plane and control-plane stack for each independent wireless communications link(s) provided in the UE.
  • Example 19 may include the machine readable storage media of any of examples 13 to 18, or any other example herein, further comprising providing PDCP bearer splitting by the MCCP stack entity.
  • Example 20 may include the machine readable storage media of any of examples 16 to 18, wherein the MCCP stack entity comprises a user-plane portion, MCCP-u, and a control-plane portion, MCCP-c.
  • Example 21 may include a method in a User Equipment (UE) operable to communicate with an Evolved Node-B (eNB) on a wireless network, comprising: connecting and
  • At least a first eNB is an anchor eNB and wherein at least a second eNB is a booster eNB; maintaining a plurality of radio access network communications links between the UE and a radio access network of the wireless network, said plurality of radio access network communications links between the UE and a radio access network of the wireless network comprising at least one primary
  • Example 22 may include the method of example 21, or any other example herein, further comprising: maintaining at least two primary communications links; and splitting traffic to be sent between the at least two primary communications links.
  • Example 23 may include the method of example 21 or 22, or any other example herein, further comprising providing at least two bearer links, wherein a bearer link is assigned to each primary communications link.
  • Example 24 may include the method of any of examples 21 to 23, or any other example herein, further comprising: providing a multi-connectivity convergence protocol (MCCP) stack entity operating above individual radio access network protocol sub-stacks; and managing how the UE data traffic is routed over the primary and secondary communications links using the MCCP stack entity.
  • MCCP multi-connectivity convergence protocol
  • Example 25 may include the method of example 24, or any other example herein, wherein operating above individual radio access network protocol sub-stacks comprises operating above the packet data convergence protocol (PDCP) stack entity of each wireless
  • Example 26 may include the method of any of examples 21 to 25, or any other example herein, further comprising providing an independent user-plane and control-plane stack for each independent wireless communications link(s) provided in the UE.
  • Example 27 may include the method of any of examples 21 to 26, or any other example herein, further comprising providing PDCP bearer splitting by the MCCP stack entity.
  • Example 28 may include the method of any of examples 24 to 27, or any other example herein, wherein the MCCP stack entity comprises a user-plane portion, MCCP-u, and a control-plane portion, MCCP-c.
  • Example 29 may include an apparatus of an Evolved Node-B (eNB) operable to
  • a User Equipment on a wireless network
  • UE User Equipment
  • one or more processors to: selectably operate the eNB in a first operational state that acts as an anchor eNB to at least one UE, wherein operating as the anchor eNB comprises providing communications between the at least one UE and a core network serving the wireless network; and selectably operate the eNB in a second operational state that acts as a booster eNB to the at least one UE, wherein operating as the booster eNB comprises providing communications between the at least one UE and a radio access network of the wireless network; wherein the one or more processors are further to: select between the first and second operational states based upon information from the at least one UE.
  • UE User Equipment
  • Another example may include the eNB of example 29, or any other example herein, wherein to select (or selecting) between the first and second operational states based upon information from the at least one UE may comprise any one or more of: based on a specified data or a specified signal received from the UE (e.g. based on data from the System Information, or the signals sBCH, eRS, PDCCH); based on receiving or otherwise processing a specified data or a specified signal from the UE (e.g. based on receiving or otherwise processing data from the System Information, or the signals sBCH, eRS, PDCCH); based on not receiving or not otherwise processing a specified data or a specified signal from the UE (e.g. based on not receiving or not otherwise processing data from the System Information, or the signals sBCH, eRS, PDCCH).
  • a specified data or a specified signal received from the UE e.g. based on data from the System Information, or the signals sBCH, eRS, P
  • the radio access network of the wireless network may comprise at least one cell, optionally a small cell.
  • Example 30 may include the apparatus of example 29, or any other example herein, wherein the anchor eNB provides both user-plane and control-plane communications between the at least one UE and a core network.
  • Example 31 may include the apparatus of example 29 or 30, or any other example herein, wherein the booster eNB provides both user-plane and control-plane communications between the at least one UE and the anchor eNB.
  • Example 32 may include the apparatus of any of examples 29 to 31, or any other example herein, wherein the booster eNB communicates with the anchor eNB over an eNB to eNB communications link interface, optionally an X2 interface.
  • Example 33 may include the apparatus of any of examples 29 to 32, or any other example herein, wherein the eNB provides at least two primary communications links with the at least one UE, and wherein the one or more processors are further to split traffic to be sent between the at least two primary communications links.
  • Example 34 may include the apparatus of example 33, or any other example herein, wherein to split traffic to be sent between the at least two primary communications links comprises providing at least two bearer links, wherein a bearer link is assigned to each primary communications link.
  • Example 35 may include the apparatus of any of examples 29 to 34, or any other example herein, wherein the one or more processors are further to: provide a multi-connectivity convergence protocol (MCCP) stack entity, wherein the MCCP stack entity operates above individual radio access network protocol sub-stacks, and wherein the MCCP stack entity manages how the at least one UE’s data traffic is routed over the primary and secondary communications links.
  • MCCP multi-connectivity convergence protocol
  • Example 36 may include the apparatus of any of examples 29 to 35, or any other example herein, wherein to operate above individual radio access network protocol sub-stacks comprises operating above the packet data convergence protocol (PDCP) stack entity of each wireless communications link(s) operating in the eNB.
  • PDCP packet data convergence protocol
  • Example 37 may include the apparatus of any of examples 29 to 36, or any other example herein, wherein each wireless communications link(s) operating in the eNB comprises an independent user-plane and control-plane stack to provide operation independent from each other wireless communications link(s) operating in the eNB.
  • Example 38 may include the apparatus of any of examples 29 to 37, or any other example herein, wherein the one or more processors are further to provide PDCP bearer splitting by the MCCP stack entity.
  • Example 39 may include the apparatus of any of examples 29 to 38, or any other example herein, wherein the MCCP stack entity comprises a user-plane portion, MCCP-u, and a control-plane portion, MCCP-c.
  • Example 40 may include an eNB device comprising an application processor, a memory, one or more antenna ports, and an interface for allowing the application processor to
  • the eNB device including the apparatus of any of examples 29 through 39.
  • Example 41 may include machine readable storage media having machine executable instructions that, when executed, cause one or more processors to perform an operation in an Evolved Node-B (eNB) operable to communicate with a User Equipment (UE) on a wireless network, comprising: selectably operating the eNB in a first operational state that acts as an anchor eNB to at least one UE, wherein operating as the anchor eNB comprises providing communications between the at least one UE and a core network serving the wireless network; and selectably operating the eNB in a second operational state that acts as a booster eNB to the at least one UE, wherein operating as the booster eNB comprises providing communications between the at least one UE and a radio access network of the wireless network; select between the first and second operational states based upon information from the at least one UE.
  • eNB Evolved Node-B
  • UE User Equipment
  • Example 42 may include the machine readable storage media of example 41, or any other example herein, further comprising providing both user-plane and control-plane
  • Example 43 may include the machine readable storage media of example 41 or 42, or any other example herein, further comprising providing, by the booster eNB, both user-plane and control-plane communications between the at least one UE and the anchor eNB.
  • Example 44 may include the machine readable storage media of any of examples 41 to 43, or any other example herein, further comprising communicating with the anchor eNB by the booster eNB over an eNB to eNB communications link interface, optionally an X2 interface.
  • Example 45 may include the machine readable storage media of any of examples 41 to 44, or any other example herein, further comprising: providing at least two primary communications links with the at least one UE; and splitting traffic to be sent between the at least two primary communications links.
  • Example 46 may include the machine readable storage media of example 45, or any other example herein, wherein splitting traffic to be sent between the at least two primary communications links comprises providing at least two bearer links, wherein a bearer link is assigned to each primary communications link.
  • Example 47 may include the machine readable storage media of any of examples 41 to 46, or any other example herein, further comprising providing a multi-connectivity convergence protocol (MCCP) stack entity, wherein the MCCP stack entity operates above individual radio access network protocol sub-stacks and wherein the MCCP stack entity manages how the at least one UE’s data traffic is routed over the primary and secondary communications links.
  • MCCP multi-connectivity convergence protocol
  • Example 48 may include the machine readable storage media of any of examples 41 to 47, or any other example herein, wherein operating above individual radio access network protocol sub-stacks comprises operating above the packet data convergence protocol (PDCP) stack entity of each wireless communications link(s) operating in the eNB.
  • PDCP packet data convergence protocol
  • Example 49 may include the machine readable storage media of any of examples 41 to 48, or any other example herein, further comprising providing an independent user-plane and control-plane stack for each other wireless communications link(s) operating in the eNB.
  • Example 50 may include the machine readable storage media of any of examples 41 to 49, or any other example herein, further comprising providing PDCP bearer splitting by the MCCP stack entity.
  • Example 51 may include the machine readable storage media of any of examples 41 to 50, or any other example herein, further comprising providing a user-plane portion, MCCP-u, and a control-plane portion, MCCP-c, of the MCCP stack entity.
  • Example 52 may include a method in an Evolved Node-B (eNB) operable to communicate with a User Equipment (UE) on a wireless network, comprising: selectably operating the eNB in a first operational state that acts as an anchor eNB to at least one UE, wherein operating as the anchor eNB comprises providing communications between the at least one UE and a core network serving the wireless network; and selectably operating the eNB in a second operational state that acts as a booster eNB to the at least one UE, wherein operating as the booster eNB comprises providing communications between the at least one UE and a radio access network of the wireless network; selecting between the first and second operational states based on information from the at least one UE.
  • eNB Evolved Node-B
  • UE User Equipment
  • Example 53 may include the method of example 52, or any other example herein, further comprising providing both user-plane and control-plane communications between the at least one UE and a core network.
  • Example 54 may include the method media of example 52 or 53, or any other example herein, further comprising providing, by the booster eNB, both user-plane and control-plane communications between the at least one UE and the anchor eNB.
  • Example 55 may include the method of any of examples 51 to 54, or any other example herein, further comprising communicating with the anchor eNB by the booster eNB over an eNB to eNB communications link interface, optionally an X2 interface.
  • Example 56 may include the method of any of examples 52 to 55, or any other example herein, further comprising: providing at least two primary communications links with the at least one UE; and splitting traffic to be sent between the at least two primary communications links.
  • Example 57 may include the method of example 56, or any other example herein, wherein splitting traffic to be sent between the at least two primary communications links comprises providing at least two bearer links, wherein a bearer link is assigned to each primary communications link.
  • Example 58 may include the method of any of examples 52 to 57, or any other example herein, further comprising providing a multi-connectivity convergence protocol (MCCP) stack entity, wherein the MCCP stack entity operates above individual radio access network protocol sub-stacks and wherein the MCCP stack entity manages how the at least one UE’s data traffic is routed over the primary and secondary communications links.
  • MCCP multi-connectivity convergence protocol
  • Example 59 may include the method of any of examples 52 to 58, or any other example herein, wherein operating above individual radio access network protocol sub-stacks comprises operating above the packet data convergence protocol (PDCP) stack entity of each wireless communications link(s) operating in the eNB.
  • PDCP packet data convergence protocol
  • Example 60 may include the method of any of examples 52 to 59, or any other example herein, further comprising providing an independent user-plane and control-plane stack for each other wireless communications link(s) operating in the eNB.
  • Example 61 may include the method of any of examples 52 to 60, or any other example herein, further comprising providing PDCP bearer splitting by the MCCP stack entity.
  • Example 62 may include the method of any of examples 52 to 61, or any other example herein, further comprising providing a user-plane portion, MCCP-u, and a control-plane portion, MCCP-c, of the MCCP stack entity.
  • Example 63 may include machine readable storage media having machine executable instructions that, when executed, cause one or more processors to perform an operation to synchronize neighboring cells using directional transmissions comprising: coordinating the neighboring cells to maintain a fixed offset between the transmission of Evolved Node-B (eNB) control signals, wherein the control signals comprises: a Primary Synchronization Signal (PSS) transmission corresponding to one or more first eNB transmit-and-receive sectors; a Secondary Synchronization Signal (SSS) transmission corresponding to one or more second eNB transmit-and-receive sectors, as received through one or more UE transmit- and-receive sectors; and a Sector Level Sweep (SLS) signal; and wherein coordinating the neighboring cells comprises: broadcasting offset information to a UE, wherein the offset information includes a neighboring cell ID, k, a maximum number of neighboring cells, N, involved and a fixed time offset, T offset , for use by a neighboring cell identified by k.
  • Example 64 may include the machine readable storage media of example 63, or any other example herein, wherein the fixed time offset, T offset , is set to zero if the neighboring cells are tightly synchronized, wherein tightly synchronized comprises being synchronized to a symbol or less time period.
  • Example 65 may include the machine readable storage media of example 63 or 64, or any other example herein, wherein, if the neighboring cells are not tightly synchronized, wherein tightly synchronized comprises being synchronized to a symbol or less time period, the method further comprises maintaining a separate timing regime for each neighboring cells that is not tightly synchronized.
  • Example 66 may include the machine readable storage media of example 65, or any other example herein, wherein maintaining a separate timing regime for each neighboring cell comprises maintaining a separate timer clock for each neighboring cell.
  • Example 67 may include the machine readable storage media of any of examples 63 to 66, or any other example herein, further comprising transmitting consecutively the Primary
  • PSS Synchronization Signal
  • SSS Secondary Synchronization Signal
  • N an overall delay of a given cell N is a k multiple of the fixed time offset, T offset ; wherein the first subframe transmission of each neighboring cell containing the Primary Synchronization Signal (PSS) transmission and the Secondary Synchronization Signal (SSS) transmission are sent simultaneously across all neighboring cells.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • Example 68 may include the machine readable storage media of any of examples 63 to 67, or any other example herein, further comprising consecutively transmitting the Primary
  • PSS Synchronization Signal
  • SSS Secondary Synchronization Signal
  • SLS Sector Level Sweep
  • Example 69 may include the machine readable storage media of any of examples 63 to 68, or any other example herein, wherein Sector Level Sweep (SLS) comprises an exhaustive search to select a best transmit sector on an eNB for a UE, wherein SLS is performed by both transmitter and receiver.
  • SLS Sector Level Sweep
  • Example 70 may include a method to synchronize neighboring cells using directional transmissions comprising: coordinating the neighboring cells to maintain a fixed offset between the transmission of Evolved Node-B (eNB) control signals, wherein the control signals comprises: a Primary Synchronization Signal (PSS) transmission corresponding to one or more first eNB transmit-and-receive sectors; a Secondary Synchronization Signal (SSS) transmission corresponding to one or more second eNB transmit-and-receive sectors, as received through one or more UE transmit-and-receive sectors; and a Sector Level Sweep (SLS) signal; and wherein coordinating the neighboring cells comprises: broadcasting offset information to a UE, wherein the offset information includes a neighboring cell ID, k, a maximum number of neighboring cells, N, involved and a fixed time offset, T offset , for use by a neighboring cell identified by k.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • SLS Sector
  • Example 71 may include the method of example 70, or any other example herein, further comprising setting the fixed time offset, T offset , to zero if the neighboring cells are tightly synchronized, wherein tightly synchronized comprises being synchronized to a symbol or less time period.
  • Example 72 may include the method of example 70 or 71, or any other example herein, wherein, if the neighboring cells are not tightly synchronized, wherein tightly synchronized comprises being synchronized to a symbol or less time period, the method further comprises maintaining a separate timing regime for each neighboring cells that is not tightly synchronized.
  • Example 73 may include the method of example 72, or any other example herein, wherein maintaining a separate timing regime for each neighboring cell comprises maintaining a separate timer clock for each neighboring cell.
  • Example 74 may include the method of any of examples 70 to 73, or any other example herein, further comprising: transmitting consecutively the Primary Synchronization Signal (PSS) transmission and the Secondary Synchronization Signal (SSS) transmission in a first subframe transmission of each neighboring cell; using the fixed time offset, T offset , to delay a subsequent transmission of the Sector Level Sweep (SLS) signal for each neighboring cell, wherein an overall delay of a given cell N is a k multiple of the fixed time offset, T offset ; and sending, simultaneously in the first subframe transmission of each neighboring cell, the Primary Synchronization Signal (PSS) transmission and the Secondary Synchronization Signal (SSS) transmission across all neighboring cells.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • Example 75 may include the method of any of examples 70 to 73, or any other example herein, further comprising: consecutively transmitting the Primary Synchronization Signal (PSS) transmission, the Secondary Synchronization Signal (SSS) transmission and the Sector Level Sweep (SLS) signal in a first subframe transmission of each neighboring cell; wherein the fixed time offset, T offset , delays the transmission of the first subframe of each neighboring cell respective to one another, wherein the neighboring cell k delays the transmission of its first subframe by k x the fixed time offset, Toffset.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • SLS Sector Level Sweep
  • Example 76 may include the method of any of examples 70 to 75, or any other example herein, wherein Sector Level Sweep (SLS) comprises an exhaustive search to select a best transmit sector on an eNB for a UE, wherein SLS is performed by both transmitter and receiver.
  • SLS Sector Level Sweep
  • Example 77 may include machine readable storage media having machine executable instructions that, when executed, cause one or more processors to perform an operation in a UE to detect a communications link loss, comprising: receiving communications over a communications link; and determining the communications link is lost (or broken) by determining incorrect receipt of at least one of a plurality of predetermined communications types over the communications link; wherein the plurality of predetermined communications type comprises: a Physical Downlink Control Channel (PDCCH); a dedicated link loss detection broadcast located in a subframe portion to be received after the PDCCH, having a set of link loss detection broadcast parameters; and an enhanced Reference Signal (eRS) persistently allocated for every one or a fixed number of Transmit Time Intervals (TTIs) associated with the communications link; and wherein incorrect receipt of the PDCCH, dedicated link loss detection broadcast or enhanced Reference Signal comprises not receiving the PDCCH, dedicated link loss detection broadcast or enhanced Reference Signal on given sector of an evolved Node-B (eNB) within a predetermined time period.
  • PDCCH Physical Downlink Control
  • Example 78 may include the machine readable storage media of example 77, or any other example herein, wherein the eRS is mapped onto a predetermined sector of an eNB.
  • Example 79 may include the machine readable storage media of example 77 or 78, or any other example herein, wherein the eRS includes cell ID information.
  • Example 80 may include the machine readable storage media of any of examples 77 to 79, or any other example herein, wherein time and frequency allocations of wireless resources of the eRS are mapped to an eNB sector index.
  • Example 81 may include a method in a UE to detect a communications link loss, comprising: receiving communications over a communications link; and determining the communications link is lost (or broken) by determining incorrect receipt of at least one of a plurality of predetermined communications types over the communications link; wherein the plurality of predetermined communications type comprises: a Physical Downlink Control Channel (PDCCH); a dedicated link loss detection broadcast located in a subframe portion to be received after the PDCCH, having a set of link loss detection broadcast parameters; and an enhanced Reference Signal (eRS) persistently allocated for every one or a fixed number of Transmit Time Intervals (TTIs) associated with the communications link; and wherein incorrect receipt of the PDCCH, dedicated link loss detection broadcast or enhanced Reference Signal comprises not receiving the PDCCH, dedicated link loss detection broadcast or enhanced Reference Signal on given sector of an evolved Node-B (eNB) within a predetermined time period.
  • PDCCH Physical Downlink Control Channel
  • eRS enhanced Reference Signal
  • TTIs Transmit Time Intervals
  • Example 82 may include the method of example 81, or any other example herein, wherein the eRS is mapped onto a predetermined sector of an eNB.
  • Example 83 may include the method of example 81 or 82, or any other example herein, wherein the eRS includes cell ID information.
  • Example 84 may include the method of any of examples 82 to 83, or any other example herein, wherein time and frequency allocations of wireless resources of the eRS are mapped to an eNB sector index.
  • Example 85 may include an apparatus of a User Equipment (UE) operable to communicate with an Evolved Node-B (eNB) on a wireless network, comprising: one or more processors to: process communication signals received over a communications link; and determine the communications link is lost (or broken) by determining incorrect receipt of at least one of a plurality of predetermined communications types over the communications link; wherein the plurality of predetermined communications type comprises: a Physical Downlink Control Channel (PDCCH); a dedicated link loss detection broadcast located in a subframe portion to be received after the PDCCH, having a set of link loss detection broadcast parameters; and an enhanced Reference Signal (eRS) persistently allocated for every one for fixed number of Transmit Time Intervals (TTIs) associated with the communications link; and wherein incorrect receipt of the PDCCH, dedicated link loss detection
  • Example 86 may include the apparatus of example 85, or any other example herein, wherein the eRS is mapped onto a predetermined sector of an eNB.
  • Example 87 may include the apparatus of example 85 or 86, or any other example herein, wherein the eRS includes cell ID information.
  • Example 88 The apparatus of any of examples 85 to 87, wherein time and frequency allocations of wireless resources of the eRS are mapped to an eNB sector index.
  • Example 90 may include the machine readable storage media of example 89, or any other example herein, wherein the link loss detection broadcast is allocated to wireless resources after the PDCCH.
  • Example 91 may include the machine readable storage media of example 89 or 90, or any other example herein, wherein the wireless resources allocated to the link loss detection broadcast is configured through system information.
  • Example 92 may include the machine readable storage media of any of examples 89 to 91, or any other example herein, wherein the link loss detection broadcast has variable length, up to a maximum length provided to the UE in advance of receipt.
  • Example 93 may include the machine readable storage media of any of examples 89 to 92, or any other example herein, wherein the link loss detection broadcast comprises a cell identification (cell ID) and sector index.
  • the link loss detection broadcast comprises a cell identification (cell ID) and sector index.
  • UE User Equipment
  • Example 95 may include the method of example 94, or any other example herein, wherein the link loss detection broadcast is allocated to wireless resources after the PDCCH.
  • Example 96 may include the method of example 94 or 95, or any other example herein, wherein the wireless resources allocated to the link loss detection broadcast is configured through system information.
  • Example 97 may include the method of any of examples 94 to 96, or any other example herein, wherein the link loss detection broadcast has variable length, up to a maximum length provided to the UE in advance of receipt.
  • Example 98 may include the method of any of examples 94 to 97, or any other example herein, wherein the link loss detection broadcast comprises a cell identification (cell ID) and sector index.
  • Example 99 may include an apparatus of a User Equipment (UE) operable to communicate with an Evolved Node-B (eNB) on a wireless network, comprising: one or more processors to: receive a set of link loss detection broadcast parameters; and use the set of link loss detection broadcast parameters to detect receipt of the link loss detection broadcast;
  • UE User Equipment
  • eNB Evolved Node-B
  • Example 100 may include the apparatus of example 99, or any other example herein, wherein the link loss detection broadcast is allocated to wireless resources after the PDCCH.
  • wireless resources may comprise a portion of the subframe transmission, i.e. one or more Physical Resource Block(s).
  • Example 101 may include the apparatus of example 99 or 100, or any other example herein, wherein the wireless resources allocated to the link loss detection broadcast is configured through system information.
  • Example 102 may include the apparatus of any of examples 99 to 101, or any other example herein, wherein the link loss detection broadcast has variable length, up to a maximum length provided to the UE in advance of receipt.
  • Example 103 may include the apparatus of any of examples 99 to 102, or any other example herein, wherein the link loss detection broadcast comprises a cell identification (cell ID) and sector index.
  • the link loss detection broadcast comprises a cell identification (cell ID) and sector index.
  • eNB Evolved Node-B
  • Example 105 may include the machine readable storage media of example 104, or any other example herein, wherein the link loss detection broadcast is allocated to wireless resources after or before the PDCCH.
  • Example 106 may include the machine readable storage media of example 104 or 105, or any other example herein, wherein the wireless resources allocated to the link loss detection broadcast is configured through system information.
  • Example 107 may include the machine readable storage media of any of examples 104 to 106, or any other example herein, wherein the link loss detection broadcast has variable length, up to a maximum length provided to a User Equipment (UE) in advance of receipt.
  • Example 108 may include the machine readable storage media of any of examples 104 to 107, or any other example herein, wherein the link loss detection broadcast comprises a cell identification (cell ID) and sector index
  • Example 109 may include the machine readable storage media of any of examples 104 to 108, or any other example herein, wherein directional transmissions comprise millimeter wave transmissions.
  • Example 110 may include the machine readable storage media of any of examples 104 to 109, or any other example herein, wherein link loss detection broadcast parameters are sent via system information.
  • Example 111 may include the machine readable storage media of any of examples 104 to 110, or any other example herein, wherein the link loss detection broadcast comprises a shortened Broadcast CHannel (sBCH) or an enhanced Reference Signal (eRS) persistently allocated for every Transmit Time Interval (TTI) associated with the communications link.
  • Example 112 may include the machine readable storage media of any of examples 104 to 111, or any other example herein, wherein persistently allocated comprises being allocated to persistent time and frequency wireless resources.
  • eNB Evolved Node-B
  • Example 114 may include the method of example 113, or any other example herein, further comprising allocating the link loss detection broadcast to wireless resources after or before the PDCCH.
  • Example 115 may include the method of example 113 or 114, or any other example herein, configuring the wireless resources allocated to the link loss detection broadcast through system information.
  • Example 116 may include the method of any of examples 113 to 115, or any other example herein, wherein the link loss detection broadcast has variable length, up to a maximum length provided to the UE in advance of receipt.
  • Example 117 may include the method of any of examples 113 to 116, or any other example herein, wherein the link loss detection broadcast comprises a cell identification (cell ID) and sector index
  • Example 118 may include the method of any of examples 113 to 117, or any other example herein, wherein directional transmissions comprise millimeter wave transmissions.
  • Example 119 may include the method of any of examples 113 to 118, or any other example herein, further comprising sending the link loss detection broadcast parameters via system information.
  • Example 120 may include the method of any of examples 113 to 119, or any other example herein, wherein the link loss detection broadcast comprises a shortened Broadcast CHannel (sBCH) or an enhanced Reference Signal (eRS) persistently allocated for every Transmit Time Interval (TTI) associated with the communications link.
  • sBCH shortened Broadcast CHannel
  • eRS enhanced Reference Signal
  • Example 121 may include the method of any of examples 113 to 120, or any other example herein, wherein persistently allocated comprises being allocated to persistent time and frequency wireless resources.
  • Example 122 may include an apparatus of an evolved Node-B (eNB) operable to
  • UE User Equipment
  • T sBCH a link loss detection broadcast interval
  • K a number of symbols in the Physical Downlink Control Channel (PDCCH)
  • N a maximum number of symbols of the link loss detection broadcast
  • M a link loss detection threshold.
  • Example 123 may include the apparatus of example 122, or any other example herein, wherein the link loss detection broadcast is allocated to wireless resources after or before the PDCCH.
  • Example 124 may include the apparatus of example 122 or 123, or any other example herein, wherein the wireless resources allocated to the link loss detection broadcast is configured through system information.
  • Example 125 may include the apparatus of any of examples 122 to 124, or any other example herein, wherein the link loss detection broadcast has variable length, up to a maximum length provided to the UE in advance of receipt.
  • Example 126 may include the apparatus of any of examples 122 to 125, or any other example herein, wherein the link loss detection broadcast comprises a cell identification (cell ID) and sector index
  • Example 127 may include the apparatus of any of examples 122 to 126, or any other example herein, wherein directional transmissions comprise millimeter wave transmissions.
  • Example 128 may include the apparatus of any of examples 122 to 127, or any other example herein, wherein link loss detection broadcast parameters are sent via system information.
  • Example 129 may include the apparatus of any of examples 104 to 128, or any other example herein, wherein the link loss detection broadcast comprises a shortened Broadcast CHannel (sBCH) or an enhanced Reference Signal (eRS) persistently allocated for every Transmit Time Interval (TTI) associated with the communications link.
  • sBCH shortened Broadcast CHannel
  • eRS enhanced Reference Signal
  • Example 130 may include the apparatus of any of examples 104 to 111, or any other example herein, wherein persistently allocated comprises being allocated to persistent time and frequency wireless resources.
  • Example 131 may include machine readable storage media having machine executable instructions that, when executed, cause one or more processors to perform an operation between a User Equipment (UE) and at least two wireless network cells comprising:
  • UE User Equipment
  • a persistent UpLink (UL) Scheduling Request message (pSR REQ Message (UL)) for transmission on the secondary communications link; wherein forming a persistent UL Scheduling Request message comprises: receiving a first offset value, d pSR-REQ , the first offset value indicative of an offset of symbols between a first symbol of the persistent UL Scheduling Request message sent on an Uplink and a last symbol that can be used for DownLink (DL)/UpLink (UL) allocation in a respective subframe; receiving a second offset value, d pSR-RSP , the second offset value indicative of an offset of symbols between the first symbol of the persistent UL Scheduling Request message and a first symbol of the persistent UL Scheduling Response message; receiving a cycle time of the persistent UL Scheduling Request message, T pSR , in terms of slots or subframes; and forming the persistent UL Scheduling Request message dependent upon
  • Example 132 may include the machine readable storage media of example 131, or any other example herein, further comprising receiving a persistent UL Scheduling Response message (pSR Resp Message (UL)) on the secondary communications link dependent upon the received first offset value, second offset value and cycle time.
  • pSR Resp Message UL
  • Example 133 may include the machine readable storage media of example 131 or 132, or any other example herein, wherein forming the persistent UL Scheduling Request message dependent upon the received first offset value, second offset value and cycle time comprises using the first offset to determine a position in a subframe to transmit the persistent UL Scheduling Request message, the position being relative to the end of the subframe in which the persistent UL Scheduling Request message is to be sent.
  • Example 134 may include the machine readable storage media of any of examples 131 to 133, or any other example herein, wherein forming the persistent UL Scheduling Response message dependent upon the received first offset value, second offset value and cycle time comprises using the first offset to determine a position in a subframe to transmit the persistent UL Scheduling Request message, the position being relative to the end of the subframe in which the persistent UL Scheduling Request message is to be sent, and using the second offset value to determine a second position in a subframe to transmit the persistent UL Scheduling Response message, the second position being relative to the first position.
  • Example 135 may include the machine readable storage media of any of examples 131 to 134, or any other example herein, wherein the position in a subframe to transmit the persistent UL Scheduling Request message is located a symbol distance d pSR-REQ away from the end of the subframe, or the first symbol of the common control and reference signals (Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS)/Broadcast Channel (BCH)/Sector Level Sweep (SLS)).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • BCH Broadcast Channel
  • SLS Supplemental Level Sweep
  • Example 136 may include the machine readable storage media of any of examples 131 to 135, or any other example herein, wherein the second position in a subframe to transmit the persistent UL Scheduling Response message is located a symbol distance d pSR-RSP away from the start of the UL Scheduling Request message.
  • Example 137 may include the machine readable storage media of any of examples 131 to 136, or any other example herein, further comprising transmitting the persistent UL
  • Example 138 may include the machine readable storage media of any of examples 131 to 137, or any other example herein, further comprising transmitting the persistent UL
  • Example 139 may include a method in a UE comprising: maintaining a primary
  • a persistent UpLink (UL) Scheduling Request message (pSR REQ Message (UL)) for transmission on the secondary communications link; wherein forming a persistent UL Scheduling Request message comprises: receiving a first offset value, d pSR-REQ , the first offset value indicative of an offset of symbols between a first symbol of the persistent UL Scheduling Request message sent on an Uplink and a last symbol that can be used for DownLink (DL)/UpLink (UL) allocation in a respective subframe;
  • Example 140 may include the method of example 139, or any other example herein, further comprising receiving a persistent UL Scheduling Response message (pSR Resp Message (UL)) on the secondary communications link dependent upon the received first offset value, second offset value and cycle time.
  • pSR Resp Message UL
  • Example 141 may include the method of example 139 or 140, or any other example herein, wherein forming the persistent UL Scheduling Request message dependent upon the received first offset value, second offset value and cycle time comprises using the first offset to determine a position in a subframe to transmit the persistent UL Scheduling Request message, the position being relative to the end of the subframe in which the persistent UL Scheduling Request message is to be sent.
  • Example 142 may include the method of any of examples 139 to 141, or any other example herein, wherein forming the persistent UL Scheduling Response message dependent upon the received first offset value, second offset value and cycle time comprises using the first offset to determine a position in a subframe to transmit the persistent UL Scheduling Request message, the position being relative to the end of the subframe in which the persistent UL Scheduling Request message is to be sent, and using the second offset value to determine a second position in a subframe to transmit the persistent UL Scheduling Response message, the second position being relative to the first position.
  • Example 143 may include the method of any of examples 139 to 142, or any other example herein, wherein the position in a subframe to transmit the persistent UL Scheduling Request message is located a symbol distance d pSR-REQ away from the end of the subframe, or the first symbol of the common control and reference signals (Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS)/Broadcast Channel (BCH)/Sector Level Sweep (SLS)).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • BCH Broadcast Channel
  • SLS Supplemental Level Sweep
  • Example 144 may include the method of any of examples 139 to 144, or any other example herein, wherein the second position in a subframe to transmit the persistent UL Scheduling Response message is located a symbol distance d pSR-RSP away from the start of the UL Scheduling Request message.
  • Example 145 may include the method of any of examples 139 to 145, or any other example herein, further comprising transmitting the persistent UL Scheduling Request (pSR) message on the secondary communications link.
  • pSR persistent UL Scheduling Request
  • Example 146 may include the method of any of examples 139 to 146, or any other example herein, further comprising transmitting the persistent UL Scheduling Response message on the secondary communications link.
  • Example 147 may include an apparatus of a User Equipment (UE) operable to communicate with an evolved Node-B (eNB) in a wireless network, comprising: one or more processors to: maintain a primary communications link with a first network cell; maintain a secondary communications link with a second network cell; and form a persistent UpLink (UL) Scheduling Request message (pSR REQ Message (UL)) for transmission on the secondary communications link; wherein, to form a persistent UL Scheduling Request message, the one or more processors are to: receive a first offset value, d pSR-REQ , the first offset value indicative of an offset of symbols between a first symbol of the persistent UL Scheduling Request message sent on an Uplink and a last symbol that can be used for DownLink (DL)/UpLink (UL) allocation in a respective subframe; receive a second offset value, dpSR-RSP, the second offset value indicative of an offset of symbols between the first symbol of the persistent UL Scheduling Request message and a first symbol of the persistent
  • Example 148 may include the apparatus of example 147, or any other example herein, wherein the one or more processors are further to receive a persistent UL Scheduling
  • pSR Resp Message (UL) on the secondary communications link dependent upon the received first offset value, second offset value and cycle time.
  • Example 149 may include the apparatus of example 147 or 148, or any other example herein, wherein the one or more processors are further to form the persistent UL Scheduling Request message dependent upon the received first offset value, second offset value and cycle time comprises using the first offset to determine a position in a subframe to transmit the persistent UL Scheduling Request message, the position being relative to the end of the subframe in which the persistent UL Scheduling Request message is to be sent.
  • Example 150 may include the apparatus of any of examples 147 to 149, or any other example herein, wherein the one or more processors are further to form the persistent UL Scheduling Response message dependent upon the received first offset value, second offset value and cycle time comprises using the first offset to determine a position in a subframe to transmit the persistent UL Scheduling Request message, the position being relative to the end of the subframe in which the persistent UL Scheduling Request message is to be sent, and using the second offset value to determine a second position in a subframe to transmit the persistent UL Scheduling Response message, the second position being relative to the first position.
  • Example 151 may include the apparatus of any of examples 147 to 150, or any other example herein, wherein the position in a subframe to transmit the persistent UL Scheduling Request message is located a symbol distance d pSR-REQ away from the end of the subframe, or the first symbol of the common control and reference signals (Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS)/Broadcast Channel (BCH)/Sector Level Sweep (SLS)).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • BCH Broadcast Channel
  • SLS Supplemental Level Sweep
  • Example 152 may include the apparatus of any of examples 147 to 151, or any other example herein, wherein the second position in a subframe to transmit the persistent UL Scheduling Response message is located a symbol distance d pSR-RSP away from the start of the UL Scheduling Request message.
  • Example 153 may include the apparatus of any of examples 147 to 152, or any other example herein, wherein the one or more processors are further to transmit the persistent UL
  • Example 154 may include the apparatus of any of examples 147 to 153, or any other example herein, wherein the one or more processors are further to transmit the persistent UL
  • Example 155 may include machine readable storage media having machine executable instructions that, when executed, cause one or more processors to perform an operation between a User Equipment (UE) and at least two wireless network cells comprising:
  • UE User Equipment
  • communications link to send and receive control messages (e.g. scheduling request) between the UE and the wireless network; detecting a loss of a primary communications link; and carrying out a fast cell switching (FCS) procedure at the UE to switch communications from the lost at least one primary communications link to use a one of the at least one secondary communications link.
  • control messages e.g. scheduling request
  • FCS fast cell switching
  • Example 156 may include the machine readable storage media of example 155, or any other example herein, wherein the FCS procedure comprises: selecting an appropriate one of the at least one secondary communications link transmitting a FCS switch request control message over the selected secondary communications link to an Evolved Node-B (eNB) providing the secondary communications link; receiving an FCS switch response control message from the eNB providing the secondary communications link.
  • the FCS procedure comprises: selecting an appropriate one of the at least one secondary communications link transmitting a FCS switch request control message over the selected secondary communications link to an Evolved Node-B (eNB) providing the secondary communications link; receiving an FCS switch response control message from the eNB providing the secondary communications link.
  • eNB Evolved Node-B
  • Example 157 may include the machine readable storage media of example 155 or 156, or any other example herein, wherein the FCS procedure further comprises: setting the eNB providing the secondary communications link as a new primary eNB providing a new primary communications link; and sending and receiving all data between the UE and the wireless network over the new primary communications link.
  • Example 158 may include the machine readable storage media of any of examples 155 to 157, or any other example herein, wherein transmitting a FCS switch request message over the selected secondary communications link to an eNB providing the secondary
  • communications link comprises transmitting the FCS switch request in a persistent
  • Example 159 may include the machine readable storage media of any of examples 155 to 158, or any other example herein, wherein receiving an FCS switch response message from the eNB providing the secondary communications link comprises receiving the FCS switch response in a persistent Scheduling Response message (pSR-RSP).
  • pSR-RSP persistent Scheduling Response message
  • Example 160 may include the machine readable storage media of any of examples 155 to 159, or any other example herein, wherein the operation of examples 155 to 159 occurs in a UE.
  • Example 161 may include a method in a User Equipment (UE) comprising: maintaining at least one primary communications link between the UE and a first network cell and using the at least one primary communications link to send and receive data between the UE and the wireless network; maintaining at least one secondary communications link between the UE and a second network cell and using the at least one secondary communications link to send and receive control messages (e.g. scheduling request) between the UE and the wireless network; detecting a loss of a primary communications link; and carrying out a fast cell switching (FCS) procedure at the UE to switch communications from the lost at least one primary communications link to use a one of the at least one secondary communications link.
  • UE User Equipment
  • Example 162 may include the method of example 161, or any other example herein, wherein the FCS procedure comprises: selecting an appropriate one of the at least one secondary communications link transmitting a FCS switch request control message over the selected secondary communications link to an evolved Nobe-B (eNB) providing the secondary communications link; receiving an FCS switch response control message from the eNB providing the secondary communications link.
  • the FCS procedure comprises: selecting an appropriate one of the at least one secondary communications link transmitting a FCS switch request control message over the selected secondary communications link to an evolved Nobe-B (eNB) providing the secondary communications link; receiving an FCS switch response control message from the eNB providing the secondary communications link.
  • eNB evolved Nobe-B
  • Example 163 may include the method of example 161 or 162, or any other example herein, wherein the FCS procedure further comprises: setting the eNB providing the secondary communications link as a new primary eNB providing a new primary communications link; and sending and receiving all data between the UE and the wireless network over the new primary communications link.
  • Example 164 may include the method of any of examples 161 to 163, or any other example herein, wherein transmitting a FCS switch request message over the selected secondary communications link to an eNB providing the secondary communications link comprises transmitting the FCS switch request in a persistent Scheduling Request message (pSR-REQ).
  • pSR-REQ persistent Scheduling Request message
  • Example 165 may include the method of any of examples 161 to 164, or any other example herein, wherein receiving an FCS switch response message from the eNB providing the secondary communications link comprises receiving the FCS switch response in a persistent Scheduling Response message (pSR-RSP).
  • pSR-RSP persistent Scheduling Response message
  • Example 166 may include an apparatus for a User Equipment (UE) comprising: one or more processors to: maintain at least one primary communications link between the UE and a first network cell and using the at least one primary communications link to send and receive data between the UE and the wireless network; maintain at least one secondary communications link between the UE and a second network cell and using the at least one secondary communications link to send and receive control messages (e.g. scheduling request) between the UE and the wireless network; detect a loss of a primary communications link; and carry out a fast cell switching (FCS) procedure at the UE to switch communications from the lost at least one primary communications link to use a one of the at least one secondary
  • FCS fast cell switching
  • Example 167 may include the apparatus of example 166, wherein the one or more processors are further to: select an appropriate one of the at least one secondary communications link transmit a FCS switch request control message over the selected secondary communications link to an evolved Nobe-B (eNB) providing the secondary communications link; receive an FCS switch response control message from the eNB providing the secondary
  • eNB evolved Nobe-B
  • Example 168 may include the apparatus of example 166 or 167, or any other example herein, wherein the one or more processors are further to: set the eNB providing the secondary communications link as a new primary eNB providing a new primary communications link; and send and receiving all data between the UE and the wireless network over the new primary communications link.
  • Example 169 may include the apparatus of any of examples 166 to 168, or any other example herein, wherein the one or more processors are further to transmit a FCS switch request to the eNB in a persistent Scheduling Request message (pSR-REQ).
  • Example 170 may include the apparatus of any of examples 166 to 169, or any other example herein, wherein the one or more processors are further to receive an FCS switch response message from the eNB in a persistent Scheduling Response message (pSR-RSP).
  • pSR-RSP persistent Scheduling Response message
  • Example 171 may include machine readable storage media having machine executable instructions that, when executed, cause one or more processors to perform an operation between a User Equipment (UE) and at least two wireless network cells comprising:
  • UE User Equipment
  • eNB Evolved Node-B
  • maintaining at least one primary communications link between the UE and a first Evolved Node-B (eNB) of a first network cell and using the at least one primary communications link to send and receive data between the UE and the wireless network maintaining at least one secondary communications link between the UE and a second eNB of a second network cell and using the at least one secondary communications link to send and receive persistent scheduling messages between the UE and the wireless network; receiving a fast cell switching request message from the UE at the second eNB providing the secondary network cell when a one of the at least one primary communications link to the UE is lost;
  • Example 172 may include the machine readable storage media of example 171, or any other example herein, further comprising initiating a sector scanning procedure at the second eNB to select a most appropriate sector of the second eNB for use to communicate with the UE.
  • Example 173 may include the machine readable storage media of any of examples 171 or 172, or any other example herein, wherein selecting most appropriate sector of the second eNB for use to communicate with the UE comprising selecting a sector having a selection parameter exceeding a predetermined threshold.
  • Example 174 may include the machine readable storage media of any of examples 171 to 173, or any other example herein, wherein receiving a fast cell switching request message from the UE at the second eNB comprises receiving the FCS switch request in a persistent Scheduling Request message (pSR-REQ).
  • pSR-REQ persistent Scheduling Request message
  • Example 175 may include the machine readable storage media of any of examples 171 to 174, or any other example herein, wherein transmitting FCS switch response message from the second eNB comprises transmitting the FCS switch response in a persistent Scheduling Response message (pSR-RSP).
  • pSR-RSP persistent Scheduling Response message
  • Example 176 may include the machine readable storage media of any of examples 171 to 175, or any other example herein, further comprising detecting a loss of a primary communications link according to any of examples 81 to 84 or 94 to 98.
  • Example 177 may include the machine readable storage media of any of examples 171 to 176, or any other example herein, wherein the operation occurs in an eNB.
  • Example 178 may include a method in an Evolved Node-B (eNB) comprising: maintaining at least one primary communications link between a User Equipment (UE) and a first eNB of a first network cell and using the at least one primary communications link to send and receive data between the UE and the wireless network; maintaining at least one secondary communications link between the UE and a second eNB of a second network cell and using the at least one secondary communications link to send and receive persistent scheduling messages between the UE and the wireless network; receiving a fast cell switching request message from the UE at the second eNB providing the secondary network cell when a one of the at least one primary communications link to the UE is lost; transmitting, from the second eNB providing the secondary network cell, a fast cell switching response message to the UE over the secondary communications link; transmitting, from the second eNB to the anchor eNB providing communications between the UE and a core network serving the wireless network, a fast cell switching notification message to control the first eNB to forward all communications for the UE to the
  • Example 179 may include the method of example 178, or any other example herein, further comprising initiating a sector scanning procedure at the second eNB to select a most appropriate sector of the second eNB for use to communicate with the UE.
  • Example 180 may include the method of any of examples 178 or 179, or any other example herein, wherein selecting most appropriate sector of the second eNB for use to communicate with the UE comprising selecting a sector having a selection parameter exceeding a predetermined threshold.
  • Example 181 may include the method of any of examples 178 to 180, or any other example herein, wherein receiving a fast cell switching request message from the UE at the second eNB comprises receiving the FCS switch request in a persistent Scheduling Request message (pSR-REQ).
  • Example 182 may include the method of any of examples 178 to 181, or any other example herein, wherein transmitting FCS switch response message from the second eNB comprises transmitting the FCS switch response in a persistent Scheduling Response message (pSR- RSP).
  • pSR- RSP persistent Scheduling Response message
  • Example 183 may include the method of any of examples 178 to 182, or any other example herein, further comprising detecting a loss of a primary communications link according to any of examples 81 to 84 or 94 to 98.
  • Example 184 may include an apparatus for an Evolved Node-B (eNB) comprising: one or more processors to: maintain at least one primary communications link between a User Equipment (UE) and a first eNB of a first network cell and using the at least one primary communications link to send and receive data between the UE and the wireless network; maintain at least one secondary communications link between the UE and a second eNB of a second network cell and using the at least one secondary communications link to send and receive persistent scheduling messages between the UE and the wireless network; receive a fast cell switching request message from the UE at the second eNB providing the secondary network cell when a one of the at least one primary communications link to the UE is lost; transmit, from the second eNB providing the secondary network cell, a fast cell switching response message to the UE over the secondary communications link; transmit, from the second eNB to the anchor eNB providing communications between the UE and a core network serving the wireless network, a fast cell switching notification message to control the first eNB to forward all communications for the
  • Example 185 may include the apparatus of example 184, or any other example herein, wherein the one or more processors are further to initiate a sector scanning procedure at the second eNB to select a most appropriate sector of the second eNB for use to communicate with the UE.
  • Example 186 may include the apparatus of any of examples 184 or 185, or any other example herein, wherein the one or more processors are further to select a most appropriate sector of the second eNB for use to communicate with the UE dependent upon a selection parameter exceeding a predetermined threshold.
  • Example 187 may include the apparatus of any of examples 184 to 186, or any other example herein, wherein the one or more processors are further to receive a fast cell switching request message from the UE at the second eNB comprises in a persistent Scheduling Request message (pSR-REQ).
  • pSR-REQ persistent Scheduling Request message
  • Example 188 may include the apparatus of any of examples 184 to 187, or any other example herein, wherein the one or more processors are further to transmit the FCS switch response in a persistent Scheduling Response message (pSR-RSP).
  • pSR-RSP persistent Scheduling Response message
  • Example 189 may include the apparatus of any of examples 184 to 188, or any other example herein, wherein the one or more processors are further to detect a loss of a primary communications link according to any of examples 81 to 84 or 94 to 98.
  • Example 190 may include an apparatus comprising means for carrying any of method examples 21 to 28, 52 to 62, 70 to 76, 81 to 84, 94 to 98, 113 to 121, 139 to 146, 161 to 165, and 178 to 183.
  • the features of the foregoing embodiments and examples, and of the following claims may be integrated together in any suitable arrangement, especially ones where there is a beneficial effect in doing so. This is not limited to only any specified benefit, and instead may arise from an“ex post facto” benefit. This is to say that the combination of features is not limited by the described forms, particularly the form (e.g.

Landscapes

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

Abstract

Des modes de réalisation concernent un équipement d'utilisateur (UE) qui communique avec un nœud B évolué (eNB) sur un réseau sans fil. L'UE comprend un ou plusieurs processeurs pour : établir une connexion/communication avec au moins un premier eNB d'ancrage et un second eNB d'appoint ; maintenir une pluralité de liaisons de communication de réseau d'accès radio entre l'UE et un réseau d'accès radio du réseau sans fil, ladite pluralité de liaisons de communication de réseau d'accès radio entre l'UE et un réseau d'accès radio du réseau sans fil comprenant au moins une liaison de communication primaire et au moins une liaison de communication secondaire ; passer de l'utilisation active de la ou des liaisons de communication primaires pour envoyer et recevoir des données de l'UE à l'utilisation active de la ou des liaisons de communication secondaires pour envoyer et recevoir des données de l'UE lorsque la ou les liaisons de communication primaires sont déterminées comme étant perdues. L'invention concerne également d'autres modes de réalisation.
PCT/US2016/042134 2016-07-13 2016-07-13 Support multiconnectivité et commutation rapide de cellules pour technologies d'accès radio cellulaire à ondes millimétriques Ceased WO2018013110A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201680086744.7A CN109314901B (zh) 2016-07-13 2016-07-13 用于多连通性支持和快速小区切换的装置
PCT/US2016/042134 WO2018013110A1 (fr) 2016-07-13 2016-07-13 Support multiconnectivité et commutation rapide de cellules pour technologies d'accès radio cellulaire à ondes millimétriques

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2016/042134 WO2018013110A1 (fr) 2016-07-13 2016-07-13 Support multiconnectivité et commutation rapide de cellules pour technologies d'accès radio cellulaire à ondes millimétriques

Publications (1)

Publication Number Publication Date
WO2018013110A1 true WO2018013110A1 (fr) 2018-01-18

Family

ID=56497928

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/042134 Ceased WO2018013110A1 (fr) 2016-07-13 2016-07-13 Support multiconnectivité et commutation rapide de cellules pour technologies d'accès radio cellulaire à ondes millimétriques

Country Status (2)

Country Link
CN (1) CN109314901B (fr)
WO (1) WO2018013110A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110972177A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 一种链路检测方法及装置
CN113784377A (zh) * 2021-09-10 2021-12-10 深圳艾灵网络有限公司 数据通信方法、装置、电子设备及存储介质
US11902948B1 (en) * 2018-11-30 2024-02-13 T-Mobile Innovations Llc Adaptive primary component carrier switching in massive MIMO based on beamforming calibration status

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023108534A1 (fr) * 2021-12-16 2023-06-22 Mediatek Singapore Pte. Ltd. Procédés et appareil de transmission de données basée sur un relais de liaison latérale avec de multiples trajets

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130310037A1 (en) * 2012-05-11 2013-11-21 Qualcomm Incorporated Carrier aggregation capable mobile operation over single frequency
US20140321282A1 (en) * 2011-12-08 2014-10-30 Interdigital Patent Holdings, Inc. High-rate dual-band cellular communications
US20150045035A1 (en) * 2013-08-12 2015-02-12 Samsung Electronics Co., Ltd. Method of handling radio link failure in wireless communication system based on multi-enb connectivity and apparatus thereof
US20150230134A1 (en) * 2014-02-07 2015-08-13 Nokia Solutions And Networks Oy Method and apparatus for performing handover and re-establishment of connections
US20150358838A1 (en) * 2013-01-10 2015-12-10 Na Wei Buffer status reporting for dual connection
US20160037406A1 (en) * 2013-04-05 2016-02-04 Telefonaktiebolaget L M Ericsson (Publ) Handover Request Indicating Split of a Radio Bearer between Cells

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013155709A1 (fr) * 2012-04-20 2013-10-24 华为技术有限公司 Procédé de configuration pour diffusion de données en flux, système de station de base et équipement d'utilisateur
US10075881B2 (en) * 2013-04-02 2018-09-11 Lg Electronics Inc. Method for performing a cell change procedure in a wireless communication system and a device therefor
CN104301955A (zh) * 2014-09-02 2015-01-21 中兴通讯股份有限公司 一种用户设备切换基站的方法及基站、用户设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140321282A1 (en) * 2011-12-08 2014-10-30 Interdigital Patent Holdings, Inc. High-rate dual-band cellular communications
US20130310037A1 (en) * 2012-05-11 2013-11-21 Qualcomm Incorporated Carrier aggregation capable mobile operation over single frequency
US20150358838A1 (en) * 2013-01-10 2015-12-10 Na Wei Buffer status reporting for dual connection
US20160037406A1 (en) * 2013-04-05 2016-02-04 Telefonaktiebolaget L M Ericsson (Publ) Handover Request Indicating Split of a Radio Bearer between Cells
US20150045035A1 (en) * 2013-08-12 2015-02-12 Samsung Electronics Co., Ltd. Method of handling radio link failure in wireless communication system based on multi-enb connectivity and apparatus thereof
US20150230134A1 (en) * 2014-02-07 2015-08-13 Nokia Solutions And Networks Oy Method and apparatus for performing handover and re-establishment of connections

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110972177A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 一种链路检测方法及装置
CN110972177B (zh) * 2018-09-28 2022-10-11 华为技术有限公司 一种链路检测方法及装置
US12022548B2 (en) 2018-09-28 2024-06-25 Huawei Technologies Co., Ltd. Link detection method and apparatus
US11902948B1 (en) * 2018-11-30 2024-02-13 T-Mobile Innovations Llc Adaptive primary component carrier switching in massive MIMO based on beamforming calibration status
CN113784377A (zh) * 2021-09-10 2021-12-10 深圳艾灵网络有限公司 数据通信方法、装置、电子设备及存储介质
CN113784377B (zh) * 2021-09-10 2024-03-22 深圳艾灵网络有限公司 数据通信方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN109314901A (zh) 2019-02-05
CN109314901B (zh) 2022-02-01

Similar Documents

Publication Publication Date Title
US11201657B2 (en) Reference signals for initial acquisition in 5G systems
US11063646B2 (en) Device and method for synchronous beam switching
US11245480B2 (en) Devices and methods for robust measurement and data receiving
US11576029B2 (en) Inter-frequency inter-public land mobile network (PLMN) discovery
US11088749B2 (en) Device and method of using BRRS configuration
US20230036278A1 (en) Beamed reference signal with hybrid beam
US20200205116A1 (en) System and method for multiplexing of tracking reference signal and synchronization signal block
US10778486B2 (en) Discovery reference signal design for LTE in unlicensed bands
US11122643B2 (en) LWIP enhancements for reliable DRB switching
WO2017086922A1 (fr) Dispositifs et procédés de suivi de faisceau pour bandes de hautes fréquences 5g
US11166282B2 (en) Evolved Node-B (eNB), radio access network (RAN) central unit (RCU) and methods for radio resource control (RRC)
US20190074918A1 (en) Intra-frequency and inter-frequency measurement for narrow band machine-type communication
CN109314901B (zh) 用于多连通性支持和快速小区切换的装置
US10499444B2 (en) Radio network access of wearable devices
WO2017180173A1 (fr) Procédures d'acquisition initiale basées sur le balayage de secteur hybride destinées à des réseaux d'accès cellulaires à ondes millimétriques
WO2018053364A1 (fr) Conception de canal de diffusion physique de liaison descendante pour systèmes de formation de faisceau

Legal Events

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

Ref document number: 16741516

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16741516

Country of ref document: EP

Kind code of ref document: A1