WO2017062014A1

WO2017062014A1 - Radio access network orchestrator for wireless networks

Info

Publication number: WO2017062014A1
Application number: PCT/US2015/054705
Authority: WO
Inventors: Anand Bedekar; Vinh Van Phan; Andrea Cattoni
Original assignee: Nokia Solutions And Networks Oy
Priority date: 2015-10-08
Filing date: 2015-10-08
Publication date: 2017-04-13

Abstract

A technique may include receiving, by a radio access network (RAN) orchestrator, a request for selecting a network convergence service site to host a network convergence service for a service flow or user device in a wireless network, the wireless network including the user device connected to a plurality of base stations, the network convergence service for the service flow or user device responsible for at least coordinating a flow of data to or from the user device via the multiple base stations, selecting one of a plurality of network convergence service hosting sites to host the network convergence service for the service flow or user device, and sending a message to the selected network convergence service hosting site indicating that the selected network convergence service hosting site has been selected to host the network convergence service for the service flow or user device.

Description

Radio Access Network Orchestrator For Wireless Networks

TECHNICAL FIELD

[0001] This description relates to communications.

BACKGROUND

[0002] A communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.

[0003] An example of a cellular communication system is an architecture that is being standardized by the 3^rd Generation Partnership Project (3 GPP). A recent development in this field is often referred to as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. E- UTRA (evolved UMTS Terrestrial Radio Access) is the air interface of 3GPP's Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, base stations or access points (APs), which are referred to as enhanced Node AP (eNBs), provide wireless access within a coverage area or cell. In LTE, mobile devices, or mobile stations are referred to as user equipments (UE). LTE has included a number of improvements or developments. [0004] A global bandwidth shortage facing wireless carriers has motivated the consideration of the underutilized millimeter wave (mm Wave) frequency spectrum for future broadband cellular communication networks, for example. mmWave (or extremely high frequency) may, for example, include the frequency range between 30 and 300 gigahertz (GHz). Radio waves in this band may, for example, have

wavelengths from ten to one millimeters, giving it the name millimeter band or millimeter wave. The amount of wireless data will likely significantly increase in the coming years. Various techniques have been used in attempt to address this challenge including obtaining more spectrum, having smaller cell sizes, and using improved technologies enabling more bits/s/Hz, and/or allowing a more efficient use of resources. One element that may be used to obtain more spectrum is to move to higher

frequencies, above 6 GHz. For fifth generation wireless systems (5G), an access architecture for deployment of cellular radio equipment employing mm Wave radio spectrum has been proposed. Other example spectrums may also be used, such as cm Wave radio spectrum (3-30 GHz).

SUMMARY

[0005] According to an example implementation, a method may include, receiving, by a radio access network (RAN) orchestrator, a request for selecting a network convergence service site to host a network convergence service for a service flow or user device in a wireless network, the wireless network including the user device connected to a plurality of base stations, the network convergence service for the service flow or user device responsible for at least coordinating a flow of data to or from the user device via the multiple base stations; selecting one of a plurality of network convergence service hosting sites to host the network convergence service for the service flow or user device; and sending a message to the selected network convergence service hosting site indicating that the selected network convergence service hosting site has been selected to host the network convergence service for the service flow or user device. [0006] According to another example implementation, an apparatus may include at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to:, receive, by a radio access network (RAN) orchestrator, a request for selecting a network convergence service site to host a network convergence service for a service flow or user device in a wireless network, the wireless network including the user device connected to a plurality of base stations, the network convergence service for the service flow or user device responsible for at least coordinating a flow of data to or from the user device via the multiple base stations; select one of a plurality of network convergence service hosting sites to host the network convergence service for the service flow or user device; and send a message to the selected network convergence service hosting site indicating that the selected network convergence service hosting site has been selected to host the network convergence service for the service flow or user device.

[0007] According to another example implementation, a computer program product may include a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including receiving, by a radio access network (RAN) orchestrator, a request for selecting a network convergence service site to host a network convergence service for a service flow or user device in a wireless network, the wireless network including the user device connected to a plurality of base stations, the network convergence service for the service flow or user device responsible for at least coordinating a flow of data to or from the user device via the multiple base stations; selecting one of a plurality of network convergence service hosting sites to host the network convergence service for the service flow or user device; and sending a message to the selected network convergence service hosting site indicating that the selected network convergence service hosting site has been selected to host the network convergence service for the service flow or user device.

[0008] According to an example implementation, a method may include. receiving, by a radio access network (RAN) orchestrator from a current network convergence service hosting site hosting a network convergence service for one or more user devices in a wireless network, a notification indicating that the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices, the wireless network including the one or more user devices, each user device connected to a plurality of base stations, the network convergence service for one or more user devices responsible for at least coordinating a flow of data to or from one or more of the user devices via the multiple base stations; selecting, by the RAN orchestrator, a target network convergence service hosting site for relocating a network convergence service for one or more user devices; and sending, by the RAN orchestrator to the current network convergence service hosting site, a relocation indication requesting a relocation of one or more network convergence services from the current network convergence service hosting site to the target network convergence service hosting site.

[0009] According to another example implementation, an apparatus may include at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to:, receive, by a radio access network (RAN) orchestrator from a current network convergence service hosting site hosting a network convergence service for one or more user devices in a wireless network, a notification indicating that the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices, the wireless network including the one or more user devices, each user device connected to a plurality of base stations, the network convergence service for one or more user devices responsible for at least coordinating a flow of data to or from one or more of the user devices via the multiple base stations; select, by the RAN orchestrator, a target network convergence service hosting site for relocating a network convergence service for one or more user devices; and send, by the RAN orchestrator to the current network convergence service hosting site, a relocation indication requesting a relocation of one or more network convergence services from the current network convergence service hosting site to the target network convergence service hosting site.

[0010] According to another example implementation, a computer program product may include a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including receiving, by a radio access network (RAN) orchestrator from a current network convergence service hosting site hosting a network convergence service for one or more user devices in a wireless network, a notification indicating that the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices, the wireless network including the one or more user devices, each user device connected to a plurality of base stations, the network convergence service for one or more user devices responsible for at least coordinating a flow of data to or from one or more of the user devices via the multiple base stations; selecting, by the RAN orchestrator, a target network convergence service hosting site for relocating a network convergence service for one or more user devices; and sending, by the RAN orchestrator to the current network convergence service hosting site, a relocation indication requesting a relocation of one or more network convergence services from the current network convergence service hosting site to the target network convergence service hosting site.

[0011 ] According to an example implementation, a method may include, detecting, by a current network convergence service hosting site hosting a network convergence service for one or more user devices in a wireless network, a condition wherein the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices, each user device connected to a plurality of base stations, the current network

convergence service for one or more user devices responsible for at least coordinating a flow of data to or from one or more of the user devices via multiple base stations;

sending, by the current network convergence entity host site to a radio access network (RAN) orchestrator, a notification indicating that the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices; receiving, by the current network convergence service hosting site from the RAN orchestrator, a relocation indication including an indication of a target network convergence service hosting site; and relocating, by the current network convergence service hosting site in response to the relocation indication, a network convergence service for one or more user devices from the current network convergence service hosting site to the target network convergence service hosting site.

