On-Demand Reconfigurable Control Plane Architecture (ORCA) Integrating Millimeter-Wave Small Cell and Microwave Macro Cell
20170374703 · 2017-12-28
Inventors
Cpc classification
H04W8/22
ELECTRICITY
H04W48/08
ELECTRICITY
H04W8/18
ELECTRICITY
International classification
Abstract
Millimeter-wave (mmWave) band communication is a very promising technology for 5G small cells. In practice, such a new system will coexist with legacy or evolved microwave band systems, such as E-UTRAN LTE macro-cell cellular systems, for a long time to come. Considering the typical scenarios where a macro cell offers umbrella coverage for clusters of small cells, several control plane (C-plane) architectural choices of macro-assisted 5G mmWave systems from both UE and network's perspectives are evaluated. Termed macro-assisted mmWave, an effective end-to-end integration of the futuristic mmWave small cells and microwave macro cells shall promise the benefits of both yet avoid individual limitations. The proposed On-demand Reconfiguration C-Place Architecture (ORCA) for Macro-assisted Millimeter Wave (mmWave) small cells is designed to meet 5G expectations of dense deployment of small cells and UEs and beamformed intermittent Gbps links.
Claims
1. A method comprising: obtaining control-plane (C-plane) setup preference information by a base station in a heterogeneous network (HetNet) having a microwave macrocell and overlaying Millimeter Wave (mmWave) small cells; determining an updated C-plane setup based on the obtained C-plane setup preference information for a user equipment (UE) having dual connectivity with a macro base station (MBS) and a smallcell base station (SBS); and performing C-plane setup update according to the updated C-plane setup of the UE.
2. The method of claim 1, wherein the C-plane setup preference information comprises at least one of a smallcell addition and removal and modification, a signaling load, a network density, available radio access resources, link quality of the macrocell and small cells, a UE mobility, and a C-plane setup transition request from the UE.
3. The method of claim 1, wherein a C-plane setup comprises one or more base stations that perform radio resource control (RRC) and radio resource management (RRM) functionalities for the UE.
4. The method of claim 1, wherein a first C-plane setup is applied for the stationary UE, and wherein anchor control signaling is provided by the SBS.
5. The method of claim 1, wherein a second C-plane setup is applied for the high-mobility UE, and wherein anchor control signaling is provided by the MBS.
6. The method of claim 1, wherein a third C-plane setup is applied for the low-mobility UE, and wherein control signaling is provided by both the MBS and the SBS.
7. The method of claim 1, wherein the C-plane setup update involves performing X2 sync and radio resource control (RRC) connection update between the MBS and the SBS.
8. The method of claim 1, wherein the updated C-plane setup is dynamically applied via software configuration based on the same set of hardware in the network.
9. A method, comprising: obtaining control-plane (C-plane) setup preference information by a user equipment (UE) in a heterogeneous network (HetNet) having a microwave macrocell and overlaying Millimeter Wave (mmWave) small cells; determining an updated C-plane setup for the UE based on the obtained C-plane setup preference information, wherein the UE maintains dual connectivity with a macro base station (MBS) and a smallcell base station (SBS); and performing C-plane setup update according to the updated C-plane setup of the UE.
10. The method of claim 9, wherein the C-plane setup preference information comprises a UE mobility and assistance information from the network.
11. The method of claim 9, wherein a C-plane setup comprises one or more base stations that perform radio resource control (RRC) and radio resource management (RRM) functionalities for the UE.
12. The method of claim 9, wherein the updated C-plane setup is different from a previously applied C-plane setup for the same UE.
13. The method of claim 9, wherein the updated C-plane setup associated with the SBS is different from a second C-plane setup associated with a second SBS for the same UE at the same time.
14. The method of claim 9, wherein the UE is stationary and applies a first C-plane setup, and wherein the UE receives control signaling from the SBS.
15. The method of claim 9, wherein the UE has high mobility and applies a second C-plane setup, and wherein the UE receives control signaling from the MBS.
16. The method of claim 9, wherein the UE has low mobility and applies a third C-plane setup, and wherein the UE receives control signaling from both the MBS and the SBS.
17. A user equipment (UE), comprising: a configuration circuit that obtains control-plane (C-plane) setup preference information in a heterogeneous network (HetNet) having a microwave macrocell and overlaying Millimeter Wave (mmWave) small cells; a first radio frequency (RF) transceiver that communicates with a macro base station (MBS); a second radio frequency (RF) transceiver that communicates with a smallcell base station (SBS); and a control circuit that determines an updated C-plane setup for the UE based on the obtained C-plane setup preference information and performs C-plane setup update according to the updated C-plane setup of the UE.
18. The UE of claim 17, wherein the C-plane setup preference information comprises a UE mobility and assistance information from the network.
19. The UE of claim 17, wherein a C-plane setup comprises one or more base stations that perform radio resource control (RRC) and radio resource management (RRM) functionalities for the UE.
20. The UE of claim 17, wherein the updated C-plane setup is different from a previously applied C-plane setup for the same UE.
21. The UE of claim 17, wherein the updated C-plane setup associated with the SBS is different from a second C-plane setup associated with a second SBS for the same UE at the same time.
22. The UE of claim 17, wherein the UE is stationary and applies a first C-plane setup, and wherein the UE receives control signaling from the SBS.
23. The UE of claim 17, wherein the UE has high mobility and applies a second C-plane setup, and wherein the UE receives control signaling from the MBS.
24. The UE of claim 17, wherein the UE has low mobility and applies a third C-plane setup, and wherein the UE receives control signaling from both the MBS and the SBS.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The accompanying drawings, where like numerals indicate like components, illustrate embodiments of the invention.
[0015]
[0016]
[0017]
[0018]
[0019]
[0020]
[0021]
[0022]
[0023]
[0024]
[0025]
[0026]
[0027]
DETAILED DESCRIPTION
[0028] Reference will now be made in detail to some embodiments of the invention, examples of which are illustrated in the accompanying drawings.
[0029]
[0030] The existing LTE 3GPP HetNet dual connectivity (DuCo) architecture is designed only for less dense deployed, relatively low-rate microwave smallcell scenarios that is not fine-tuned for stationary or dense scenarios with Gbps mmWave small cells. The 3GPP HetNet DuCo defines control-plane and user-plane split with single radio resource control (RRC) for HetNet mobility, and flow/bearer data split. In control plane, control signaling with RRC/S1-MME anchor is at the macrocell only. The single RRC anchor provides simple and robust handover (HO) but no diversity, single failure point at the macro base station with X2 latency. The control plane is not designed to handle very dense deployment of small cells, UEs, and many intermittent links with signaling errors. In the example of
[0031] In accordance with one novel aspect, a control plane architecture to integrate mmWave small cells and microwave macro cells effectively is proposed. The On-demand Reconfiguration C-Place Architecture (ORCA) for Macro-assisted Millimeter Wave (mmWave) small cells is designed to meet 5G expectations of dense deployment of small cells and UEs and beamformed intermittent Gbps links. ORCA is also designed to meet the E-UTRAN constraints of limited and costly microwave spectrum, limited macrocell processing power, backhaul link and CN capacity. Further, ORCA is designed to consider the deployment scenarios following classification criteria of connection/UE/cell density, UE mobility level, backhaul quality, and integration with macrocell-macro-assisted mmWave small cells. For example, given the limited processing resources and link capacity with existing E-UTRAN MeNB/MBS, anchoring data path and control functionalities at the MBS, as in existing HetNet DuCo or PDCP-level LTE-WiFi Aggregation, may not scale up gracefully with the 5G expectation of dense connections and small RAN latency, e.g., up to 100 connections/km.sup.2 and end-to-end RAN latency as small as 1-5 ms, respectively.
[0032] The proposed ORCA revises the LTE DuCo C-plane architecture with scenario-specific and on-demand configurability. ORCA utilizes the X2-C interference but reduces inter-BS sync-up. The master BS overwrites slave or secondary BSs on configuration and UE capability negotiation, and peer-to-peer BSs have detailed functional split. ORCA redefines C-plane and RRM functional split between macrocell and smallcell for localized and fast radio control. ORCA also provides flexible (context/load) scenario based end-to-end configuration. ORCA provides UE on-demand C-plane diversity for robustness, saves the (RACH, signaling) resources at MBS, and reduces the latency between UE and SBSs.
[0033]
[0034] UE 201 also includes a 3GPP protocol stack module 226 supporting various protocol layers including NAS 225, AS/RRC 224, PDCP/RLC 223, MAC 222 and PHY 221, a TCP/IP protocol stack module 227, an application module APP 228, and a management module 230 including a configuration module 231, a mobility module 232, and a control module 233. The different circuits and modules are function circuits and modules that can be configured and implemented by software, firmware, hardware, or any combination thereof. For example, each circuit or module may comprise processor 212 plus corresponding software codes. The function circuits and modules, when executed by processor 212 (via program instructions and data contained in memory 211), interwork with each other to allow UE 201 to perform certain embodiments of the present invention accordingly. Configuration module 231 obtains C-plane setup preference information, mobility module 232 determines UE mobility based on UE speed, movement, and cell count, control module 233 determines and applies a preferred C-plane setup for the UE dynamically.
[0035]
[0036] Although mmWave small cells may work independently, macro-assisted mmWave systems offer the following potential advantages: more robust mobility support, resilience to mmWave link outage, small-area throughput boosting and wide-area signaling coverage. As a result, a new flexible, end-to-end architecture to integrate E-UTRAN and mmWave small cells is needed. Different deployment scenarios demand for different and sometimes conflicting architecture setups. Operators cannot afford a static yet inefficient architecture, nor an ever-changing architecture particularly with ever-changing hardware (UE, RAN, and EPC equipment) requirements. Operators want to have one set of HW that supports all scenarios and even futuristic scenarios at affordable cost (CAPEX/OPEX), yet offering customized services for individual users. The examples may include SDN, NFV, Centralized RAN (C-RAN) etc. Although C-plane and U-plane separation offers flexibility, but different mmWave deployment scenarios still demand for different C-plane architectures.
[0037] In light of the above, the proposed ORCA keeps the same underlying HW architecture intact, but overlay on top of it multiple logical C-plane architecture setups by on-demand software configuration. For each C-plane setup scenario, either the UE or the network operator may trigger SW (re)configuration of the architecture setup based on real-time needs, context/load situations, and UE capability. The same UE may see multiple different logical architecture setups active at different moments that corresponds to different scenarios. The same UE may see different logical architecture setups with different SBSs. Different UEs that have different (mobility, load, or context) scenarios may be configured with different logical architecture setups even if they are served by the same physical entities (MBS, SBS, MME/EPC, etc.) For each architecture setup, there could be further refined C-Plane RRM functional split between the underlying network entities. For the future mmWave deployment scenarios or evolving macrocell E-UTRAN HW, the proposed on-demand architecture may also evolve accordingly without incurring extra CAPEX/OPEX. For example, ORCA may evolve into C-RAN type of architecture easily, as C-RAN type of configuration becomes one of the embodiments of the C-plane architecture setup under ORCA.
[0038]
[0039]
[0040]
[0041]
[0042]
[0043]
[0044] If the answer to step 802 is No, then in step 806, the UE performs scanning, RACH, RRC setup procedure with the selected small cells. In step 811, the UE applies C-plane setup 1 and receiving control signaling from the selected SBS. If the answer to step 804 is yes, then in step 805, the UE checks whether the macrocell has high load and whether the UE has low-mobility. If the answer is yes, then the UE also goes to step 806. If the answer is No, then the UE goes to step 808 and checks whether the UE has high-mobility. If the answer is yes, then the UE goes to step 807. If the answer is No, then the goes to step 809 and performs scanning, RACH, RRC setup procedure with multiple cells (macrocell by MBS and smallcell by SBS). In step 813, the UE applies C-plane setup 3 and receives anchor control signaling from MBS and assisted control signaling from SBS.
[0045] When UE is in C-plane setup 2 (step 812), if the UE slows down and an active mmWave link becomes operational, then the UE can trigger C-plane setup transition and change to setup 3 (step 813). If the UE then settles down in an mmWave smallcell, then the UE can trigger another C-plane setup transition and change to setup 1 (step 811). If the UE starts moving or if the existing mmWave link degrades, then the UE again triggers C-plane setup transition and changes back to setup 3 (step 813). Finally, if the UE speeds up or if the existing mmWave link degrades, then the UE triggers another C-plane setup transition and change to setup 2 (step 812).
[0046]
[0047] If the answer to step 902 is No, then in step 903, the MBS checks whether there is too many low-mobility UEs in C-plane setup 2 and setup 3. If the answer is No, then the MBS goes to step 906 directly. If the answer is yes, then the MBS goes to step 905 and suggests the UE to transition to C-plane setup 1 or setup 3 and then goes back to step 901.
[0048] If the answer to step 906 is No, then in step 907, the MBS checks whether a UE has triggered transition request between C-plane setup 1 and setup 3. If the answer is no, then the MBS goes back to step 901. If the answer is yes, then the MBS goes to step 909 and performs X2 sync-up with the target SBS about anchor RRC switching for the UE. In step 911, the MBS performs RRC connection update. Finally, the MBS updates MME and macrocell RRC state and record in step 910. The MBS then goes back to step 901 repeating the operation.
[0049]
[0050] If the answer to step 1002 is yes, then in step 1003, the SBS suggests the UE to transition to C-plane setup 3 and then goes back to step 1001. If the answer to step 1004 is also yes, then in step 1005, the SBS suggests the UE to transition to C-plane setup 1 or setup 2 and then goes back to step 1001.
[0051] If the answer to step 1006 is no, then in step 1007, the SBS checks whether a UE has triggered C-plane transition request to get out of setup 3. If the answer is no, then the SBS goes back to step 1001. If the answer is yes, then the MBS goes to step 1009 and performs X2 sync-up with the MBS about anchor RRC switching or macro fallback for the UE. In step 1011, the SBS performs RRC connection update. Finally, the SBS updates MME and smallcell RRC state and record in step 1010. The SBS then goes back to step 1001 repeating the operation.
[0052]
[0053]
[0054] Although the present invention has been described in connection with certain specific embodiments for instructional purposes, the present invention is not limited thereto. Accordingly, various modifications, adaptations, and combinations of various features of the described embodiments can be practiced without departing from the scope of the invention as set forth in the claims.