Patent Application
20210014737
Long Term Evolution (LTE) is a mobile telecommunications protocol for wireless communication involving mobile user equipment, such as mobile devices and data terminals. LTE networks include existing Fourth Generation (4G), and 4.5 Generation (4.5G) wireless networks. The goals of LTE included increasing the capacity and speed of wireless data networks and redesigning and simplifying the network architecture to include an Internet Protocol (IP)-based system with reduced latency.
Next Generation mobile networks have been proposed as the next evolution of mobile wireless networks, such as the existing 4G and 4.5G LTE mobile networks. Next Generation mobile networks, such as Fifth Generation New Radio (5G NR) mobile networks, are expected to operate in the higher frequency ranges (e.g., in the GigaHertz frequency band) with a broad bandwidth near 500-1,000 MegaHertz. The expected bandwidth of Next Generation mobile networks is intended to support higher speed downloads. The proposed 5G mobile telecommunications standard may operate in the millimeter wave bands (e.g., 14 GigaHertz (GHz) and higher), and may support more reliable, massive machine communications (e.g., machine-to-machine (M2M), Internet of Things (IoT)). Next Generation mobile networks, such as those implementing the 5G mobile telecommunications standard, are expected to enable a higher utilization capacity than current wireless systems, permitting a greater density of wireless users. Next Generation mobile networks are designed to increase data transfer rates, increase spectral efficiency, improve coverage, improve capacity, and reduce latency.
“Network Slicing” is a proposed innovation for implementation in Next Generation Mobile Networks, such as 5G mobile networks. Network slicing is a type of virtualized networking architecture that involves partitioning of a single physical network into multiple virtual networks. The partitions, or “slices,” of the virtualized network may be customized to meet the specific needs of applications, services, devices, customers, or operators. Each network slice can have its own architecture, provisioning management, and security that supports a particular application or service. Speed, capacity, and connectivity functions are allocated within each network slice to meet the requirements of the objective of the particular network slice. Network slicing may be implemented in a dynamic fashion, such that the slices of the virtualized network may change over time and may be re-customized to meet new or changing needs of applications, services, devices, customers, or operators.
The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. The following detailed description does not limit the invention.
The evolution of mobile networks, such as Next Generation radio networks, towards Open Radio Access Networks (RANs) and virtualized RANs has gained momentum. Open RANs have the ability to integrate, deploy, and operate RANs using elements (e.g., components, subsystems, and software) which are sourced from multiple different vendors, are inter-operable, and can connect over open interfaces. Virtualized RANs involve the use of Network Functions Virtualization (NFV) and Software Defined Networks (SDNs) to virtualize a portion of the RAN onto standard Information Technology (IT) and Commercial Off-the-Shelf (COTS) hardware in a central location or in the cloud. Virtualized RANs offer a number advantages, including a flexible and scalable architecture that enables dynamic load-balancing, intelligent traffic steering, and latency reduction using local caching.
Next Generation mobile networks, through the use of network slicing, for example, are being designed to offer a variety of services that each demands a different network performance for different types of transport sessions. Exemplary embodiments described herein implement an intelligent radio controller that, in conjunction with multiple network distributed User Plane (UP) functions, enables the flexible routing and transport of traffic to satisfy different QoS and network slicing requirements associated with different types of network services and different types of traffic. Using, for example, NFV, different UP functions may be installed at different distributed locations throughout the network environment, such as in an edge cloud (e.g., a Multi-Access Edge Computing (MEC) cloud), in a centralized RAN (C-RAN), and/or in the core cloud. The intelligent radio controller selects one of the distributed UP functions within the network environment to satisfy network performance requirements for a particular transport session, such as latency or bandwidth requirements. The network performance requirements may be derived from a user profile of the particular user, and/or from the needs of a particular application or a particular network service. For example, a given application may require a maximum amount of end-to-end latency or a minimum amount of bandwidth. The intelligent radio controller additionally selects a particular distributed unit (DU) from multiple different DUs based on a performance profile associated with each DU, where the DUs implement a subset of wireless station functions associated with radio frequency (RF) communication with user equipment (UEs) and where each of the DUs connects to a respective radio unit (RU). The intelligent radio controller initiates data transport for the particular session to and/or from a UE via a transport path that includes the selected UP function and the selected DU.
The CU-UP 125 includes a logical node that hosts user plane functions, such as, for example, data routing and transport functions. As described in further detail below, CU-CP 120 and CU-UP 125 of CU 105 may include distributed nodes that may be located remotely from one another. As further described below, multiple distributed CU-CP 120s and/or multiple CU-UPs 125 may be positioned at different locations within a network (not shown). A selected one of the CU-CPs 120 and a selected one of the CU-UPs 125 may be used for handling traffic from one or more UEs (not shown).
The DU 110 of base station 100 may, in some implementations, include multiple DUs 110-1 through 110-n, where n is equal to or greater than 2. Each DU 110 of the multiple DUs includes a logical node that hosts functions associated with the Radio Link Control layer, the Medium Access Control (MAC) layer, and the physical layer (PHY). The RU 115 may include multiple RUs 115-1 through 115-n. Each RU 115 may include at least one radio transceiver, and associated antenna(s), for RF wireless communication with one or more user equipment (UEs) (not shown). Each DU 110 connects to a RU 115. For example, each DU of the multiple DUs 110-1 through 110-n connects to a respective one of RUs 115-1 through 115-n (e.g., DU 110-1 connects to RU 115-1, DU 110-2 connects to RU 115-2, etc.).
CU 105 controls the transport of data (e.g., data packets) received at a RU 115 via wireless RF transmissions from a UE (not shown), and controls the transport of data from the wireless network to a DU 110 and RU 115 for wireless transmission to a destination UE (not shown). UEs, as referred to herein, may include any type of electronic device having a wireless capability (e.g., a Radio Frequency (RF) transceiver) to communicate with the wireless network via a base station 100. Each of the UEs may include, for example, a computer (e.g., desktop, laptop, tablet, or wearable computer), a personal digital assistant (PDA), a “smart” phone, or a “Machine-to-Machine” (M2M) or “Internet of Things” (IoT) device. A “user” (not shown) may own, operate, and/or administer each UE.
Core cloud 210 includes the core components of a wireless network that serves to provide wireless access to subscribing UEs (not shown). The wireless network may include any type of wireless network that provides wireless access and connectivity to UEs. The wireless network may include, for example, a Public Land Mobile Network (PLMN) or a satellite network. In the case of a 5G wireless network, the core components may include, among other components, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), and core-implemented user plane (UP) functions. In the case of a 4G wireless network, or other types of wireless networks, core cloud 210 may include different core components that possibly perform different functions than the components of a 5G wireless network.
Edge cloud 220 includes one or more edge computing data centers, or other edge devices, that enable the movement of traffic and network services from core cloud 210 towards the edge of network environment 200 and closer to the destination devices (e.g., UEs). Instead of sending data to core cloud 210 for processing, routing, and transport, edge cloud 220 includes components that handle the data closer to the destination devices, thereby reducing latency. Edge Cloud 220 may include, for example, a Multi-Access Edge Computing (MEC) network. Though not shown in
C-RAN hub 230 may include a centralized office “hotel” at which multiple CU-CPs 120 are located to enable efficient and cost-effective network access. C-RAN hub 230 may connect to edge cloud 220, as shown in
PDN 240 may include any type of packet-switching network(s) that can connect to core cloud 210 for transporting data to and from nodes that are external to core cloud 210. PDN 240 may include, for example, the Internet, a local area network(s) (LAN), a wide area network(s) (WAN), or a metropolitan area network (MAN). In one example, one or more servers may be connected to PDN 240 and may engage in data transport with a UE (not shown) via PDN 240 and core cloud 210.
As shown in
As shown in
As shown in
The sub-functions of SON 330 may include, for example, a self-configuration sub-function, a self-optimization sub-function, a self-healing sub-function, and/or a self-protection sub-function, for automatically organizing and operating the components of the wireless network. The self-configuration sub-function may automatically configure and integrate new base stations 100 into the wireless network. The self-configuration sub-function may automatically adjust technical parameters, such as emission power, antenna orientation, etc., of base stations 100 based on changes in the network configuration (e.g., addition of a new base station 100, addition of a new DU 110, and failure of a DU 110 or RU 115) so as to provide a certain coverage and capacity. The self-optimization sub-function may automatically adjust base station 100 parameters to optimize performance of the wireless network. The self-healing sub-function may automatically identify failing network nodes and adjust the operation of adjacent nodes so that the adjacent nodes can support the users that were supported by the failing node. The self-protection sub-function may automatically defend the nodes of the wireless network from penetration by any unauthorized user.
As shown in
Device 700 may include a bus 710, a processing unit 715, a main memory 720, a read only memory (ROM) 730, a storage device 740, an input device 750, an output device 760, and a communication interface 770. Bus 710 may include a path that permits communication among the elements of device 700.
Processing unit 715 may include one or more processors or microprocessors which may interpret or execute stored instructions associated with one or more processes, or processing logic that implements the one or more processes. For example, in one implementation, processing unit 715 may include, but is not limited to, programmable logic such as Field Programmable Gate Arrays (FPGAs) or accelerators. Processing unit 715 may include software, hardware, or a combination of software and hardware for executing the processes described herein. Main memory 720 may include a random access memory (RAM) or another type of dynamic storage device that may store information and, in some implementations, instructions for execution by processing unit 715. ROM 730 may include a Read Only Memory (ROM) device or another type of static storage device (e.g., Electrically Erasable Programmable ROM (EEPROM)) that may store static information and, in some implementations, instructions for use by processing unit 715. Storage device 740 may include a magnetic and/or optical recording medium and its corresponding drive. Main memory 720, ROM 730 and storage device 740 may each be referred to herein as a “non-transitory computer-readable medium” or a “non-transitory storage medium.”
Input device 750 may include one or more devices that permit a user or operator to input information to device 700, such as, for example, a keypad or a keyboard, a display with a touch sensitive panel, voice recognition and/or biometric mechanisms, etc. Output device 760 may include one or more devices that output information to the operator or user, including a display, a speaker, etc. Input device 760 and output device 760 may, in some implementations, be implemented as a graphical user interface (GUI) that displays GUI information and which receives user input via the GUI. In some implementations, such as when device 700 executes functions of a CU-UP 125, input device 750 and/or output device 760 may be omitted from device 700.
Communication interface 770 may include one or more transceivers that enable device 700 to communicate with other devices and/or systems. For example, in the case where device 700 hosts the functions of a CU-CP 120 or a CU-UP 125, communication interface 770 may include a wired transceiver for communicating with other nodes via a wired network, such as, for example, via edge cloud 220, core cloud 210, or PDN 240. In implementations in which network device 700 executes the functions of a DU 115, communication interface 770 may include one or more optical transceivers for communicating with a RU 110 via optical fiber.
Device 700 may perform certain operations or processes, as may be described herein. Device 700 may perform these operations in response to processing unit 715 executing software instructions contained in a computer-readable medium, such as memory 720. A computer-readable medium may be defined as a physical or logical memory device. A logical memory device may include memory space within a single physical memory device or spread across multiple physical memory devices. The software instructions may be read into main memory 720 from another computer-readable medium, such as storage device 740, or from another device via communication interface(s) 770. The software instructions contained in main memory 720 may cause processing unit 715 to perform the operations or processes, as described herein. Alternatively, hardwired circuitry (e.g., logic hardware) may be used in place of, or in combination with, software instructions to implement the operations or processes, as described herein. Thus, exemplary implementations are not limited to any specific combination of hardware circuitry and software.
The configuration of components of device 700 illustrated in
The exemplary process includes radio slice controller 130 receiving a DU profile from each available DU 110 (block 800-
Radio slice controller 130 receives, from the SON, an updated DU performance profile for one or more of the available DUs 110 based on any changed conditions (block 810). The SON, shown in
Radio Slice controller 130 selects a DU 110, from the available DUs 110, based on the DU profile of each DU 110 (block 820). Radio slice controller 130 determines which DU's can provide a sufficient network performance (e.g., sufficient bandwidth, throughput, latency, and/or error rate), as determined from each DU's DU profile, and selects one of the determined DUs.
Radio slice controller 130 obtains the UE's user profile, and network performance requirement(s) of the application associated with the UE transport (block 830). The CU-CP 120 hosting radio slice controller 130 may control traffic to and from a particular UE 140 that is communicating via the wireless network using a particular application. The UE 140 may have a user profile associated with UE 140, and the particular application may require a certain level of network performance. For example, the application may be a Voice over Internet Protocol (VoIP) application, and the VoIP application may require a certain maximum latency, and a certain maximum error rate, on the transport path to ensure a sufficient VoIP call quality. As another example, the application may be a massively multiplayer online (MMO) game that may require a minimum bandwidth, a maximum latency, and a maximum packet loss to ensure the quality of the gaming session.
Radio slice controller 130 selects a CU-UP 125 of multiple distributed CU-UPs 125 for transport along a transport path, that includes the selected DU, based on the UE's user profile and the application network performance requirement(s) (block 840). As described above with respect to
Radio slice controller 130 receives key performance indicator (KPI) measurements associated with the chosen data path (block 850)(
Radio slice controller 130 determines if the KPI measurements satisfy the user profile requirements and the application requirements (block 860). Radio slice controller 130 compares the KPI measurement data, received from the SON, with the requirements of the UE's user profile and/or the application to determine if the network performance, across the chosen transport path, is sufficient to satisfy the user profile requirements and/or the application requirements.
If the KPI measurements indicate that the network performance via the selected transport path does not satisfy either the user profile requirements or the application requirements (NO—block 860), then the exemplary process may return to block 840 (
If the KPI measurements indicate that the network performance via the selected transport path satisfies both of the user profile requirements and the application requirements (YES—block 860), then radio slice controller 130 initiates transport between the chosen DU 110 and the chosen CU-UP 125 via the chosen transport path (block 870). During transport to/from the UE via the selected data path that includes the selected DU 110 and the selected CU-UP 125, radio slice controller 130 may receive KPI measurement updates associated with the chosen transport path (e.g., block 850). Transport over the selected transport path continues, during the UE's transport session, if radio slice controller 130 determines that the measured KPIs indicate that the network performance via the path satisfies both the user profile requirements and the application requirements (e.g., YES—block 860). If, however, radio slice controller 130 determines that the measured KPIs do not satisfy either the user profile requirements or the application requirements (e.g., NO—block 860), then the exemplary process may return to block 840 (
Though not shown in
The foregoing description of implementations provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. For example, while a series of blocks has been described with respect to
Certain features described above may be implemented as “logic” or a “unit” that performs one or more functions. This logic or unit may include hardware, such as one or more processors, microprocessors, application specific integrated circuits, or field programmable gate arrays, software, or a combination of hardware and software.
No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
All structural and functional equivalents to the elements of the various aspects set forth in this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. No claim element of a claim is to be interpreted under 35 U.S.C. § 112(f) unless the claim element expressly includes the phrase “means for” or “step for.”
In the preceding specification, various preferred embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded in an illustrative rather than restrictive sense.