[0012] According to another example implementation, an apparatus may include at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to:, detect, by a current network convergence service hosting site hosting a network convergence service for one or more user devices in a wireless network, a condition wherein the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices, each user device connected to a plurality of base stations, the current network convergence service for one or more user devices responsible for at least coordinating a flow of data to or from one or more of the user devices via multiple base stations; send, by the current network convergence entity host site to a radio access network (RAN) orchestrator, a notification indicating that the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices; receive, by the current network convergence service hosting site from the RAN orchestrator, a relocation indication including an indication of a target network convergence service hosting site; and relocate, by the current network convergence service hosting site in response to the relocation indication, a network convergence service for one or more user devices from the current network convergence service hosting site to the target network convergence service hosting site.

[0013] According to another example implementation, a computer program product may include a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including detecting, by a current network convergence service hosting site hosting a network convergence service for one or more user devices in a wireless network, a condition wherein the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices, each user device connected to a plurality of base stations, the current network convergence service for one or more user devices responsible for at least coordinating a flow of data to or from one or more of the user devices via multiple base stations; sending, by the current network convergence entity host site to a radio access network (RAN) orchestrator, a notification indicating that the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices; receiving, by the current network convergence service hosting site from the RAN orchestrator, a relocation indication including an indication of a target network convergence service hosting site; and relocating, by the current network convergence service hosting site in response to the relocation indication, a network convergence service for one or more user devices from the current network convergence service hosting site to the target network convergence service hosting site.

[0014] The details of one or more examples of implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG. 1 is a block diagram of a wireless network according to an example implementation. [0016] FIG. 2 is a block diagram of a wireless network 200 according to another example implementation.

[0017] FIG. 3 is a flow chart illustrating operation of a radio access network (RAN) orchestrator according to an example implementation.

[0018] FIG. 4 is a flow chart illustrating operation of RAN orchestrator according to an example implementation.

[0019] FIG. 5 is a flow chart illustrating operation of a network convergence service (NCS) hosting site according to an example implementation.

[0020] FIG. 6 is a flow chart illustrating operation of a RAN orchestrator according to another example implementation.

[0021] FIG. 7 is a diagram illustrating an example operation of network 200 where the radio access network (RAN) orchestrator collects information.

[0022] FIG. 8 is a diagram illustrating an example operation of network 200 where radio access network (RAN) orchestrator selects one of a plurality of network convergence service (NCS) hosting sites to host a NCS for a UE or service flow according to an example implementation.

[0023] FIG. 9 is a diagram illustrating an example operation of network 200 where radio access network (RAN) orchestrator selects one of a plurality of network convergence service (NCS) hosting sites for relocation of a NCS for a UE or service flow.

[0024] FIG. 10 is a diagram illustrating an example operation of network 200 where a network convergence service (NCS) is relocated.

[0025] FIG. 11 is a diagram illustrating a network according to another example implementation.

[0026] FIG.12 is a block diagram of a wireless station or network device (e.g., base station/access point or mobile station/user device/user equipment) according to an example implementation. DETAILED DESCRIPTION

[0027] FIG. 1 is a block diagram of a wireless network 130 according to an example implementation. In the wireless network 130 of FIG. 1, user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs), may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an Access Point (AP) or an enhanced Node B (eNB). At least part of the functionalities of a base station (BS), access point (AP) or (e)Node B (eNB) may be also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head. BS 134 provides wireless coverage within a cell 136, including to user devices 131, 132, 133 and 135. Although only four user devices are shown as being connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to a core network 150 via a SI interface 151. This is merely one simple example of a wireless network, and others may be used.

[0028] A user device (or user terminal, or user equipment (UE)) may refer to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples. It should be appreciated that a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. A user device may also be referred to herein as a user equipment (UE).

[0029] In LTE (as an example), core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility/handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.

[0030] The various example implementations may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE-A, 5G, cm Wave, and/or mm Wave band networks, or any other wireless network. LTE, 5G, cmWave and mm Wave band networks are provided only as illustrative examples, and the various example implementations may be applied to any wireless technology/wireless network.

[0031] FIG. 2 is a block diagram of a wireless network 200 according to another example implementation. Wireless network 200 may include a user device or UE 210 that is connected to multiple base stations (BSs) or access points (APs) or similar radio connection points. In the example shown in FIG. 2, UE 210 is connected to multiple BSs, including BS 220A and BS 220B. Thus, UE 210 includes multiple wireless connections, e.g., a wireless or radio connection to each of multiple BSs, which may be referred to as multi-connectivity. The radio connections may all use the same radio access technology, or may use different radio access technologies.

[0032] With respect to UE 210, BS 220A may also be referred to as radio leg 1, while BS 220B may be referred to as radio leg 2, because UE 210 (configured for multi- connectivity or multiple BS connections) may send and receive data via these two radio legs or BSs, as part of multi-connectivity. Thus, for UE 210, BSs 220A and 220B provide two radio legs for the communications of data and/or control signals to and from UE 210. The UE 210 may send and/or receive data for multiple service flows, including, for example, for service flow 1 and service flow 2. Each service flow may, for example, be associated with an application running on the UE 210. And, each service flow may include its own quality of service (QoS) requirements, such as, for example, a requested data rate, a maximum number of hops, a maximum latency, an average data rate, a maximum or peak data rate, a maximum or average allowed delay, and a maximum error rate (e.g., maximum packet error rate or packet drop rate), as some example QoS parameters for the service flow or for UE 210. The QoS requirements may include other parameters. [0033] According to an example implementation, BS 220A may include a protocol stack, which may include a number of protocol entities, with each entity performing one or more functions or operations. An example protocol stack for BS 220A may include, for example, a radio convergence service (RCS) 224A for service flow 1 (RCS1) 224A, a RCS for service flow 2 (RCS2), a Media Access Control (MAC) entity 226A (which may be shared among both service flows), and a Physical layer (PHY) entity 228A. BS 220B may include a similar set of protocol entities/services. BS 220A may also include a lower network convergence service (NCS-L) 222A which may be a thin or limited functionality service or entity that communicates (may send and received packets or messages) with the network convergence service(s) (NCSs) that are located at a NCS hosting site, described in greater detail below. Unless otherwise noted, the term network convergence service or NCS only refers to the NCS located or instantiated at a NCS hosting site, and generally does not refer to the NCS-L at a BS. The term NCS-L refers only to the lower NCS (NCS-L) provided at a BS for communication with the NCS provided at NCS hosting sites. Although not shown, other protocol entities/services may also be included for BSs 220A and 220B. A BS or AP may include all of its protocol entities or services in the same location, or may have a functionality split in which different subsets of its protocol entities or services are in different locations. For example, some of the protocol entities or services may be located at the same site as the antennas, while others may be located in a more central or cloud location.

[0034] According to an example implementation, RCS 224A may perform segmentation/concatenation or reassembly, error detection and correction, data retransmission (for example using an Automatic Repeat Request (ARQ) protocol), duplicate detection and in-sequence data delivery to higher layers. RCS may be known by alternative names such as RLC (Radio Link Control). A RCS may be provided for each service flow, for example. MAC entity 226A may perform multiplexing of logical channels, hybrid ARQ (HARQ) retransmissions (where ARQ may refer to automatic repeat request), and other MAC-related functions. The PHY entity 224A may perform coding/decoding, modulation/demodulation, multi-antenna mapping, and other physical layer functions. Other protocol entities or services, not shown, may also be provided at each BS or radio leg.

