WO2017082949A1 - Gestion de mobilité pour réseaux d'accès radio définis par un logiciel - Google Patents

Gestion de mobilité pour réseaux d'accès radio définis par un logiciel Download PDF

Info

Publication number
WO2017082949A1
WO2017082949A1 PCT/US2016/025403 US2016025403W WO2017082949A1 WO 2017082949 A1 WO2017082949 A1 WO 2017082949A1 US 2016025403 W US2016025403 W US 2016025403W WO 2017082949 A1 WO2017082949 A1 WO 2017082949A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
controller
controller device
ran
handover
Prior art date
Application number
PCT/US2016/025403
Other languages
English (en)
Inventor
Alexander Sirotkin
Feng Yang
Xu Zhang
Original Assignee
Intel Corporation
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 Corporation filed Critical Intel Corporation
Priority to TW105132749A priority Critical patent/TWI714647B/zh
Priority to TW109146234A priority patent/TWI778479B/zh
Publication of WO2017082949A1 publication Critical patent/WO2017082949A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/10—Reselecting an access point controller
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • LTE Long-Term Evolution
  • An LTE cellular communication system may include a Radio Access Network (RAN) section and a "core" network section.
  • the RAN section may handle the wireless (radio) communications with the mobile devices.
  • the "core” section may handle control functionality relating to providing data services to the mobile devices.
  • UDN ultra-dense radio access networks
  • SC standalone small cells
  • UDN deployments may be used in either outdoor or indoor traffic hotspots where additional capacity is needed.
  • UDN deployments can result in additional challenges, such as inter-cell interference.
  • a large number of small cells can lead to a high volume of signaling messages, from the small cells, in the network core.
  • Fig. 1 is a diagram of an example environment, corresponding to a cellular network, in which systems and/or methods described herein may be implemented;
  • Fig. 2 is a flowchart illustrating a process for performing an intra-controller handover in the environment of Fig. 1 ;
  • Fig. 3 is a signal flow diagram illustrating an example intra-controller handover
  • Fig. 4 is a diagram of environment that particularly illustrates multiple controllers
  • Fig. 5 is a flowchart illustrating a process for performing an inter-controller handover in the environment of Fig. 1 ;
  • Fig. 6 is a signal flow diagram illustrating an example inter-controller handover; and Fig. 7 illustrates example components of an electronic device.
  • SDN Software Defined Network
  • the described architecture separates the control plane and the user plane in the RAN.
  • a controller in the RAN, may serve a number of base stations and perform mobility management control functions (i.e., functions related to handovers), via the control plane, for base stations in the RAN.
  • User plane traffic may be separately communicated between base stations and an SDN switch.
  • the SDN switch in the RAN, may be used to route data plane traffic and terminate the backhaul connection towards the core network.
  • the control and user plane separation may facilitate efficient mobility management decisions by the controller. Additionally, the control and user plane separation may enable multiple base stations to be associated with a "virtual" cell, in which mobility management decisions within the virtual cell may be hidden (i.e., may not need to be communicated) from the core network. In this manner, the amount of signaling with the core network can be reduced.
  • intra-controller handover operations i.e., between base stations within a virtual cell
  • inter-controller handover operations i.e., between base stations in different virtual cells
  • a control plane handover may first be performed between the controllers of the different virtual cells.
  • the user plane handover between base stations may then be performed.
  • Fig. 1 is a diagram of an example environment 100, corresponding to a cellular network, in which systems and/or methods described herein may be implemented.
  • Environment 100 may generally provide a Software Defined Network (SDN)-based architecture, in the RAN, that separates control plane signaling and user plane data traffic.
  • SDN Software Defined Network
  • the RAN control plane interface is illustrated with dashed lines and the RAN user plane interface is illustrated with solid lines.
  • environment 100 may include mobile devices, which may be referred to as User Equipment (UE) 105, a RAN 110, and an Evolved Packet Core (EPC) 130.
  • Environment 100 may represent a wireless cellular communications network, such as a network based on the Third Generation Partnership Project (3GPP) standards.
  • RAN 110 may generally provide the wireless (e.g., radio) interface with UE 105.
  • the core portion may provide back-end control plane and user plane transport paths, user control and authentication, and other features.
  • UE 105 may include a portable computing and communication device, such as a personal digital assistant (PDA), a smart phone, a cellular phone, a laptop computer with connectivity to a cellular wireless network, a tablet computer, etc.
  • PDA personal digital assistant
  • UE 105 may also include non-portable computing devices, such as desktop computers, consumer or business appliances, or other devices that have the ability to wirelessly connect (e.g., via radio links) to cellular wireless network.
  • non-portable computing devices such as desktop computers, consumer or business appliances, or other devices that have the ability to wirelessly connect (e.g., via radio links) to cellular wireless network.
  • a single UE 105 is shown. In practice, multiple UEs 105 may operate in the context of a wireless network.
  • RAN 110 may represent a 3GPP access network that includes one or more Radio Access Technologies (RATs).
  • RATs Radio Access Technologies
  • RAN 110 may include one or more base stations, such as macrocells 112 and small cells 114.
  • RAN 110 may additionally include a controller 120 and a SDN switch 125.
  • base stations such as macrocells 112 and small cells 114
  • Evolved NodeBs eNBs
  • macrocells 112 and small cells 114 may include less control logic. Instead, the control logic may be
  • Macrocells 112 may provide a radio interface, for UEs 105, to a relatively larger area than small cells 114. Small cells 114 may be deployed to increase system capacity and can include coverage areas within the coverage area of macrocell 112. Small cells 114 may include, for example, picocells, femtocells, and/or home NodeBs. Macrocells 112 and small cells 114 may implement, for example, logic relating to Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) processing, Medium Access Control (MAC) layer processing, and Physical (PHY) layer processing.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Physical
  • Controller 120 may include one or more computation and communication devices that act as a control node for RAN 110. Although a single controller is shown in Fig. 1, in practice, multiple controllers 120 may be used to control RAN 110, where each controller 120 may be assigned to control a number of base stations (e.g., macrocells 112 and/or small cells 114). The base stations assigned to a particular controller 120 may be referred to as a "virtual cell" herein. Controller 120 may operate to perform the control functions for the air interface of RAN 110. For instance, as shown in Fig. 1 as non-limiting examples, controller 120 may perform control functions relating to: (1) Radio Resource Control (RRC) signaling; (2) Radio Resource
  • RRC Radio Resource Control
  • RRM Radio Resource Management
  • SON Self-Organizing Networks
  • BS base station
  • SI -Application Protocol Sl-AP
  • X2-AP Application Protocol
  • controller 120 may perform control functions relating to the RRC protocol sublayer that relates to the LTE air interface between UEs 105 and the base stations. Services and functions provided by the RRC sublayer may include broadcasting of System Information related to the non-access stratum (NAS), broadcasting of System
  • NAS non-access stratum
  • controller 120 may analyze and control radio resources, such as to manage co-channel interference and other wireless radio transmission characteristics. For example, controller 120 may control parameters, at macrocell 112 and small cells 114, relating to radio transmit power, user allocation, beamforming, data rates, the modulation scheme being used, the error coding scheme being used, etc. Controller 120 may also, in some implementations, control SON parameters at the base stations and/or at SDN switch 125. The SON parameters may generally relate to self-configuration, self- optimization, and self-healing of the base stations.
  • Controller 120 may also, in some implementations, control base stations ("BS Ctrl"), such as controlling of the provisioning and operation of macro cells 112 and small cells 114. Controller 120 may also, in some implementations, perform functions for the SI -Application Protocol signaling between RAN 110 and EPC 130.
  • the Sl-AP signaling messages may be routed through SDN switch 125 to EPC 130.
  • the S l-AP signaling messages may include, for example, signaling relating to UE capability information, context transfer, SI interface management, and/or other application protocol functions.
  • controller 120 may also perform functions for the X2-AP signaling.
  • the X2-AP signaling messages may relate to, for example, UE mobility management and load management. Controller 120 may also perform functions relating to SDN configuration and control (SDN Ctrl). For example, controller 120 may update routing tables in SDN switch 125 or update/configure other networking aspect of SDN switch 125.
  • SDN Ctrl SDN configuration and control
  • SDN switch 125 may be a SDN device that operates to connect RAN 110 to EPC 130.
  • SDN switch 125 may be configured by controller 120.
  • SDN switch 125 may include functionality of a router or another networking device.
  • Software-defined networking in general, refers to an approach to computer networking that allows network administrators to manage network services through abstraction of higher-level functionality. In SDN, decisions about where traffic is sent (the control plane) may be decoupled from systems that forward traffic to the selected destination (the data plane).
  • configuration of the SDN aspects may be performed using the OpenFlow protocol.
  • OpenFlow is a communications protocol that gives access to the forwarding plane of a network switch or router, such as SDN switch 125.
  • controller 120 may communicate, using OpenFlow messages, (labeled as interface "OF” in Fig. 1), to SDN switch 125, to configure the encapsulation, the de-capsulation, and routing of packets (e.g., GPRS Tunneling Protocol (GTP) user plane packets).
  • GTP GPRS Tunneling Protocol
  • controller 120 may communicate, using messages (labeled as interface "OF-w" in Fig. 1), with the base stations to configure the base stations; set up, modify, and/or delete wireless pipes associated with the base stations; and perform aerial (radio) coordination.
  • An interface may refer to a physical or logical connection between devices in environment 100.
  • the user plane "Xi" and "S I" interfaces are illustrated in Fig. 1.
  • the Xi interfaces may be used to transfer payload data (e.g., Sl-U payload data) between the base stations and SDN switch 125.
  • the SI interfaces which may include the 3GPP SI -user plane (Sl-U) interface, may be used to transfer the payload data between SDN switch 125 and various devices (e.g., SGW 142 and MME 144) of EPC 130.
  • EPC 130 may include a number of network devices, including serving gateway (SGW) 142, Mobility Management Entity (MME) 144, and packet data network gateway (PGW) 146.
  • SGW 142 may include one or more network devices that aggregate traffic received from one or base stations.
  • SGW 142 may generally handle user (data) plane traffic.
  • MME 144 may include one or more computation and communication devices that perform operations to register UE 105 with EPC 130, and/or perform other operations.
  • MME 144 may generally handle control plane traffic.
  • PGW 146 may include one or more devices that act as the point of interconnect between core network 140 and external IP networks and/or operator IP services. PGW 146 may route packets to and from the access networks, and external IP networks.
  • the quantity of devices and/or networks, illustrated in Fig. 1, is provided for explanatory purposes only. In practice, there may be additional devices and/or networks; fewer devices and/or networks; different devices and/or networks; or differently arranged devices and/or networks than illustrated in Fig. 1. Alternatively, or additionally, one or more of the devices of environment 100 may perform one or more functions described as being performed by another one or more of the devices of environment 100. Furthermore, while “direct" connections are shown in Fig. 1, these connections should be interpreted as logical communication pathways, and in practice, one or more intervening devices (e.g., routers, gateways, modems, switches, hubs, etc.) may be present.
  • intervening devices e.g., routers, gateways, modems, switches, hubs, etc.
  • the OF-w interface may be a control interface used, by controller 120, to control the operation of macro cell 112 and/or small cells 140.
  • One example implementation of OF-w messages are listed in Table I.
  • the "message name” column includes potential names or message labels, and the "description of main fields” column includes a more detailed description of the fields and/or function of the various messages.
  • Fig. 2 is a flowchart illustrating a process 200 for performing a handover operation in environment 100.
  • the handover operation may be an intra-controller handover operation. That is, the handover operation may be between base stations that are connected to a particular controller 120.
  • Process 200 may be performed by controller 120.
  • the term "source” base station will be used to refer to, in the context of a network handover, the beginning base station to which the UE is attached.
  • target base station will be used to refer to, in the context of a network handover, the base station at the end of the handover procedure to which the UE is attached.
  • Process 200 may include determining that a handover should occur (block 210).
  • the handover operation is an intra-controller handover.
  • the handover operation may be handover from one of small cells 114 to the other of small cells 1 14.
  • the determination of the handover may be made based on a number of factors.
  • UE 105 may occasionally or periodically measure the strength of signals received by UE 105 from various cells in the vicinity of UE 105.
  • UE 105 may report, to controller 120, the measurements.
  • Controller 120 may determine, based on the received measurements and potentially based on other factors, such as congestion or load of other base stations that are in the virtual cell of controller 120, to initiate a handover operation to cause the UE to attach to a different base station (e.g., to a different small cell 114).
  • a different base station e.g., to a different small cell 114.
  • controller 120 may additionally use trajectory or velocity information relating to UE 105, to select appropriate base stations for a handover.
  • Process 200 may further include updating the SDN switch, associated with the virtual cell (block 220).
  • the updating of SDN switch 125 may include, for example, updating the routing/s witching table of SDN switch 125 to modify entries, corresponding to the traffic flow or flows associated with UE 105, such that traffic from the target base station will continue to be forwarded to the correct entity (e.g., the correct SGW 142) in EPC 130.
  • the updating of SDN switch 125 may be performed using the OF interface.
  • Process 200 may further include updating the source base station using the OF-w interface (block 230). For instance, with respect to the messages indicated in Table I, controller 120 may transmit the "UE handover command" message to the source base station. The source base station may respond with a "UE status report” message back to controller 120.
  • Process 200 may further include updating the target base station using the OF-w interface (block 240).
  • the target base station may be updated to indicate that the UE will attach to the target base station.
  • controller 120 may transmit the "UE context setup" message to the target base station, which may provide context information, for the UE, to the target base station.
  • controller 120 controls each of the base stations in the virtual cell of controller
  • controller 120 has knowledge of the state of the base stations in the virtual cell (e.g., the traffic loading state of each base station, the available radio resources, etc.). Accordingly, when performing the intra-controller handover procedure pursuant to process 200, controller 120 can more effectively control the handover operation. As a result, handover failure caused by a handover being initiated with an improper target base station (e.g., one that is highly loaded and does not have sufficient radio resource), may be reduced.
  • an improper target base station e.g., one that is highly loaded and does not have sufficient radio resource
  • Fig. 3 is a signal flow diagram illustrating an example intra-controller handover involving various devices in environment 100.
  • the source base station and target base station are labeled as source base station 310 and target base station 320, respectively.
  • UE 105 and controller 120 may exchange measurement information relating to the connectivity of UE 105 to the source base station or to other base stations (at 305,
  • UE 105 may communicate signal strength measurements corresponding to the various base stations in the vicinity of UE 105. Controller 120, based on the signal strength measurements, may make handover (HO) decisions relating to UE 105 (at 310, "HO decision"). For example, when the signal strength received from the base station, to which the UE is currently attached (source base station 310), falls below a threshold, controller 120 may choose another base station (target base station 320) to which the UE should attach.
  • Target base station 320 may be chosen as another base station, in the vicinity of the UE, in which the signal strength between the UE and target base station 320 is above a threshold and in which the target base station has available radio resources.
  • controller 120 may be able to make an optimal, or near optimal, handover decision.
  • the measurement information can be communicated, from the base station to the controller, by transparently transferring RRC messages (received from the UE) to the controller, via the OF-w interface (i.e., via the control plane interface).
  • RRC messages received by the base station may be encapsulated, by the base station, as OF-w messages and sent to controller 120.
  • Controller 120 may subsequently modify SDN switch 125, such as by modifying the routing table associated with SDN switch 125, to update SDN switch 125 such that SDN switch 125 will buffer packets received for UE 105 (at 315, "modify flow entry").
  • the modification may particularly include deleting traffic flow entries associated with bearers in the SDN switch, to thus cause received packets associated with the bearers to be buffered by the SDN switch.
  • the buffering may be performed until the handover operation is completed.
  • the OF interface may be used to modify an entry to the routing table, of SDN switch 125, to cause SDN switch 125 to buffer packets received for UE 105.
  • Controller 120 may subsequently transmit a UE handover command message to source base station 310 (at 320, "UE handover command”).
  • the UE handover command may be transmitted, via the OF-w interface, and may correspond to the message "UE handover command” (Table I).
  • the message may include, for instance, an identification of UE 105 and an indication of the RRC connection(s) that are to be reconfigured.
  • source base station 310 may initiate the RRC connection reconfiguration with UE 105 (at 325, "RRC connection reconfiguration”).
  • Source base station 310 may update controller 120 with a status report relating to the RRC reconfiguration (at 330, "UE status report”).
  • the UE status report may be transmitted, via the OF-w interface, and may correspond to the message "UE status report” (Table I).
  • Controller 120 may subsequently inform target base station 220 of the handover.
  • UE context information needed to process the handover in a manner that will not cause interruption at the UE, may be transmitted to target base station 320.
  • controller 120 may transmit a UE context setup message, via the OF-w interface, to target base station 320 (at 335, "UE context setup").
  • the UE context setup message may include a number of information fields, including a UE identification field, security information, dedicated bear configuration information, and random access channel (RACH) configuration information.
  • RACH random access channel
  • a RACH procedure may be performed. For instance, as shown, a random access preamble may be transmitted from UE 105 to target base station 320 and the random access response may be transmitted from target base station 320 to UE 105 (at
  • packets received at SDN switch 125 may be buffered at SDN switch 125 (at 350, "packet buffering”).
  • the handover operation, in the air interface may be completed based on the communication, between UE 105 and target base station 320, of an "RRC connection reconfiguration complete” message (at 355).
  • target base station 320 may transmit an "UL RRC message transfer" message to controller 120 (at 360), and controller 120 may additionally release the UE context from source base station 310 (at 365, "UE context release”).
  • Controller 120 may modify SDN switch 125, such as by modifying the routing table associated with SDN switch 125, to update SDN switch 125 such that SDN switch 125 will appropriately forward traffic flows received from target base station 320 to EPC 130, and forward traffic flows received from EPC 130 to target base station 320 (at 370, "modify flow entry").
  • the OF interface may be used to add an entry to the routing table, of SDN switch 125, to forward traffic flows, corresponding to UE 105 and from target base station 320, to EPC 130.
  • Fig. 4 is a diagram of environment 100 that particularly illustrates multiple controllers 120.
  • each controller 120 may control a number of base stations, where the set of base stations controlled by a particular controller 120 may be referred to herein as the virtual cell for controller 120.
  • two controllers 120 are shown, labeled as controller 120-1 and controller 120-2.
  • four base stations are illustrated, labeled as base stations 405-420.
  • Base stations 405 and 410 are illustrated as being affiliated with controller 120-1, and base station 420 is illustrated as being affiliated with controller 120-2.
  • Base station 415 may connect, via control plane message, to both base controllers 120-1 and 120-2.
  • This base station may be considered to be in an "inter-controller handover (HO) zone” that is affiliated with both controller 120-1 and 120-2 (i.e., both controllers 120 may control base station 415).
  • Base stations 405, 410, and 420 in contrast, may be considered to be in an "intra- controller handover (HO) zone," as these base stations are only potentially controlled by one controller.
  • HO inter-controller handover
  • Whether a particular base station is potentially connected to multiple controllers 120 (inter-controller HO zone) or to a single controller 120 may be statically determined (e.g., configured by a network administer) or dynamically determined and configured by the network.
  • Fig. 5 is a flowchart illustrating a process 500 for performing a handover operation in an inter-controller handover scenario.
  • the term "source” will be used to refer to, in the context of a network handover, the beginning network device (i.e., base station, controller, or SDN switch) to which the UE is affiliated at the beginning of the handover operation.
  • the term “target” will be used to refer to, in the context of a network handover, the ending network device (i.e., base station, controller, or SDN switch) to which the UE is affiliated at the completion of the handover operation.
  • Process 500 may include determining that a handover operation should occur (block 510).
  • the handover operation is an inter-controller handover. That is, the source base station may be associated with a different controller 120 than the target base station or the source base station may be a base station that is in an inter-controller handover zone.
  • the source base station may be associated with a different controller 120 than the target base station or the source base station may be a base station that is in an inter-controller handover zone.
  • Controller 120-1 may determine (e.g., on the basis of the UE's historical data, including trajectory, location, velocity, observed neighboring cells, etc.) that a handover is appropriate and that the target base station is base station 420, which is affiliated with controller 120-2 (the target controller).
  • the source controller may transmit a handover request to the target controller (block
  • Process 500 may further include affiliating the target controller (controller 120-2), with the UE, as the active controller (block 530).
  • Process 500 may further include affiliating the target SDN switch (e.g., SDN switch 125-2), with the UE, as the active switch (block 540).
  • the configuration that is performed in blocks 520-540 may all be performed in the control plane of the RAN.
  • Process 500 may further include signaling the EPC to request the handover operation (block 550).
  • the target controller may communicate with EPC 130, such as with SGW 142 and MME 144, to request bearer modifications, in EPC 130, relating to the handover.
  • Process 500 may further include performing the intra- controller handover procedure (block 560). In this manner, the handover between the source and target base station may be performed.
  • Fig. 6 is a signal flow diagram illustrating an example inter-controller handover involving various devices in environment 100.
  • the inter-controller handover procedure can be divided into two phases.
  • the first phase includes control plane operations relating to switching the active controller 120 (and, if a different SDN switch 125 is being used by the target controller, switching the SDN switch) and notifying EPC 130.
  • the second phase follows the intra-controller handover operation, as discussed with respect to Figs. 2 and 3.
  • UE 105 may initially be communicating, with SGW 142 of the EPC, using source base station 415 and source SDN switch 125-1 (at 605, "packet data").
  • source controller 120-1 may determine that a handover operation should be performed (at 610, "HO decision").
  • the handover decision may be based on information such as the trajectory of the UE, the location of the UE, the velocity of the UE, signal strength measurements made by the UE, etc.
  • the handover decision may involve a handover between base stations in different virtual cells, such as, with reference to Fig. 4, a handover that involves base stations associated with two different controllers 120 (e.g., between source base station 415 and target base station 420).
  • Source controller 120-1 may transmit a handover request to target controller 120-2 (at
  • the handover request may be made via a control plane signaling in RAN 110.
  • the handover request may be acknowledged by target controller 120-2 (at 620, "handover request ACK").
  • Source controller 120-1 may indicate, to source base station 415, that the controller and SDN switch that are to be used, for the particular UE, are being switched to target controller 120-2, and target SDN switch 125-2 (at 625, "controller and anchor switch”).
  • Target controller 120-2 may correspondingly update target SDN switch 125-2 to modify or add entries for the traffic flows, corresponding to the UE (at 630, "modify flow entry").
  • Target controller 120-2 may inform EPC 130 of the handover. As shown, target controller 120-2 may transmit a path switch request to MME 144 (at 635, "path switch request”). In response, MME 144 may control SGW 142 to modify the bearer path (at 640, "modify bearer request”). SGW 142 may switch the downlink (DL) path for the bearer (at 142, "switch DL path”). At this point, packet data communicated between SGW 142 and UE 105 may be transmitted via target SDN switch 152-2 and source base station 415. Acknowledgement of the downlink path switch may be transmitted back to target controller 120-2 (at 655 and 660, "modify bearer response” and “path switch response”).
  • the target controller and target SDN switch are affiliated with UE 105, and the handover procedure may be completed as in the intra-controller handover procedure (described with respect to Figs. 2 and 3) (at 665, "intra-controller handover procedure").
  • high-density radio access networks may be employed in a flexible manner and in which signaling to the core network, due to handovers, may be reduced.
  • core network signaling may only be needed for inter-controller handovers.
  • Handovers within the virtual cell of a controller may be handled in the RAN.
  • circuitry or “processing circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • Fig. 7 illustrates, for one embodiment, example components of an electronic device 700.
  • the electronic device 700 may be a UE, a base station, an SDN switch, a controller (e.g., controller 120), an MME, PGW, or SGW.
  • the electronic device 700 may include application circuitry 702, baseband circuitry 704, Radio Frequency (RF) circuitry 706, front-end module (FEM) circuitry 708 and one or more antennas 760, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • the RF circuitry 706, FEM circuitry 708, and antennas 760 may be omitted. In other embodiments, any of said circuitries can be included in different devices.
  • Application circuitry 702 may include one or more application processors.
  • the application circuitry 702 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 memory /storage may include, for example, computer-readable medium 703, which may be a non-transitory computer-readable medium.
  • Application circuitry 702 may, in some embodiments, connect to or include one or more sensors, such as environmental sensors, cameras, etc.
  • Baseband circuitry 704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 704 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 706 and to generate baseband signals for a transmit signal path of the RF circuitry 706.
  • Baseband processing circuitry 704 may interface with the application circuitry 702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 706.
  • the baseband circuitry 704 may include a second generation (2G) baseband processor 704a, third generation (3G) baseband processor 704b, fourth generation (4G) baseband processor 704c, and/or other baseband processor(s) 704d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 7G, etc.).
  • the baseband circuitry 704 e.g., one or more of baseband processors 704a-d
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • baseband circuitry 704 may be wholly or partially implemented by memory /storage devices configured to execute instructions stored in the memory/storage.
  • the memory /storage may include, for example, a non-transitory computer-readable medium 704h.
  • modulation/demodulation circuitry of the baseband circuitry 704 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 704 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 704 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
  • EUTRAN evolved universal terrestrial radio access network
  • PHY physical
  • MAC media access control
  • RLC radio link control
  • a central processing unit (CPU) 704e of the baseband circuitry 704 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 704f.
  • the audio DSP(s) 704f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • the baseband circuitry 704 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), and/or radio resource control (RRC) elements.
  • a central processing unit (CPU) 704e of the baseband circuitry 704 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 704f.
  • the audio DSP(s) 104f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Baseband circuitry 704 may further include memory /storage 704g.
  • the memory /storage 704g may be used to load and store data and/or instructions for operations performed by the processors of the baseband circuitry 704.
  • Memory /storage 704g may particularly include a non- transitory memory.
  • Memory /storage for one embodiment may include any combination of suitable volatile memory and/or non-volatile memory.
  • the memory /storage 704g 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
  • memory /storage 704g 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 704 and the application circuitry 702 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 704 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 704 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
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 704 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 706 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 706 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 706 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 704.
  • RF circuitry 706 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 708 for transmission.
  • the RF circuitry 706 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 706 may include mixer circuitry 706a, amplifier circuitry 706b and filter circuitry 706c.
  • the transmit signal path of the RF circuitry 706 may include filter circuitry 706c and mixer circuitry 706a.
  • RF circuitry 706 may also include synthesizer circuitry 706d for synthesizing a frequency for use by the mixer circuitry 706a of the receive signal path and the transmit signal path.
  • the mixer circuitry 706a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 708 based on the synthesized frequency provided by synthesizer circuitry 706d.
  • the amplifier circuitry 706b may be configured to amplify the down-converted signals and the filter circuitry 706c 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.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 704 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 706a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • electronic device 700 when the electronic device 700 is implemented as part of a base station or a controller, electronic device 700 may include an apparatus for controlling the mobility of UEs.
  • the electronic device may include handover circuitry, or other logic, to determine that the UE should be switched, from a source (serving) base station; determine whether the source base station lies within an intra-controller handover zone or an inter- controller-handover zone; select one or more of a target base station or target controller for the UE to be switched to; and cause switchover of the connection between the UE and the serving base station to the target base station.
  • the mixer circuitry 706a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 706d to generate RF output signals for the FEM circuitry 708.
  • the baseband signals may be provided by the baseband circuitry 704 and may be filtered by filter circuitry 706c.
  • the filter circuitry 706c 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 706a of the receive signal path and the mixer circuitry 706a 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 706a of the receive signal path and the mixer circuitry 706a 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 706a of the receive signal path and the mixer circuitry 706a may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a 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 706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 704 may include a digital baseband interface to communicate with the RF circuitry 706.
  • 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 706d may be a fractional-N synthesizer or a fractional N/N+6 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 706d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 706d may be configured to synthesize an output frequency for use by the mixer circuitry 706a of the RF circuitry 706 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 706d may be a fractional N/N+6 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 704 or the applications processor 702 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 702.
  • Synthesizer circuitry 706d of the RF circuitry 706 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 (DP A).
  • the DMD may be configured to divide the input signal by either N or N+6 (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 706d 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 706 may include an IQ/polar converter.
  • FEM circuitry 708 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 760, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 706 for further processing.
  • FEM circuitry 708 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 706 for transmission by one or more of the one or more antennas 760.
  • the FEM circuitry 708 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 706).
  • the transmit signal path of the FEM circuitry 708 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 706), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 760.
  • PA power amplifier
  • the electronic device 700 may include additional elements such as, for example, memory/storage, display, camera, sensors, and/or input/output (I/O) interface.
  • the electronic device of Fig. 7 may be configured to perform one or more methods, processes, and/or techniques such as those described herein.
  • a controller device for a radio access network (RAN) of a cellular communication network may include circuitry to: receive measurement information relating to a strength of a connectivity of User Equipment (UE) to a source base station of a plurality of base stations in the RAN; determine, based on the received measurement information, to perform a handover operation; and when the source base station is affiliated with a second controller device in the RAN, perform an inter-controller handover operation in which the circuitry is further to: determine the second controller device as a controller device with which the UE is to be affiliated, and communicate with the second controller device to switch an affiliation of the UE from the controller device to the second controller device.
  • UE User Equipment
  • the circuitry is further to: store affiliations of the plurality of base stations, to controller devices to which the plurality of base stations are affiliated, at least some of the plurality of the base stations being affiliated with the controller device and others of the plurality of the base stations being affiliated with the controller device and with the second controller device in the RAN; and when the source base station is affiliated with the controller device and not the second controller device, perform an intra-controller handover operation in which the circuitry is further to: determine a target base station to which the UE is to attach after completion of the handover operation, modify configuration of a Software Defined Network (SDN) switch, in the RAN, to indicate that traffic flows with the UE should be communicated with a core portion of the cellular communication network via the SDN switch and the target base station.
  • SDN Software Defined Network
  • example 3 the subject matter of example 1 or 2, or any of the examples herein, may further include wherein the measurement information and the configuration of the SDN switch is performed via control plane interfaces.
  • example 4 the subject matter of example 1 or 2, or any of the examples herein, may further include wherein the circuitry is further to: inform, during an inter-controller handover operation, a core portion of the cellular communication network, of the handover operation, and refrain from informing the core portion of the cellular communication network during an intra- controller handover operation.
  • example 5 the subject matter of example 4, or any of the examples herein, may further include wherein informing the core portion of the cellular network includes transmitting a path switch request to a Mobility Management Entity (MME).
  • MME Mobility Management Entity
  • example 6 the subject matter of example 1 or 2, or any of the examples herein, may further include wherein the measurement information includes measurement information, obtained by the UE, and forwarded, from the source base station to the control device, via a control plane interface.
  • the measurement information includes measurement information, obtained by the UE, and forwarded, from the source base station to the control device, via a control plane interface.
  • example 7 the subject matter of example 2, or any of the examples herein, may further include wherein the determination of the target base station includes determining an optimal target base station based on load information relating to the plurality of base stations.
  • example 8 the subject matter of example 2, or any of the examples herein, may further include wherein the configuration of the SDN switch includes deleting one or more traffic flow entries to the SDN switch to cause buffering of packets, associated with the traffic entries, at the SDN switch.
  • the subject matter of example 8, or any of the examples herein may further include wherein the modification to the SDN switch additionally includes adding traffic flow entries to the SDN switch to cause the traffic flows to be communicated with the target base station.
  • the subject matter of examples 8 or 9, or any of the examples herein may further include wherein the modifications to the SDN? switch are performed via a control plane in the RAN.
  • a computer readable medium may contain program instructions for causing one or more processors, associated with a controller device for a radio access network (RAN) of a cellular communication network, to: store an indication of a plurality of base stations, in the RAN, to which the controller device is affiliated, at least some of the plurality of the base stations being affiliated with the controller device and others of the plurality of the base stations being affiliated with the controller device and with a second controller device in the RAN; receive measurement information relating to a strength of the connectivity of the UE to a source base station of the plurality of base stations, in the RAN, and to which the UE is attached; determine, based on the received measurement information, to perform a handover operation, as an inter-controller handover operation, when the source base station is affiliated with another controller device in the RAN, wherein the one or more processors, as part of performance of the inter-controller handover, are further to: determine the second controller device as a controller device with which the UE is to be affiliated, and
  • example 12 the subject matter of example 11, or any of the examples herein, may further include wherein the program instructions are further to cause the one or more processors to: determine, based on the received measurement information, to perform a handover operation, as an intra-controller handover operation, when the source base station is not affiliated with another controller device in the RAN, wherein the one or more processors are further to:
  • SDN Software Defined Network
  • example 13 the subject matter of example 12, or any of the examples herein, may further include wherein the measurement information and the configuration of the SDN switch is performed via control plane interfaces.
  • example 14 the subject matter of example 12, or any of examples herein, may further include wherein the program instructions are further to cause the one or more processors to: inform, during an inter-controller handover operation, a core portion of the cellular
  • example 15 the subject matter of example 14, or any of the examples herein, may further include wherein informing the core portion of the cellular network includes transmitting a path switch request to a Mobility Management Entity (MME).
  • MME Mobility Management Entity
  • example 16 the subject matter of example 21, or any of examples herein, may further include wherein the measurement information includes measurement information, obtain by the UE, and forwarded, from the source base station to the control device, via a control plane interface.
  • the measurement information includes measurement information, obtain by the UE, and forwarded, from the source base station to the control device, via a control plane interface.
  • example 17 the subject matter of example 12, or any of examples herein, may further include wherein the determination of the target base station includes determining an optimal target base station based on load information relating to the plurality of base stations.
  • example 18 the subject matter of example 12, or any of examples herein, may further include wherein the modification to the SDN switch includes deleting one or more traffic flow entries to the SDN switch to cause buffering of packets, associated with the traffic entries, in the SDN switch.
  • example 19 the subject matter of example 18, or any of examples herein, may further include wherein the modification to the SDN switch additionally includes adding traffic flow entries to the SDN switch to cause the traffic flows to be communicated with the target base station.
  • a base station for a cellular communication network may comprise: a radio interface to connect to User Equipment (UE) devices; a control plane interface to connect to a controller device for a radio access network (RAN) of the cellular communication network; a data plane interface to a Software Defined Network (SDN) switch in the RAN; and processing circuitry to: decode a Radio Resource Control (RRC) layer measurement report received over the radio interface from a particular UE, of the UE devices, the measurement report indicating a strength of the connectivity of the particular UE to the base station; cause providing of the measurement report, to the controller device, via the control plane interface; cause transmission of the received user plane data, to a core portion of the cellular communications network, via the data plane interface; process an indication, from the controller device, to perform a handover of the particular UE with a second base station; and cause transmission, via the radio interface, of a RRC connection reconfiguration message to the particular UE, to cause the particular UE to initiate communication with the second base
  • RRC Radio Resource Control
  • control plane interface includes an OpenFlow-based interface.
  • control plane interface connects the base station to a plurality of controller devices in the RAN.
  • a base station for a cellular communication network may comprise: means for implementing a data plane interface to a Software Defined Network (SDN) switch in Radio Access Network (RAN) of the cellular communications network; and means for receiving, from a particular User Equipment (UE) device, and over a radio interface, a Radio Resource Control (RRC) layer measurement report indicating a strength of the connectivity of the particular UE to a base station; means for providing the measurement report, to a controller device for the RAN of the cellular communication network; means for receiving, from the particular UE and over the radio interface, user plane data; means for transmitting the received user plane data, to a core portion of the cellular communications network, via the data plane interface; means for receiving, from the controller device and based on the provided measurement report, an indication to perform a handover of the particular UE with a second base station; and means for transmitting, in response to the indication to perform the handover, a RRC connection reconfiguration message to the particular UE, via the radio interface, to
  • SDN Software De
  • example 25 the subject matter of example 24, or any of the examples herein, wherein the indication to perform the handover operation is received via the control plane interface.
  • control plane interface includes an OpenFlow-based interface.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Circuits Of Receivers In General (AREA)

Abstract

L'invention concerne une architecture SDN, pour un système de communications cellulaires, qui sépare le plan de contrôle et le plan d'utilisateur dans un RAN du système de communications cellulaires. Un contrôleur, dans le RAN, peut servir un certain nombre de stations de base et assurer des fonctions de contrôle de gestion de mobilité (par ex. des fonctions associées aux transferts), par le biais d'un plan de contrôle, pour des stations de base dans le RAN. Le trafic du plan d'utilisateur peut être communiqué séparément entre les stations de base et un commutateur SDN. Le commutateur SDN, dans le RAN, peut être utilisé pour le routage du trafic de plan de données et achever la connexion de liaison secondaire vers le réseau noyau.
PCT/US2016/025403 2015-11-11 2016-03-31 Gestion de mobilité pour réseaux d'accès radio définis par un logiciel WO2017082949A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
TW105132749A TWI714647B (zh) 2015-11-11 2016-10-11 用於軟體定義無線電存取網路的行動管理
TW109146234A TWI778479B (zh) 2015-11-11 2016-10-11 用於軟體定義無線電存取網路的行動管理

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2015094258 2015-11-11
CNPCT/CN2015/094258 2015-11-11

Publications (1)

Publication Number Publication Date
WO2017082949A1 true WO2017082949A1 (fr) 2017-05-18

Family

ID=55754442

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/025403 WO2017082949A1 (fr) 2015-11-11 2016-03-31 Gestion de mobilité pour réseaux d'accès radio définis par un logiciel

Country Status (2)

Country Link
TW (2) TWI778479B (fr)
WO (1) WO2017082949A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10575235B2 (en) 2015-06-10 2020-02-25 At&T Intellectual Property I, L.P. Facilitation of network resource routing and resource optimization
US10637563B2 (en) 2018-08-06 2020-04-28 At&T Intellectual Property I, L.P. Dynamic adjustment of integrated access and backhaul link partition for emergency communications

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI657683B (zh) * 2017-11-21 2019-04-21 中華電信股份有限公司 移除交換器之已完成流程條目的方法及用於移除已完成流程條目的交換器系統

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140254373A1 (en) * 2013-03-08 2014-09-11 Tellabs Operations, Inc. Method and Apparatus for Improving LTE Enhanced Packet Core Architecture Using Openflow Network Controller
US20140269535A1 (en) * 2013-03-15 2014-09-18 Cisco Technology, Inc. Wireless system with split control plane and data plane
US20150103665A1 (en) * 2013-10-14 2015-04-16 Futurewei Technologies Inc. Method, apparatus and system for implementing pdn connections

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9119028B2 (en) * 2010-04-14 2015-08-25 Qualcomm Incorporated Method and apparatus for supporting location services via a Home Node B (HNB)
US20150055623A1 (en) * 2013-08-23 2015-02-26 Samsung Electronics Co., Ltd. MOBILE SOFTWARE DEFINED NETWORKING (MobiSDN)
US9614724B2 (en) * 2014-04-21 2017-04-04 Microsoft Technology Licensing, Llc Session-based device configuration

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140254373A1 (en) * 2013-03-08 2014-09-11 Tellabs Operations, Inc. Method and Apparatus for Improving LTE Enhanced Packet Core Architecture Using Openflow Network Controller
US20140269535A1 (en) * 2013-03-15 2014-09-18 Cisco Technology, Inc. Wireless system with split control plane and data plane
US20150103665A1 (en) * 2013-10-14 2015-04-16 Futurewei Technologies Inc. Method, apparatus and system for implementing pdn connections

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
GURUSANTHOSH P ET AL: "SDMA: A semi-distributed mobility anchoring in LTE networks", 2013 INTERNATIONAL CONFERENCE ON SELECTED TOPICS IN MOBILE AND WIRELESS NETWORKING (MOWNET), IEEE, 19 August 2013 (2013-08-19), pages 133 - 139, XP032490864, DOI: 10.1109/MOWNET.2013.6613809 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10575235B2 (en) 2015-06-10 2020-02-25 At&T Intellectual Property I, L.P. Facilitation of network resource routing and resource optimization
US11337132B2 (en) 2015-06-10 2022-05-17 At&T Intellectual Property I, L.P. Facilitation of network resource routing and resource optimization
US10637563B2 (en) 2018-08-06 2020-04-28 At&T Intellectual Property I, L.P. Dynamic adjustment of integrated access and backhaul link partition for emergency communications
US11336366B2 (en) 2018-08-06 2022-05-17 At&T Intellectual Property I, L.P. Dynamic adjustment of integrated access and backhaul link partition for emergency communications

Also Published As

Publication number Publication date
TWI778479B (zh) 2022-09-21
TWI714647B (zh) 2021-01-01
TW202126008A (zh) 2021-07-01
TW201728126A (zh) 2017-08-01

Similar Documents

Publication Publication Date Title
US20220022105A1 (en) Dual Radio Operation Between Access Systems Using 3GPP Radio Access Technology
EP3305009B1 (fr) Mobilité wlan pour agrégation lte/wlan
US10771214B2 (en) System and method for uplink power contrl framework
EP3482602B1 (fr) Systèmes, procédés et dispositifs de séparation de plan utilisateur de commande pour des réseaux d'accès radio 5g
US11122453B2 (en) Systems, methods and devices for measurement configuration by a secondary node in EN-DC
EP3596999B1 (fr) Retransmission de pdu pdcp par des noeuds centralisés d'une architecture ran
US11792838B2 (en) Bearer-less architecture for a wireless cellular network
US20200110627A1 (en) Centralized unit and distributed unit connection in a virtualized radio access network
US10812169B2 (en) User equipment measurements for new radio
US11140691B2 (en) Long-term evolution (LTE) and wireless local area network (WLAN) aggregation (LWA) connection procedures
US20200305218A1 (en) Lwip enhancements for reliable drb switching
US20190373497A1 (en) Measurement gap configuration for new radio (nr) systems
WO2017078779A1 (fr) Division de plan de commande et de plan d'utilisateur pour réseaux d'accès radio 5g
TWI778479B (zh) 用於軟體定義無線電存取網路的行動管理
WO2018038804A1 (fr) Agrégation lte-wlan (lwa) améliorée utilisant un marqueur final pour un transfert sans changement de terminaison wlan (wt)
WO2018031649A1 (fr) Accès à des technologies existantes au moyen d'un équipement utilisateur
WO2017096531A1 (fr) Commutateur de réseau défini par logiciel et nœud b évolué (enb) pour une connectivité à porteuses multiples
WO2018031139A1 (fr) Prise en charge améliorée d'agrégation x2 et xw de lte-wlan pour un transfert sans changement de terminaison wlan

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

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

Country of ref document: EP

Kind code of ref document: A1