[0035] Referring to FIG. 2, network 200 may also include gateways, such as a control gateway C-MGW 232 and a user-plane gateway U-GW 234, a transport network 230, and one or more network convergence services (NCSs). Network Convergence Service may be known by alternative names, such as PDCP (Packet Data Convergence Protocol) or other names. The transport network 230 may include a plurality of network devices, e.g., switches, IP (Internet Protocol) Routers, or other network devices that are connected via a plurality of data links, to allow data and control messages to be sent or routed for one or more service flows, e.g., between user gateway U-GW 234 and the one or more base stations (BSs), such as BSs 220A and 220B.

[0036] According to an example implementation, a network convergence service (NCS) may be provided per (or for each) user device or per service flow. Each NCS may be located or instantiated at one of a plurality of NCS hosting sites, such as one of NCS hosting sites 236, 238, 240, 242, 244, etc. For example, NCS hosting sites may be provided at a variety of locations or implementations to host the NCS, such as on a BS/AP (e.g., NCS hosting site 244 provided on BS 220A), on a network device within transport network 230 (e.g., NCS hosting site 242), provided as a virtual NCS within a cloud-based service, or at another location or on another device within network 200. Thus, each NCS may be created or instantiated physically on a BS/AP or network device, on a network device, or may be provided or instantiated as a virtualized/cloud-based implementation within a cloud-based service, for example.

[0037] According to an example implementation, a network convergence service (NCS) may be provided for each user device and/or for each service flow. A NCS may, for example, provide network convergence services for a service flow or a user device, such as coordinating a flow of data to and/or from one or more of the user devices via multiple base stations/radio legs. The coordinating of a flow of data may involve various operations, such as ciphering, or header compression, or distributing the packets of a flow to be transmitted over multiple available radio legs, or prioritizing different types of packets, or selecting an amount of traffic to send over each of multiple available radio legs, or providing in-sequence delivery, or the like. For example, as shown in FIG. 2, two gateways are shown, which may receive incoming traffic/data from another network, such as the Internet. As noted, data may be sent and received for one or more user devices, and/or for one or more service flows, where a service flow may include a flow of packets or data from a common source or category of applications and may have QoS requirements.

[0038] According to an illustrative example, a network convergence service, NCS1, may initially be created or instantiated on source (or current) NCS1 hosting site 236. For example, NCS1 may provide network convergence services for service flow 1, and/or for UE 210. Thus, among other operations or functions, NCS1 may coordinate a flow of data to and from UE 210 via multiple base stations/radio legs (e.g., via BS 220A and BS 220B) that are connected to the UE 210. For example, NCS1 may receive data for service flow 1 via U-GW 234, and then may forward (shown as line 237A) a portion (e.g., packets with even sequence numbers) of the data via a transport network 230 to BS 220A for forwarding via wireless connection to UE 210, and may forward (shown as line 237B) a remaining portion (e.g., packets with odd sequence numbers) via transport network 230 to BS 220B for forwarding via wireless connection to UE 210. While only two BSs/radio legs are shown as being connected to UE 210, any number of BSs may be connected to UE 210 to provide multi-connectivity.

[0039] In this simple example, while NCS 1 may select even packets to be sent to UE 210 via BS 220A and odd packets to be sent to UE 210 via BS 220B, this is merely an illustrative example, and NCS1 may allocate data or traffic for the service flow 1 among the multiple BSs in any manner, e.g., taking into consideration a number of conditions or parameters, such as, e.g., any QoS requirements for the service flow, an available capacity or load at each BS or radio leg, latency within transport network 230 between NCS1 and each BS (which would typically involve different paths, and thus, may include different latencies across transport network 230), and other conditions or parameters. NCS1 may similarly instruct UE 210 to transmit data over one or more BSs for each service flow, e.g., NCS1 may control or allocate uplink data for service flow 1 in a similar manner.

[0040] In addition, a second service flow, service flow 2, is shown in FIG. 2, where a different NCS (NCS2), which may be installed at a different NCS hosting site (NCS hosting site 240). NCS2 may perform network convergence services for service flow 2, for example.

[0041] A radio access network (RAN) control plane 250 may include a RAN orchestrator 252, a radio resource control (RRC) entity 254. A software defined network (SDN) controller 256 may be included in the RAN control plane 250 or may be a separate entity. Each of these entities may be provided at a same location/device, or on different locations/devices, either on physical devices (e.g., on a network device, AP/BS or other device) or as a virtualized entity on a cloud-based service, or other location.

[0042] As noted, a network convergence service (NCS) for a user device or service flow may be located or instantiated at one of a plurality of different network convergence service (NCS) hosting sites. When a service flow is started for a UE, a suitable NCS hosting site must be selected to host the NCS for the service flow/UE. Also, during the lifetime of a service flow, a relocation of a NCS from a source (or current) NCS hosting site to a target NCS hosting site may become necessary or advantageous.

[0043] According to an example implementation, RAN orchestrator 252 selects an initial NCS hosting site to host an NCS for a service flow or UE. In addition, RAN orchestrator 252 may select a target (or new) NCS hosting site to relocate a NCS for the service flow or UE, e.g., when one or more circumstances or parameters change, or when such a relocation may become necessary or at least desirable. According to an example implementation, RAN orchestrator 252 may select one of a plurality of NCS hosting sites to host a NCS for a service flow or UE (either an initial NCS hosting site or for NCS relocation) based on one or more of the following, for example: the quality of service requirements for the service flow or UE, the performance state information for one or more NCS hosting sites, the network state information (e.g., for transport network 230) and the multi-connectivity status information for the service flow or UE.

[0044] R C entity 254 may communicate with each BS to assist in setting up each radio leg or each connection between UE 210 and a plurality of BSs, e.g., to assist in setting up the wireless connections between UE 210 and each of BS 220 A and 220B. Thus, the RRC entity 254 may determine the multi-connectivity status information for each UE, including an indication of the BSs/radio legs that are connected to each UE.

[0045] In addition, the RRC entity 254 may learn or obtain the QoS requirements for each service flow or user device, e.g., when the service flow is started or created, and may also receive a QoS requirements update when the QoS requirements for the service flow change. According to an illustrative example implementation, the QoS

requirements for a service flow or for a UE may include one or more of the following: a requested data rate; a maximum number of hops; a maximum latency; an average data rate; a maximum or peak data rate; and a maximum error rate (e.g., a maximum packet error rate). These are merely some example QoS parameters, and other parameters may be used for the QoS requirements for a service flow or UE. RAN orchestrator may receive from RRC 254 the QoS requirements for each service flow or UE. Thus, the RAN orchestrator 252 may select a suitable NCS hosting site for the service flow or UE based on, for example, the QoS requirements of the service flow or UE, e.g., in order to select a NCS hosting site that can meet the QoS requirements for the service flow or UE.

[0046] RAN orchestrator 252 may receive, e.g., from RRC 254, the multi- connectivity status information for each user device indicating the one or more (or plurality) of base stations or radio legs connected to each user device. Thus, the RAN orchestrator 252 may select a suitable NCS hosting site for the service flow or UE based on the multi-connectivity status for the UE. For example, if a UE is connected to three BSs/radio legs, then RAN orchestrator 252 may (or should) select a NCS hosting site for the UE that can support three radio legs/BSs, or should select a NCS hosting site that is at a physical location where the NCS hosting site can access or communicate with all three BSs/radio legs of the UE without incurring a latency that exceeds the QoS requirements of the service flow or UE. These are merely some illustrative examples of how the multi-connectivity status and/or QoS requirements for a UE may be considered by the RAN orchestrator 252 in selecting a NCS hosting site for a service flow or UE.

[0047] SDN controller 256 may communicate with one or more (or all or each) of the network devices (e.g., switches or routers) of transport network 230. Therefore, based on this communication with network devices within transport network 230, SDN controller 256 may obtain network state information for the transport network 230.

According to an illustrative example implementation, the network state information that may be obtained by SDN controller 256 for transport network 230 may include one or more of the following: a network topology information for transport network 230, such as, for example, network topology information including information indicating the one or more network devices and data links interconnecting the network devices; one or more performance attributes of one or more of the data links within transport network 230; a data rate of one or more of the data links; a latency of one or more of the data links within transport network 230; an available capacity of one or more network devices and/or data links within the transport network 230; and/or an amount of load (or amount of resources used/occupied) on one or more of the network devices or on one or more of the data links within transport network 230. These are merely some examples, and the network state information may include other network data, statistics or parameters.

[0048] According to an example implementation, RAN orchestrator 252 may receive the network state information from SDN controller 256, e.g., via an application programming interface (API). Thus, RAN orchestrator 252 may select a NCS hosting site for a UE or service flow based on, for example, the network state information for one or more network devices for transport network 230. As an illustrative example, RAN orchestrator 252 may consider the network topology, number of hops for a path between each NCS hosting site and a BS/radio leg for a UE, may determine a total estimated latency for each path between each NCS hosting site and each radio leg/BS of the UE, and then may select a NCS hosting site that provides, for example, a number of hops and/or maximum latency that meets the QoS requirements for the service flow or UE. This is merely an illustrative example of how a selection by RAN orchestrator 252 of a NCS hosting site may be based on or may consider the network state information of transport network 230.

[0049] RAN orchestrator 252 may also communicate with each of the plurality of NCS hosting sites to obtain performance state information for each NCS hosting site. The performance state information may include, for example, information describing one or more processing resources of each network convergence service (NCS) hosting site; a processing power or capabilities of the NCS hosting site; a link capacity for one or more data links of the NCS hosting site; and/or an indication of an amount of load or usage of the processing power or link capacity, or an indication of an available amount of the processing power or link capacity, of the NCS hosting site. These are merely some illustrative examples of performance state information that RAN orchestrator 252 may request and receive from one or more (or each) NCS hosting site. Thus, for example, some NCS hosting sites may have significant processing power and available resources (e.g., possibly for some cloud-based hosting sites), while other NCS hosting sites may have less processing power or less resources to allocate to an instantiated NCS that may be hosted on such NCS hosting site. Thus, the performance state information for one or more NCS hosting sites may be used by RAN orchestrator 252 to select one of a plurality of NCS hosting sites to host a NCS, e.g., to ensure that a selected NCS hosting site has sufficient processing power and/or other resources to support a NCS that may be run or hosted on such NCS hosting site.

[0050] Therefore, according to an example implementation, when a service flow is started, a suitable NCS hosting site will be selected by the RAN orchestrator 252. During the lifetime of a service flow, a relocation of a NCS may be triggered for various reasons, such as for example, a change in the performance state information of the current NCS hosting site (such as a processing overload at the current/source NCS hosting site such that the NCS hosting site may be unable to continue hosting the NCS (or where another NCS is a much better hosting site for a NCS)), a change in multi-connectivity status of the UE (e.g., add a new BS/radio leg, or drop an existing radio leg/BS), a change in the QoS requirements for the service flow or UE, a change in the network state information for a path(s) between the current NCS hosting site and one or more radio legs/BSs for the UE (e.g., which may result in increased latency and/or decreased data rate or throughput for such paths, for example), or other reason.

[0051] Selection of a suitable NCS-H hosting site (at the time of service flow setup, or at the time of NCS relocation) may use one or more factors, e.g., (i) anticipated processing load brought in by the new flow, and whether that can be met by one or more potential NCS hosting sites (which may include consideration of performance state information for one or more possible NCS hosting sites), (ii) QoS requirements of the service flow, and whether those can be fulfilled by particular NCS hosting sites, (iii) UE's multi-connectivity legs and radio status, and whether a particular NCS location is a good choice considering the multi-connectivity status of the UE, (iv) network state information of the transport network 230, and/or other factors.

[0052] According to example implementation, RAN orchestrator 252 may, for example perform one or more of the following: (i) receive registration notifications from one or more network elements when the network element hosts an NCS; (ii) receive a multi-connectivity status for one or more UEs; (iii) receive a QoS requirements for one or more service flows or UEs; (iv) use the API for SDN controller 256 to obtain network state information (e.g., network topology, paths, device/link bandwidths and latencies, amount of load on each link or network device, ...) for transport network 230 that may be coupled between one or more NCS hosting sites and the plurality of BSs/radio legs for one or more UEs; (v) receive performance state information for one or more NCS hosting sites (e.g., NCS hosting site processing power or hosting site resources, available capacity or load indications for one or more resources); (vi) receive a request from a network element regarding the need for selecting an initial NCS hosting site for a UE or service flow; (vii) receiving a relocation request or other notification indicating that the current NCS hosting site for a service flow/UE is unable to continue hosting the NCS for the UE or service flow (e.g., due to inadequate resources or an overload condition at the NCS hosting site, unable to meet QoS requirements for the service flow/UE, due to a change in multi-connectivity status, or other reason); (viii) in response to the request for selection of an initial NCS hosting site, selecting an initial NCS hosting site for the NCS and then sending a message to the selected NCS hosting site indicating that the selected NCS hosting site has been selected to host the NCS for the service flow or UE; and (ix) in response to the relocation request or other notification, selecting a target NCS hosting site for NCS relocation for the UE or service flow, and then providing a notification of such selected target NCS hosting site to a requesting network device or the current/source NCS hosting site and/or the target NCS hosting site, to initiate NCS relocation.

According to an example implementation, logically, RAN Orchestrator 252 can be considered as part of the RAN control plane 250.

[0053] A number of different scenarios may cause the RAN orchestrator 252 to relocate a NCS to a new/target NCS hosting site.

[0054] In a first illustrative scenario, the current/source NCS hosting site may become overloaded (e.g., in either CPU/processing and/or link bandwidth terms) and the RAN orchestrator 252 decides to offload/relocate one or more UEs (or offload/relocate NCSs for one or more UEs) to a different target NCS hosting site. Example : Source NCS hosting site = a macro base station, and Target NCS hosting site = some cloud- based scalable hosting site. Scenario: Many UEs of the macro BS enters multi- connectivity while macro is hosting NCS for all these UEs. Then the throughput/traffic demand of the UEs increases, and the processing capability of macro BS (source NCS hosting site) is unable to sustain NCS processing for all of UEs. In this case, the RAN orchestrator may offload or relocate one or more NCSs from the source NCS hosting to a target NCS hosting site.

[0055] In a second example scenario, based on a UE's traffic, it is determined that the current NCS hosting site is not suitable to provide the right handling for the traffic, or is unable to meet the QoS requirements for the UE. For example, some new traffic is starting for a UE, and a different NCS hosting site may provide better path characteristics (e.g. lower path latency) to meet the new traffic's QOS. Or when new multi-connectivity legs are added/dropped, a different path may be more optimal considering radio legs/BSs and the network topology. Or a UE may require some special treatment (e.g., Deep Packet Inspection (DPI)) or handling that is not available at the current NCS hosting site whereas a new target NCS hosting site is able to provide that capability, for example. Or, for example, a UE's traffic is determined to be "low-revenue" by an operator, and NCS processing is then moved to a "cheaper" processing platform (e.g. lower-tier cloud). Or a UE enters some multi-connectivity scenario (e.g. 4 radio legs/BSs) but the current NCS hosting site can only support 2 radio legs per UE, etc. Thus, in these situations, the RAN orchestrator may relocate a NCS from a current/source NCS hosting site to a target NCS hosting site.

[0056] In a third example scenario, a UE may perform a handover to a different "macro" BS/cell, then the NCS for the UE may be relocated to a new NCS hosting site that can serve the new macro BS, which may be similar to the case above where multi- connectivity radio legs for the UE are added/deleted, and the NCS is relocated based on this change in multi-connectivity.

[0057] FIG. 3 is a flow chart illustrating operation of a radio access network (RAN) orchestrator according to an example implementation. Operation 310 includes receiving, by a radio access network (RAN) orchestrator, a request for selecting a network convergence service (NCS) site to host a network convergence service for a service flow or user device in a wireless network, the wireless network including the user device connected to a plurality of base stations, the network convergence service for the service flow or user device responsible for at least coordinating a flow of data to or from the user device via the multiple base stations. Operation 320 includes selecting one of a plurality of network convergence service hosting sites to host the network convergence service for the service flow or user device. And, operation 330 includes sending a message to the selected network convergence service hosting site indicating that the selected network convergence service hosting site has been selected to host the network convergence service for the service flow or user device.

[0058] According to an example implementation of the method of FIG. 3, the method may further include receiving a quality of service requirements for the service flow or user device; receiving a performance state information for one or more network convergence service hosting sites; receiving a network state information for a transport network coupled to the one or more network convergence service hosting sites and the plurality of base stations; receiving a multi-connectivity status information for the user device indicating the plurality of base stations that are connected to the user device; wherein the selecting may include selecting one of the plurality of network convergence service (NCS) hosting sites to host the network convergence service for the service flow or user device based on at least one of the quality of service requirements, the

performance state information, the network state information and the multi-connectivity status information.

[0059] According to an example implementation of the method of FIG. 3, the method may further include instantiating or creating, on the selected network

convergence service hosting site, an instance of the network convergence service for the user device or service flow.

[0060] According to an example implementation of the method of FIG. 3, the receiving the request may include: receiving a request to select an initial network convergence service hosting site to host the network convergence service for the service flow or the user device, the request including a quality of service requirements for the service flow or user device and a multi-connectivity status information for the user device indicating the plurality of base stations that are connected to the user device.

[0061] According to an example implementation of the method of FIG. 3, the quality of service requirements for the service flow or user device may include one or more of the following for the service flow or user device: a requested data rate; a maximum number of hops; a maximum latency; an average data rate; a maximum or peak data rate; and a maximum packet error rate.

[0062] According to an example implementation of the method of FIG. 3, the performance state information for one or more network convergence service hosting sites may include one or more of the following for one or more network convergence service hosting sites: information describing one or more processing resources of the network convergence service hosting site; a processing power or capabilities of the network convergence service hosting site; a link capacity for one or more data links of the network convergence service hosting site; and an indication of an amount of load or usage of the processing power or link capacity, or an indication of an available amount of the processing power or link capacity, of the network convergence service hosting site.

[0063] According to an example implementation of the method of FIG. 3, the transport network includes one or more network devices, and wherein the network state information for the transport network includes one or more of the following: a network topology information including information indicating the one or more network devices and data links interconnecting the network devices; one or more performance attributes of one or more of the data links; a data rate of one or more of the data links; a latency of one or more of the data links; and an amount of load on one or more of the network devices or on one or more of the data links.

[0064] According to another example implementation, an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: receive, by a radio access network (RAN) orchestrator, a request for selecting a network convergence service site to host a network convergence service for a service flow or user device in a wireless network, the wireless network including the user device connected to a plurality of base stations, the network convergence service for the service flow or user device responsible for at least coordinating a flow of data to or from the user device via the multiple base stations; select one of a plurality of network convergence service hosting sites to host the network convergence service for the service flow or user device; and send a message to the selected network convergence service hosting site indicating that the selected network convergence service hosting site has been selected to host the network convergence service for the service flow or user device.

[0065] According to another example implementation, a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: receiving, by a radio access network (RAN) orchestrator, a request for selecting a network convergence service site to host a network convergence service for a service flow or user device in a wireless network, the wireless network including the user device connected to a plurality of base stations, the network convergence service for the service flow or user device responsible for at least coordinating a flow of data to or from the user device via the multiple base stations; selecting one of a plurality of network convergence service hosting sites to host the network convergence service for the service flow or user device; and sending a message to the selected network convergence service hosting site indicating that the selected network convergence service hosting site has been selected to host the network convergence service for the service flow or user device.

[0066] FIG. 4 is a flow chart illustrating operation of RAN orchestrator according to an example implementation. Operation 410 includes receiving, by a radio access network (RAN) orchestrator from a current network convergence service hosting site hosting a network convergence service for one or more user devices in a wireless network, a notification indicating that the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices, the wireless network including the one or more user devices, each user device connected to a plurality of base stations, the network convergence service for one or more user devices responsible for at least coordinating a flow of data to or from one or more of the user devices via the multiple base stations. Operation 420 includes selecting, by the RAN orchestrator, a target network convergence service hosting site for relocating a network convergence service for one or more user devices; and Operation 430 includes sending, by the RAN orchestrator to the current network convergence service hosting site, a relocation indication requesting a relocation of one or more network convergence services from the current network convergence service hosting site to the target network convergence service hosting site.

[0067] According to an example implementation of the method of FIG. 4, the notification indicates that the current network convergence service hosting site is overloaded or is unable to meet quality of service requirements for one or more service flows or user devices.

[0068] According to an example implementation of the method of FIG. 4, the notification received by the RAN orchestrator is associated with a handover or a multi- connectivity status change for at least one of the user devices.

[0069] According to an example implementation of the method of FIG. 4, the selecting is performed based on one or more of the following: the quality of service requirements for the service flow or the user device; a performance state information for one or more network convergence service hosting sites; a network state information for a transport network coupled to the one or more network convergence service hosting sites and the plurality of base stations; and a multi-connectivity status information for one or more user devices indicating the plurality of base stations that are connected to each of the user devices.

[0070] According to an example implementation of the method of FIG. 4, the method may further include: the RAN orchestrator selecting one or more network convergence services to be relocated from the current network convergence service hosting site to the target network convergence service hosting site; and wherein the relocation indication, sent by the RAN orchestrator, indicates the selected network convergence services to be relocated from the current network convergence service hosting site to the target network convergence service hosting site.

[0071] FIG. 5 is a flow chart illustrating operation of a network convergence service (NCS) hosting site according to an example implementation. Operation 510 includes detecting, by a current network convergence service hosting site hosting a network convergence service for one or more user devices in a wireless network, a condition wherein the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices, each user device connected to a plurality of base stations, the current network convergence service for one or more user devices responsible for at least coordinating a flow of data to or from one or more of the user devices via multiple base stations.

Operation 520 includes sending, by the current network convergence entity host site to a radio access network (RAN) orchestrator, a notification indicating that the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices. Operation 530 includes receiving, by the current network convergence service hosting site from the RAN orchestrator, a relocation indication including an indication of a target network convergence service hosting site. And operation 540 includes relocating, by the current network convergence service hosting site in response to the relocation indication, a network convergence service for one or more user devices from the current network convergence service hosting site to the target network convergence service hosting site.

[0072] According to an example implementation of the method of FIG. 5, the notification indicates that the current network convergence service hosting site is overloaded or is unable to meet quality of service requirements for one or more service flows or user devices.

[0073] According to an example implementation of the method of FIG. 5, the relocation indication from the RAN orchestrator identifies one or more network convergence services to be relocated to the target network convergence service hosting site.

[0074] According to an example implementation of the method of FIG. 5, the method may further include: selecting, by the current network convergence service hosting site, one or more network convergence services to be relocated from the current network convergence service hosting site to the target network convergence service hosting site.

[0075] FIG. 6 is a flow chart illustrating operation of a RAN orchestrator according to another example implementation. Operation 610 includes RAN orchestrator 252 receiving a request for a NCS hosting site selection, e.g., for service flow setup, for a UE, or for a NCS relocation. Operation 620 includes RAN orchestrator 252 preparing a list of candidate NCS hosting sites based on, e.g., UE multi-connectivity status (the radio legs/BS connections for the UE), and possibly other information, and then retrieving performing state information for each of a plurality of NCS hosting sites (e.g., from the candidate NCS hosting sites). Operation 630 includes RAN orchestrator 252 retrieving network state information for transport network 230. Operation 640 includes RAN orchestrator 252 preparing or ranking an ordered list of the candidate NCS hosting sites based on, e.g., ability of the hosting site to support the UE/SF QoS requirements/needs, considering path bandwidth and latency, and other information. Operation 650 includes RAN orchestrator 252 searching the rank-ordered list and selecting a NCS hosting site that has sufficient available capacity/resources to meet the anticipated processing load of the service flow/UE and/or meet the QoS requirements of the service flow/UE.

Operation 660 includes RAN orchestrator 252 providing information regarding or indicating the selected NCS hosting site to one or more other entities. For example, RAN orchestrator may notify the requesting entity, e.g., R C entity 254, or the current NCS hosting site, and/or a target NCS hosting site, of the NCS hosting that has been selected to host the NCS for the UE/service flow. [0076] FIG. 7 is a diagram illustrating an example operation of network 200 where the radio access network (RAN) orchestrator collects information. At 718A and 718B, NCS hosting site 1 and NCS hosting site 2, respectively, are created or

instantiated. According to one illustrative example, NCS hosting sites 1 and 2 may be provided as a physical installation on, e.g., dedicated hardware. Alternatively, these NCS hosting sites may each be instantiated as a virtualized network function (VNF) by a network functions virtualization (NFV) orchestrator. NFV instantiates and manages network functions as virtualized instances in a cloud infrastructure (as opposed to a physical installation on dedicated hardware). A VNF is a network function that is instantiated in a virtual machine or Linux container or the like in a cloud infrastructure (as opposed to having its own box or network device). Any of the network functions described herein, e.g., RAN orchestrator, NCS hosting site, NCS, SDN controller, RRC entity, etc., may be provided via a physical installation on a specific device, or may be provided as virtualized network functions (VNFs).

[0077] At 718A and 718B, NCS hosting sites 1 and 2, respectively, register with RAN orchestrator 252, e.g., indicating that these hosting sites can host NCS, and each providing performance state information for the respective NCS hosting site.

[0078] At 720A and 720B, NCS hosting sites 1 and 2, respectively, may periodically provide a report with an updated performance state information, e.g., that may identify an updated values for processing power/capabilities for the NCS hosting site, updated information describing one or more resources for the NCS hosting site, updated link capacity (or updated available/unused link capacity), an updated amount of load or amount of available capacity of the hosting site's processing power, data link capacity or other network resource of the NCS hosting site. At 722, NCS hosting site 1 may periodically, or in response to an event, may provided update UE/service flow status for one or more or all of the service flows for which NCS hosting site 1 is hosting a NCS, e.g., which may indicate, for example, that all flows are being handled adequately and meeting QoS requirements, or information may be provided indicating that QoS requirements are not being met for one or more service flows, other information.

[0079] At 724, RAN orchestrator 252 obtains multi-connectivity status information and service flow QoS needs/requirements for one or more UEs from R C entity 254. At 726, RAN orchestrator may 252 (e.g., periodically) determines or obtains network state information for transport network 230, e.g., including network state information related to one or more possible communication/routing paths between various NCS hosting sites and various radio legs/BSs for the UEs for which the RAN orchestrator 252 obtained multi-connectivity status and service flow requirements at 724. This information may be used by RAN orchestrator 252 to select an initial or relocation NCS hosting site for one or more UEs or service flows.

[0080] FIG. 8 is a diagram illustrating an example operation of network 200 where radio access network (RAN) orchestrator selects one of a plurality of network convergence service (NCS) hosting sites to host a NCS for a UE or service flow. At 812, RRC entity 254 may establish, or assist in establishing or creating a service flow (end-to- end, between the core network 810 and the UE) a service flow, e.g., based on a request from the UE, as an example. Core network 810 may include gateways 232, 234 and/or other core network equipment.

[0081 ] At 814, RAN orchestrator 252 receives, from RRC entity 254, a request for an initial NCS hosting site selection/assignment for a UE or for a service flow. In an example implementation, request 814 may also include or provide the UE multi- connectivity status and the QoS requirements for the service flow. At 816, RAN orchestrator 252 selects one of a plurality of NCS hosting sites to host the NCS for the service flow or UE, e.g., based on one or more of the QoS requirements for the service flow or UE, the performance state information for the transport network 230, the network state information for one or more possible NCS hosting sites, and the multi-connectivity status information for the UE. E.g., in this example, RAN orchestrator may select NCS hosting site 1 to host the NCS for the UE or service flow.

[0082] At 820, RAN orchestrator 252 or RRC 254 sends a message to the selected NCS hosting site (e.g., to NCS hosting site 1) indicating that NCS hosting site 1 has been selected to host the NCS for the UE or service flow. At 822, the service flow between the UE and the core network 810 continues, using the selected NCS hosting site. This may include, for example, establishing a tunnel and flow control to be established between the UE and each leg/BS for the service flow.

[0083] FIG. 9 is a diagram illustrating an example operation of network 200 where radio access network (RAN) orchestrator selects one of a plurality of network convergence service (NCS) hosting sites for relocation of a NCS for a UE or service flow. Two different example implementations are shown in FIG. 9. In a first example implementation, operations 910 - 918 in FIG. 9 describe an overload-driven relocation, including the selection of a NCS hosting site for NCS relocation in response to a general overload condition. While, according to a second example implementation, operations 930-938 of FIG. 9 describe a QoS-driven relocation, including the selection of a NCS hosting site for NCS relocation in response to a current hosting site being unable to meet or satisfy a QoS requirements for a specific UE(s) or service flow(s).

[0084] In the first example implementation, at 910, a current NCS hosting site (NCS hosting site 1) for a UE or service flow may detect an overload condition, e.g., more traffic or load, or insufficient resources at the hosting site. At 912, NCS hosting site may send to RAN orchestrator 252 a notification of the overload, and may indicate an amount of load to be shed or relocated. For example, the notification at 912 may provide a notification indicating that the current NCS hosting site is unable to continue hosting the NCS for one or more service flows or UEs.

[0085] At 914, RAN orchestrator 252 selects one of a plurality of NCS hosting sites, e.g., with sufficient resources or capacity to receive/relocate some load (e.g., to receive/host a relocated NCS for one UEs or service flows). This selection of a new or target NCS may, e.g., based on one or more of the QoS requirements for the service flow or UE, the performance state information for the transport network 230, the network state information for one or more possible NCS hosting sites, and the multi-connectivity status information for the UE. E.g., in this example, RAN orchestrator may select NCS hosting site 2 as a target NCS hosting site for relocation of an NCS for one or more UEs or service flows.

[0086] At 916, RAN orchestrator 252 sends, to current NCS hosting site (NCS hosting site 1) a relocation indication, e.g., indicating the decision to initiate NCS relocation and/or requesting relocation of one or more NCS hosting sites. The relocation indication at 916 may include, for example, information identifying a target NCS hosting site (e.g., information identifying NCS hosting site 2 as the target hosting site) and an amount of load (or amount of traffic and/or number of NCSs) that can be shed or relocated. At 918, the current/source NCS hosting site (NCS hosting site 1) may select one or more NCSs (or one or more UEs with associated NCSs) to be relocated to the target NCS hosting site. The relocation may then be performed from the source/current NCS hosting site (site 1) to the target NCS hosting site (e.g., site 2).

[0087] In the second example implementation, at 930, the current/source hosing NCS site (e.g., site 1) detects UEs for which their current QoS requirements are not acceptable or cannot be met by the current NCS hosting site. At 932, the current NCS hosting site sends a notification to RAN orchestrator 252 of UE QoS inadequacy or other notification that the current hosting site is unable to meet QoS requirements for one or more UEs or service flows. At 934, the RAN orchestrator 252 selects one NCS hosting site to be the target hosting site, e.g., having sufficient resources/capacity, with a suitable location given UE's multi-connectivity status, etc. At 936, RAN orchestrator 252 send a relocation indication (indicating the decision to relocate one or more NCSs) to the current NCS hosting site, identifying the target NCS hosting site (e.g., site 2), and the amount of load shedding/relocation allowed, or may be even identify specific UEs/NCSs that can or should be relocated to the target NCS hosting site. At 938, the source/current NCS hosting site (site 1) and the target NCS hosting site (site 2) then execute or perform the relocation of one or more NCSs.

[0088] FIG. 10 is a diagram illustrating an example operation of network 200 where a network convergence service (NCS) is relocated. At 1010, the source NCS hosting site makes a decision to relocate a NCS for one or more UEs, and determines a target NCS hosting site (see, e.g., FIG. 9). At operation 1, the source NCS hosting site sends a NCS relocation initiation request, and may provide one or more parameters or context for the UE to move the UE tunnel from the source NCS hosting site to the target NCS hosting site. These parameters or UE context may include, for example, NCC-L tunnel endpoint information for downlink, UE context including ciphering key/context, and other parameters.

[0089] At operation 2 in FIG. 10, the target NCS hosting site sends a relocation initiation response to the source NCS hosting site, e.g., providing the new NCS tunnel end-point information for uplink communication, and tunnel end-point information for downlink. At operation 3 of FIG. 10, the source NCS hosting site notifies the NCS-L for the UE (at one of the radio legs/BSs connected to the UE) of the relocation of the NCS to the target, and indicates the new NCS tunnel and end-point information to allow the NCS-L to establish a tunnel with the target NCS hosting site. At operation 4, the NCS-L for the UE performs flow control initialization with the target NCS hosting site.

[0090] At operation 5a of FIG. 10, source NCS hosting site sends to RRC entity 254 a relocation notification, indicating the U-GW information, and the target NCS hosting site. At operation 5b, RRC entity 254 sends a path switch message to C-MGW 232, providing the tunnel end-point information at the target NCS hosting site for downlink communication. At operation 5c, C-MGW 232 sends to U-GW 234 a path switch message to U-GW with tunnel end-point information at target NCS hosting site. At operation 6, U-GW 232 sends to C-MGW a path switch message including the tunnel end-point information of the U-GW 234. At operation 7, U-GW 234 sends an end marker packet to the source NCS hosting site, e.g., indicating end of the service flow through the source NCS hosting site. At operation 8, subsequent downlink data for the UE/service flow is sent from U-GW to the target NCS hosting site (for forwarding to the UE). The target NCS hosting site then encrypts the received data at 1020, and at operation 10, sends the encrypted data to the NCS-L for the UE (located at one or more BSs/radio legs connected to the UE). At 1030, the NCS-L for the UE buffers the data and delivers the data via radio/wireless link to the UE. At operation 9, source NCS hosting site sends a source NCS hosting site end marker, indicating end of the use of the source NCS hosting site for the UE/service flow.

[0091] FIG. 11 is a diagram illustrating a network according to another example implementation. RAN orchestrator 252 may be implemented as a virtualized network function (VNF), and is connected via an API with the SDN controller 256. A network functions virtualization orchestrator (NFV orchestrator) 1110 is coupled to a VNF manager, and then a Virtualized Infrastructure Manager (VIM.) Also, a virtualized implementation of a NCS hosting site 1120 is shown. An instance of NCS may be a virtualized network function, and may comprise a NCS signaling block 1130 and user data plane block 1140, each of which may be considered as a Virtual Network Function Component (VNFC). U-plane block 1140 and/or the C-plane block 1130 of NCS hosting site is connected to NCS-L 150 (which may be provided at a BS or radio leg for the UE) via transport network 230, which includes one or more network elements/devices.

[0092] FIG. 12 is a block diagram of a wireless station (e.g., base station, access point or user device, or other network device) 1200 according to an example

implementation. The wireless station 1200 may include, for example, one or two RF (radio frequency) or wireless transceivers 1202A, 1202B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit/entity (controller) 1204 to execute instructions or software and control transmission and receptions of signals, and a memory 806 to store data and/or instructions.

[0093] Processor 1204 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 1204, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 1202 (1202A or 1202B). Processor 1204 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 1202, for example). Processor 1204 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 1204 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor 1204 and transceiver 1202 together may be considered as a wireless transmitter/receiver system, for example.

[0094] In addition, referring to FIG. 12, a controller (or processor) 1208 may execute software and instructions, and may provide overall control for the station 1200, and may provide control for other systems not shown in FIG. 8, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 1200, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.

[0095] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 1204, or other controller or processor, performing one or more of the functions or tasks described above.

[0096] According to another example implementation, RF or wireless

transceiver(s) 1202A/1202B may receive signals or data and/or transmit or send signals or data. Processor 1204 (and possibly transceivers 1202A/1202B) may control the RF or wireless transceiver 1202 A or 1202B to receive, send, broadcast or transmit signals or data.

[0097] The embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other

communication systems. Another example of a suitable communications system is the 5G concept. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.

[0098] It should be appreciated that future networks will most probably utilise network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent.

[0099] Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Implementations may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software implementations that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks. In addition, implementations may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).

[00100] The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, readonly memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.

[00101 ] Furthermore, implementations of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers,...) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber- physical systems. Therefore, various implementations of techniques described herein may be provided via one or more of these technologies.

[00102] A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

[00103] Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[00104] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.

Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non- volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[00105] To provide for interaction with a user, implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.

[00106] Implementations may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components. Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.

[00107] While certain features of the described implementations have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the various embodiments.

Claims

WHAT IS CLAIMED IS:

1. A method comprising:

receiving, by a radio access network (RAN) orchestrator, a request for selecting a network convergence service site to host a network convergence service for a service flow or user device in a wireless network, the wireless network including the user device connected to a plurality of base stations, the network convergence service for the service flow or user device responsible for at least coordinating a flow of data to or from the user device via the multiple base stations;

selecting one of a plurality of network convergence service hosting sites to host the network convergence service for the service flow or user device; and

sending a message to the selected network convergence service hosting site indicating that the selected network convergence service hosting site has been selected to host the network convergence service for the service flow or user device.

2. The method of claim 1 and further comprising:

receiving a quality of service requirements for the service flow or user device; receiving a performance state information for one or more network convergence service hosting sites;

receiving a network state information for a transport network coupled to the one or more network convergence service hosting sites and the plurality of base stations; receiving a multi-connectivity status information for the user device indicating the plurality of base stations that are connected to the user device;

wherein the selecting comprises selecting one of the plurality of network convergence service hosting sites to host the network convergence service for the service flow or user device based on at least one of the quality of service requirements, the performance state information, the network state information and the multi-connectivity status information.

3. The method of claim 1 and further comprising:

instantiating or creating, on the selected network convergence service hosting site, an instance of the network convergence service for the user device or service flow.

4. The method of claim 1 wherein receiving the request comprises:

receiving a request to select an initial network convergence service hosting site to host the network convergence service for the service flow or the user device, the request including a quality of service requirements for the service flow or user device and a multi-connectivity status information for the user device indicating the plurality of base stations that are connected to the user device.

5. The method of claim 2 wherein the quality of service requirements for the service flow or user device comprises one or more of the following for the service flow or user device:

a requested data rate;

a maximum number of hops;

a maximum latency;

an average data rate;

a maximum or peak data rate; and

a maximum packet error rate.

6. The method of claim 2 wherein the performance state information for one or more network convergence service hosting sites comprises one or more of the following for one or more network convergence service hosting sites:

information describing one or more processing resources of the network convergence service hosting site; a processing power or capabilities of the network convergence service hosting site;

a link capacity for one or more data links of the network convergence service hosting site; and

an indication of an amount of load or usage of the processing power or link capacity, or an indication of an available amount of the processing power or link capacity, of the network convergence service hosting site.

7. The method of claim 2 wherein the transport network includes one or more network devices, and wherein the network state information for the transport network comprises one or more of the following:

a network topology information including information indicating the one or more network devices and data links interconnecting the network devices;

one or more performance attributes of one or more of the data links;

a data rate of one or more of the data links;

a latency of one or more of the data links; and

an amount of load on one or more of the network devices or on one or more of the data links.

8. An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to:

receive, by a radio access network (RAN) orchestrator, a request for selecting a network convergence service site to host a network convergence service for a service flow or user device in a wireless network, the wireless network including the user device connected to a plurality of base stations, the network convergence service for the service flow or user device responsible for at least coordinating a flow of data to or from the user device via the multiple base stations;

select one of a plurality of network convergence service hosting sites to host the network convergence service for the service flow or user device; and

send a message to the selected network convergence service hosting site indicating that the selected network convergence service hosting site has been selected to host the network convergence service for the service flow or user device.

9. A computer program product, the computer program product comprising a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method comprising:

10. A method comprising:

receiving, by a radio access network (RAN) orchestrator from a current network convergence service hosting site hosting a network convergence service for one or more user devices in a wireless network, a notification indicating that the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices, the wireless network including the one or more user devices, each user device connected to a plurality of base stations, the network convergence service for one or more user devices responsible for at least coordinating a flow of data to or from one or more of the user devices via the multiple base stations;

selecting, by the RAN orchestrator, a target network convergence service hosting site for relocating a network convergence service for one or more user devices; and sending, by the RAN orchestrator to the current network convergence service hosting site, a relocation indication requesting a relocation of one or more network convergence services from the current network convergence service hosting site to the target network convergence service hosting site.

11. The method of claim 10 wherein the notification indicates that the current network convergence service hosting site is overloaded or is unable to meet quality of service requirements for one or more service flows or user devices.

12. The method of claim 10 wherein the notification received by the RAN orchestrator is associated with a handover or a multi-connectivity status change for at least one of the user devices.

13. The method of claim 10 wherein the selecting is performed based on one or more of the following: the quality of service requirements for the service flow or the user device;

a performance state information for one or more network convergence service hosting sites;

a network state information for a transport network coupled to the one or more network convergence service hosting sites and the plurality of base stations; and

a multi-connectivity status information for one or more user devices indicating the plurality of base stations that are connected to each of the user devices.

14. The method of claim 10 and further comprising:

the RAN orchestrator selecting one or more network convergence services to be relocated from the current network convergence service hosting site to the target network convergence service hosting site; and

wherein the relocation indication, sent by the RAN orchestrator, indicates the selected network convergence services to be relocated from the current network convergence service hosting site to the target network convergence service hosting site.

15. A method comprising:

detecting, by a current network convergence service hosting site hosting a network convergence service for one or more user devices in a wireless network, a condition wherein the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices, each user device connected to a plurality of base stations, the current network convergence service for one or more user devices responsible for at least coordinating a flow of data to or from one or more of the user devices via multiple base stations;

sending, by the current network convergence entity host site to a radio access network (RAN) orchestrator, a notification indicating that the current network convergence service hosting site is unable to continue hosting the network convergence service for one or more service flows or user devices;

receiving, by the current network convergence service hosting site from the RAN orchestrator, a relocation indication including an indication of a target network convergence service hosting site; and

relocating, by the current network convergence service hosting site in response to the relocation indication, a network convergence service for one or more user devices from the current network convergence service hosting site to the target network convergence service hosting site.

16. The method of claim 15 wherein the notification indicates that the current network convergence service hosting site is overloaded or is unable to meet quality of service requirements for one or more service flows or user devices.

17. The method of claim 15 wherein the relocation indication from the RAN orchestrator identifies one or more network convergence services to be relocated to the target network convergence service hosting site.

18. The method of claim 15 and further comprising:

selecting, by the current network convergence service hosting site, one or more network convergence services to be relocated from the current network convergence service hosting site to the target network convergence service hosting site.