Multi-tenant wireless network management based on traffic monitoring

Abstract

An arrangement is presented that includes a multi-tenant network management system. A first virtual wireless network can be operated as part of a wireless network. The first virtual wireless network can be mapped to a first set of service level operational parameters. A second virtual wireless network can also be operated as part of the wireless network on behalf of a third entity. The second virtual wireless network can be mapped to a second set of service level operational parameters. There can be a traffic monitoring system that separately monitors and compiles traffic-related statistics for the first virtual wireless network and the second virtual wireless network. The virtual network management system can use machine learning to determine how to modify properties of the first virtual wireless network to satisfy the first set of service level operational parameters.

Description

[Technical field]

[0001] [Cross Reference] This application claims the benefit of and priority to U.S. patent application Ser. No. 16 / 518,859, filed July 22, 2019, entitled “MULTI-TENANT WIRELESS NETWORK MANAGEMENT BASED ON TRAFFIC MONITORING,” which is hereby incorporated by reference in its entirety. [Background technology]

[0002] Network operators must frequently reconfigure their networks to satisfy various quality of service metrics. Understanding how to properly reconfigure a network can be a complex task performed by highly skilled network architects. When there are stakes such as multiple virtual networks operating on a single physical network, network reconfiguration can become very complex. The arrangements detailed herein help optimize network reconfiguration. Summary of the Invention [Means for solving the problem]

[0003] Various embodiments related to a multi-tenant network management system are described. In some embodiments, a multi-tenant network management system is described. The system may include a wireless network operated by a first entity. The system may include a first virtual wireless network operated as part of the wireless network on behalf of a second entity. The first virtual wireless network may be mapped to a first set of service level operational parameters. The system may include a second virtual wireless network operated as part of the wireless network on behalf of a third entity. The second virtual wireless network may be mapped to a second set of service level operational parameters that may differ from the first set of service level operational parameters. The system may include a traffic monitoring system that may separately monitor and compile traffic related statistics for the first virtual wireless network and the second virtual wireless network. The system may include a virtual network management system in communication with the traffic monitoring system. The virtual network management system may use machine learning deployment to determine how to modify properties of the first virtual wireless network to satisfy the first set of service level operational parameters. The virtual network management system may modify the first virtual wireless network based on the machine learning deployment.

[0004] An embodiment of such a system may include one or more of the following mechanisms, where the virtual network management system modifying the first virtual wireless network may include changing an amount of wireless bandwidth allocated to the first virtual wireless network. The virtual network management system modifying the first virtual wireless network may include changing a network topology of the first virtual wireless network to reduce latency. The virtual network management system modifying the first virtual wireless network may include allocating additional processing resources to the first virtual wireless network. The virtual network management system modifying the first virtual wireless network may include moving processing capacity closer to an edge of the first virtual wireless network. Moving processing capacity closer to an edge of the first virtual wireless network may include switching data centers hosting the processing capacity. The machine learning arrangement may be a neural network that provides an output. The traffic monitoring system may compile separate short-term and long-term traffic statistics for the first virtual wireless network and the second virtual wireless network. The short-term statistics may cover a period of less than one week and the long-term statistics may cover a period of more than one week. The virtual network management system may be further configured to output a long term recommendation. The virtual network management system may be further configured to determine how to modify properties of the second virtual wireless network to satisfy a second set of service level operational parameters. The first wireless network and the second virtual wireless network may each be used exclusively for communication with Internet of Things (IoT) devices.

[0005] In some embodiments, a method for managing a multi-tenant wireless network is described. The method may include monitoring, by the wireless network, traffic associated with a first virtual wireless network operating on the wireless network. The wireless network may be operated by a first entity. The first virtual wireless network may be operated on behalf of a second entity. The first virtual wireless network may be mapped to a first set of service level operational parameters. The method may include monitoring, by the wireless network, traffic associated with a second virtual wireless network operating on the wireless network. The second virtual wireless network may be operated on behalf of a third entity. The second virtual wireless network may be mapped to a second set of service level operational parameters that are different from the first set of service level operational parameters. The method may include separately compiling, by the virtual network management system, traffic-related statistics for the first virtual wireless network and the second virtual wireless network. The method may include determining, by the virtual network management system, how to modify properties of the first virtual wireless network to satisfy the first set of service level operational parameters. The method may include modifying, by the virtual network management system, the first virtual wireless network based on the analyzing.

[0006] An embodiment of such a method may include one or more of the following mechanisms, where the virtual network management system modifying the first virtual wireless network may include changing an amount of wireless bandwidth allocated to the first virtual wireless network. The virtual network management system modifying the first virtual wireless network may include changing a network topology of the first virtual wireless network to reduce latency. The virtual network management system modifying the first virtual wireless network may include allocating additional processing resources to the first virtual wireless network. The virtual network management system modifying the first virtual wireless network may include moving processing capacity closer to an edge of the first virtual wireless network. Moving processing capacity closer to an edge of the first virtual wireless network may include switching a data center hosting the processing capacity. The determining may be performed using a neural network. The determining may include compiling separate short-term and long-term traffic statistics for the first virtual wireless network and the second virtual wireless network. The short-term statistics may cover a period of less than one week and the long-term statistics may cover a period of more than one week. The method may further include determining, by the virtual network management system, how to modify properties of the second virtual wireless network to satisfy a second set of service level operational parameters. [Brief description of the drawings]

[0007] [Figure 1] SUMMARY OF THE DISCLOSURE An embodiment of a multi-tenant network management system is described. [Diagram 2] SUMMARY OF THE DISCLOSURE An embodiment of a virtual network management system is described. [Diagram 3] SUMMARY OF THE DISCLOSURE Embodiments of modifications that may be implemented by a multi-tenant network management system to meet service level operational parameters are described. [Figure 4] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of a method for managing a multi-tenant wireless network is described. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] A wireless network operator may use a single physical wireless network to provide virtual wireless networks to multiple independent virtual network operators (VNOs). Each VNO may have a particular set of quality of service (QoS) parameters that the wireless network operator commits to providing to the VNO. The QoS for each VNO may differ in one or more respects. By way of illustration, a first VNO may be associated with its QoS parameters defining a small amount of data throughput delivered with low latency. A second VNO may be associated with its QoS parameters defining a large amount of data delivered with a higher latency. A third VNO may be associated with QoS parameters of high data throughput and very low latency.

[0009] A virtual network management system (VNMS) may function in communication with or as part of a physical wireless network. Traffic specific to each VNO's virtual wireless network (VWN) may be monitored for various characteristics (e.g., data volume, latency, etc.). The VNMS may analyze the traffic data collected for each VWN individually, periodically or intermittently. The VNMS may analyze the traffic data in combination with QoS parameters associated with a particular VWN. If the VNMS detects a situation in which a VWN is performing below its mapped QoS parameters, the VNMS may modify one or more characteristics of how the VWN operates in an attempt to meet the mapped QoS parameters. Conversely, if a situation is detected in which a VWN is performing significantly above its mapped QoS parameters, the VNMS may modify one or more characteristics of how the VWN operates in an attempt to still meet the mapped QoS parameters without expending unnecessary network resources.

[0010] The VNMS may implement modifications to the way each VWN functions. The VNMS may use forms of artificial intelligence (AI), such as trained neural networks (including attempting to make optimal decisions based on large sets of measurements or historical data), machine learning (ML), and / or big data analytics to determine how the functionality of the wireless network should be modified to satisfy the QoS parameters mapped to the VWN. Some modifications to the functionality of the wireless network may be made by the VNMS without requiring any input from an administrator. Other modifications, such as changes involving the addition and removal of hardware, may be output by the VNMS in the form of recommendations that are implemented by the administrator.

[0011] Such embodiments as detailed herein may be particularly useful for Internet of Things (IoT) focused VWNs. Many entities would prefer to function as a VNO since the VNO entity does not have to build its own physical network. Rather, the VNO may agree on QoS parameters with an entity that already has a physical wireless network in place. Furthermore, entities in the IoT space based on the particular business sector they belong to may have very different needs for QoS. As an illustration, a first entity with many parking facilities distributed across a geographical area may wish to collect data from its on-site parking system and distribute the data. Since this data is for parking, the volume may be relatively small and latency (e.g., a few seconds) may not be critical at all. However, a second entity that processes credit card transactions may wish to have significantly lower latency than the first entity. While the following embodiments focus on a VWN that communicates primarily or exclusively with IoT devices, it should be understood that other embodiments may communicate primarily or exclusively with other forms of wireless devices such as smartphones, mobile phones, etc. Wired network deployments are also possible.

[0012] Details regarding the above and other embodiments are provided in conjunction with the figures. Figure 1 illustrates an embodiment of a multi-tenant network management system 100. The multi-tenant network management system 100 may include a core wireless network 110, base stations 120 (e.g., 120-1, 120-2), IoT devices 130 (e.g., 130-1, 130-2, 130-3, and 130-4), VNO systems 140 (e.g., 140-1, 140-2), and the Internet 150.

[0013] The wireless network may be operated by an entity that may be referred to as a Physical Wireless Network Operator (PWNO). The PWNO may operate base stations 120 across a geographic region (e.g., a continent, a country, a state, a county, etc.). Depending on the type of wireless network, each cell associated with each base station among the base stations 120 may vary greatly in size. By way of illustration, a single base station (e.g., base station 120-1) may be capable of serving a relatively large geographic region, such as having a radius of 20-50 miles. Such a base station may be part of a Narrowband Internet of Things (NB-IoT) network that uses a Low Power Wide Area Network (LPWAN) radio access technology (RAT). Alternatively, the base station may use a relatively high power RAT, such as 4G Long Term Evolution (LTE) or 5G New Radio (NR). The functional communication radius of a 5G NR base station may be less than 0.5 miles. For a 4G LTE network, the base station may be an eNodeB (eNB), and for a 5G NR network, the base station may be a gNodeB (gNB).

[0014] Various IoT devices 130 may communicate with the base station 120. As an example, IoT devices 130-1 and 130-3 may be associated with a first VNO, and IoT devices 130-2 and 130-4 may be associated with a second VNO. Thus, IoT devices mapped to different VNOs may communicate with the same base station 120. Each of the base stations 120 may have a portion of the bandwidth (e.g., a bandwidth portion (BWP)) dedicated to a particular VNO. Mapping the VNOs to different BWPs may separate the VNOs on the air interface, but this arrangement may result in some statistical multiplexing loss. For the semi-static case, the system may measure the traffic of the various VNOs and adjust the BW of the BWP accordingly. These BWPs may use different portions of the overall carrier bandwidth and may use different subcarrier spacings (SCS). Alternatively, these BWPs may overlap and use the same SCS. Alternatively, IoT devices associated with different VNOs may use the same BWP for communication, since the communication may be scheduled by the base station. In such an embodiment, isolation can be achieved without losing statistical multiplexing gain by using an intelligent base station (e.g., gNB) scheduler that dynamically adjusts the BW of each VNO.

[0015] Various processing tasks may be performed directly at the base station 120. Illustratively, the gateway processing system 114 may be incorporated as part of the base station 120. The gateway processing system 114 may include one or more processors and non-transitory processor-readable media. The gateway processing system 114 may be configured to execute instructions specific to a particular VNO. Thus, data received from an IoT device 130-1 associated with a particular VNO may be processed by the gateway processing system 114-1 using instructions associated with the particular VNO. In other embodiments, the gateway processing system 114 may be separate from the base station 120 and may be part of the core wireless network 110.

[0016] The core wireless network 110 may include high level processing resources (e.g., 111-1, 111-2), an authentication system 112, core network components 113 (e.g., 113-1, 113-2), a gateway processing system 114 (e.g., 114-1, 114-2), a virtual network management system 115, VWN configuration data 116, a VNO QoS parameters data structure 118, and a traffic monitoring system 117 (e.g., 117-1, 117-2). As previously mentioned, the gateway processing system 114 may perform processing on data received from or transmitted to the IoT device 130. In some embodiments, the gateway processing system 114 is part of the core wireless network 110 and is separate from the base station 120. It should be understood that in some embodiments, some core network components 113 may be located between the gateway processing system 114 and the base station 120.

[0017] The core network components may represent at least some of the core components of a 4G LTE, NB-IoT LPWAN, or some other form of wireless network. For a 4G LTE network, the core components may include a Packet Data Network Gateway (PGW), a Servicing Gateway (SGW). For a 5G NR network, the core network components 113 may include a User Plane Function (UPF).

[0018] The traffic monitoring system 117 may monitor traffic in each component of the physical wireless network, including the individual core network components 113 and base stations 120. The traffic monitoring system 117 monitors and compiles traffic data (e.g., uplink and downlink data volume, uplink and downlink data transfer latencies, processing delays, etc.) throughout the core wireless network 110 and base stations 120. The traffic monitoring system 117 may maintain separate statistics for traffic associated with each VNO. Thus, statistics specific to each VNO are compiled and accumulated.

[0019] The traffic monitoring system 117 may maintain multiple types of traffic statistics. In some embodiments, the traffic statistics for each VNO are divided into two general categories: short-term statistics and long-term statistics. Generally, short-term statistics are specific to a relatively short time period, such as between one hour and one week, and long-term statistics are specific to a relatively long time period, such as more than one week (one month, one year, etc.). Again, the short-term and long-term statistics may be specific to each VNO.

[0020] In some embodiments, there may be high-level processing resources 111. These processing resources may be geographically and hierarchically further away from the base stations 120 than the gateway processing system 114. A single high-level processing system, such as high-level processing resource 111-1, may serve multiple base stations and gateway processing systems. The high-level processing resources 111 may have more computing resources and may perform more powerful processing and data storage for the VNO. The high-level processing resources 111 may be hosted by a geographically distributed data center. In some embodiments, the high-level processing resources 111 may not be strictly part of the core wireless network 110, but rather may communicate with the core wireless network 110. The high-level processing resources 111 may communicate with an external VNO system 140.

[0021] The VNO systems 140 may each be operated by a different virtual network operator. From each VNO's perspective, the physical wireless network appears dedicated to the VNO's data, i.e., other VNOs' use of the physical wireless network will be invisible to that VNO. A first VNO may operate one or more server systems as VNO system 140-1, and a second VNO may operate one or more server systems as VNO system 140-2. The VNO systems 140 may be completely unrelated to each other and may not communicate with each other, since each is operated by a different independent entity. Each VNO system in the VNO systems 140 may communicate with the core wireless network 110 for multiple purposes. The first VNO system 140 may send and receive data to and from the core wireless network 110 that is exchanged with IoT devices in the IoT devices 130 associated with the particular VNO system. For example, only IoT devices mapped to a VNO in the VNO system 140-1 may be allowed to exchange data with the VNO system 140-1. The VNO system 140 may also exchange authentication information with the core wireless network 110. In order for an IoT device to be authorized to communicate using the core wireless network 110, the IoT device may need to be mapped to a particular VNO and properly authenticated. Through the VNO system, the VNO provider may provide authentication information for each of its mapped IoT devices. By way of illustration, the VNO system 140-1 may provide authentication information (e.g., MAC address, IMSI) for various IoT devices, such as the IoT device 130-1. The authentication information may be stored and managed by the authentication system 112, which may include one or more servers or processing systems and one or more non-transitory processor-readable media. The authentication system 112 may receive a communication request from the IoT device 130-1. The authentication system 112 may authenticate the IoT device 130-1 based on the authentication data received from the VNO system 140-1 and may allow the IoT device 130-1 to communicate using the wireless network. IoT device 130-1 may be mapped to a VNO provider operating VNO system 140-1.

[0022] A virtual network management system (VNMS) 115 may communicate with a traffic monitoring system 117. The VNMS 115 may periodically or intermittently receive compiled statistics (e.g., long-term and / or short-term statistics) from the traffic monitoring system 117 for each VNO. The VNMS 115 may further access a data structure that stores VWN configuration data 116 detailing, for each VNO, the computing resources, bandwidth, system architecture, etc., being used to operate the VWN. The VNMS 115 may also have access to VNO QoS parameters 118, which may be stored using a non-transitory processor-readable medium. The VNO QoS parameters 118 define, for each VNO, the specific QoS parameters that need to be met. Such VNO QoS parameters 118 may include maximum latencies for uplink and downlink communications, and data throughput rates for uplink and downlink communications. These QoS parameters may be based on a contractual agreement between each VNO and the PWNO. Different VNOs may have at least some different QoS parameters. Further details regarding the VNMS 115 are provided in relation to FIG.

[0023] With respect to the components of the core wireless network 110, it should be understood that various distributed computing systems, communication buses, non-transitory processor-readable media, wired networks, and other computerized components are used for each component of the core wireless network 110. Furthermore, there are two entities: base station 120, gateway processing system 114, core network components 113, traffic monitoring system 117, and high-level processing resources 111. It should be understood that this number of entities is merely an example. For example, in a real world embodiment, there may be many more base stations 120. Similarly, in a real world implementation, it may be expected that many more than four IoT devices 130 will communicate with the base station 120.

[0024] FIG. 2 illustrates an embodiment of a Virtual Network Management System (VNMS) 115. The VNMS may be implemented using one or more computer server systems including one or more processors. Thus, the VNMS 115 may include one or more dedicated or general-purpose processors. Such dedicated processors may include processors specifically designed to perform the functions detailed herein. Such dedicated processors may be ASICs or FPGAs, which are general-purpose components physically and electrically configured to perform the functions detailed herein. Such general-purpose processors may execute dedicated software stored using one or more non-transitory processor-readable media, such as random access memory (RAM), flash memory, hard disk drive (HDD), or solid-state drive (SSD).

[0025] The VNMS 115 may include various components including a neural network 210 (trained using training data 220), a network reconfiguration engine 230, and a network recommendation engine 235. The neural network 210 may be initially trained using a set of training data 220. The training data 220 may include data including network configurations and statistics, where each instance of the network configuration and associated statistics may be mapped to a desired reconfiguration for how the network configuration should be modified based on the statistics. By way of illustration, thousands of examples with accurate network modifications may be used to form the training data 220. The neural network may be trained using the training data 220. The trained neural network 210 may be implemented using a processing system as part of the VNMS 115.

[0026] Although the VNMS 115 is depicted as using a neural network, it should be understood that other forms of AI or ML may be used. By way of illustration, other types of trained networks may be used instead of a neural network. In some embodiments, big data analytics may be used instead. In such embodiments, large amounts of data may be captured about the functioning of the virtual wireless network and analyzed for correlations, trends, etc. Such analytics may be used by the network reconfiguration engine 230 and by the network recommendation engine 235. In some embodiments, algorithms such as Kalman filters may be implemented.

[0027] After neural network 210 is trained, it may receive statistics from traffic monitoring system 117. The statistics received by neural network 210 may be specific to the VWN of each VNO. That is, for each VNO, a separate set of statistics is received by neural network 210. Thus, the output of neural network 210 will be specific to a particular VWN and VNO. In some embodiments, neural network 210 receives statistics separated into two sets, short-term statistics 201 and long-term statistics 202. In some embodiments, separate neural networks take short-term and long-term traffic statistics as inputs and provide separate outputs (e.g., short-term and long-term modifications and recommendations). As part of the analysis by neural network 210, VWN configuration data 116 and VNO QoS parameters 118 may be accessed to determine the current VWN configuration for the VNO and the QoS parameters for the particular VNO, respectively. A comparison with the VNO QoS parameters 118 may be performed to determine which QoS parameters are not being met (or are exceeded by too large a threshold margin) due to the performance of the physical wireless network.

[0028] In some embodiments, there may be an additional component that functions as a predictor. The predictor may be configured to forecast near-term traffic for each VNO, such as based on short-term statistics. Such forecasts may be used to help make optimal decisions and reconfigure the network in advance of increases or decreases in traffic for the VNO.

[0029] Based on the received traffic statistics, VWN configuration data 116, and VNO QoS parameters 118, neural network 210 may provide one or more outputs including 1) modifications to be implemented for a particular VNO's VWN, and / or 2) recommendations on how to modify a particular VNO's VWN. Network reconfiguration engine 230 may reconfigure the physical wireless network according to the output of neural network 210 to more closely match (e.g., meet or slightly exceed) the performance of the physical wireless network to the VNO QoS parameters mapped to the corresponding VNO. Details of specific changes that may be implemented by network reconfiguration engine 230 are provided in connection with FIG. 3. Information detailing the modifications 240 may be output to appropriate portions of the physical wireless network for implementation.

[0030] The network recommendation engine 235 may output recommendations of how the physical wireless network may be reconfigured by an administrator. Such recommendations may not be appropriate or possible for implementing the VNMS without administrator intervention. An illustrative example may be a recommendation to add new computing resources to a particular location in the physical wireless network. As an example of this, a particular gateway processing system, such as the gateway processing system 114-2, may not be capable of meeting the latency QoS parameters for a particular VNO. The gateway processing system 114-2 may not have additional processing resources available to allocate to the VNO. Therefore, additional physical processing resources may need to be installed as part of the gateway processing system 114-2 to help meet the QoS parameters of the VNO. In other situations, certain changes to the VWN functionality may be deemed so critical that they require administrator consent or expertise to be implemented. The recommendations output by the network recommendation engine 235 may be output as recommendations 245, such as for presentation to an administrator via a display device as a generated report.

[0031] 2, various modifications 240 may be implemented directly by the VNMS 115 in the physical wireless network to verify the performance of the VNO's VWN against the QoS parameters mapped to the VNO. FIGURE 3 illustrates an embodiment 300 of modifications that may be implemented by the multi-tenant network management system to satisfy service level operational parameters.

[0032] A first type of modification that may be implemented by the VNMS 115 without administrator consent or input may be to reallocate processing resources. As an illustration, for a particular VNO, high-level processing may be performed in a particular data center. The VNMS 115 may determine that the distance between this data center and the IoT devices it serves creates too much latency compared to the allowed QoS parameters mapped to the VNO. Thus, the high-level processing resources 111-2 may be moved to a different data center that offers, for example, lower latency.

[0033] Conversely, the VNMS 115 may determine that the latency for communications between a currently used data center and the IoT devices it serves exceeds a smaller threshold amount than required by the VNO's QoS parameters, and high-level processing resources 111-2 may therefore be moved to a different data center, for example, that offers higher latency but has other benefits (e.g., lower cost).

[0034] A second type of modification that may be implemented by the VNMS 115 without administrator consent or input may be to move processing functions between components. By way of illustration, for a particular VNO, processing may be performed using high-level processing resources 111-1. The VNMS 115 may determine that the latency within the core wireless network 110 is too high compared to the allowed QoS parameters mapped to the VNO. Thus, the processing of the high-level processing resources 111-1 performed on behalf of the particular VNO may be moved to a gateway processing system such as gateway processing system 114-1 (i.e., closer to the edge of the core wireless network 110), as indicated by arrow 320.

[0035] The reverse may also be true. The VNMS 115 may determine that latency within the core wireless network 110 exceeds a threshold below the allowed QoS parameters mapped to the VNO. Therefore, processing performed on behalf of a particular VNO may be moved from a gateway processing system, such as gateway processing system 114-1, to higher level processing resources 111, as indicated by arrow 320. Such an arrangement may add latency, but may reduce costs by moving processing away from the edge of the core wireless network 110.

[0036] A third type of modification that may be implemented by the VNMS 115 without administrator consent or input may be to adjust the amount of bandwidth of one or more base stations designated for a particular VNO. Such modifications may be used for semi-static control of BW per VNO. Such BW adjustments may be dynamically implemented by the base station scheduler. For some VNOs, portions of bandwidth are explicitly received at one or more base stations 120. These portions of bandwidth may be explicitly designated BWPs. If the amount of data throughput (uplink, downlink, or both) for a particular VNO does not meet the QoS parameters of the VNO, a bandwidth reallocation 330 may be implemented to add additional bandwidth to the VNO's VWN. Conversely, if the amount of bandwidth designed for the VNO's VWN results in data throughput that is at least a threshold above the QoS parameters of the VNO, the bandwidth for the VNO may be reduced so that it may be added for communication with IoT devices of another VNO.

[0037] A fourth type of modification that may be implemented by the VNMS 115 without administrator consent or input may be to adjust the amount of processing resources allocated to components of the core wireless network 110. If traffic statistics indicate that processing is taking too long to meet the VNO's QoS parameters, available additional processing resources, such as processing resources 340 of high-level processing resources 111-1, may be allocated to the VNO's VWN. Alternatively, if traffic statistics indicate that processing time could be increased without violating the VNO's QoS parameters, processing resources may be deallocated from the VNO's VWN and dedicated to other tasks (e.g., the VWN of some other VNO).

[0038] A fifth type of modification that may be implemented by the VNMS 115 without administrator consent or input may be to adjust the topology of how the core wireless network components communicate. By way of illustration, if the total latency of delivering data from the VNO's IoT devices to the VNO's associated VNO system 140-1 is too high, the gateway processing system 114 may be instructed to communicate directly with the VNO system 140-1, rather than delivering the data through higher level processing resources. Such an arrangement may be understood as a change to the topology or hierarchy of the VNO's VWN.

[0039] Various methods may be implemented using the systems detailed in connection with Figures 1-3. Figure 4 illustrates an embodiment of a method 400 for managing a multi-tenant wireless network. Each block of method 400 may be implemented using the systems of Figures 1-3. In particular, each block of method 400 may be implemented using the physical wireless network and its components, such as a traffic monitoring system and a VNMS.

[0040] In block 405, traffic may be monitored on the physical wireless network, such as by using various distributed traffic monitoring components. By way of illustration, each data packet may be monitored through each component of the physical wireless network. The traffic monitored in block 405 may be mapped to a particular VWN (such as based on the IoT device with which it is associated). This VWN is linked to a particular VNO. Thus, a first entity operating the physical wireless network has reached an agreement to operate the VWN on behalf of a second entity (VNO). The traffic monitored in block 405 may include tracking the amount of uplink and downlink data, the latency of the uplink and downlink data across some or all components of the wireless network. Tracking may also be performed within an amount of time to perform processing on data received from or transmitted to a user device, such as a wireless IoT device. Traffic may be monitored with respect to time, and thus it may be possible to identify peaks and troughs of VWN traffic for a VNO.

[0041] Similar to block 405, traffic may be monitored on the physical wireless network in block 410. However, in this block, the traffic monitored may be linked to a different (second) VWN. This VWN is linked to a different VNO. Thus, a first entity operating the physical wireless network has reached an agreement to operate another VWN on behalf of a third entity (VNO). The traffic monitored in block 410 may include tracking the amount of uplink and downlink data, the latency of uplink and downlink data across some or all components of the wireless network. Tracking may also be performed within an amount of time to perform processing on data received from or transmitted to a user device, such as a wireless IoT device. Traffic may be monitored with respect to time, and therefore, it may be possible to identify peaks and troughs of VWN traffic for a VNO. The traffic data of block 410 is maintained separately from the traffic data of block 405. Although the method 400 includes an example of two VNOs with separate VWNs, it should be understood that this is only one example and other embodiments may include a larger number of VNOs, each with its own VWN.

[0042] At block 415, traffic statistics may be compiled separately for the first VWN and the second VWN. These traffic statistics may include latency data (uplink and / or downlink), data throughput (uplink and / or downlink), and processing time for some or all components of the VWN. In some embodiments, the traffic statistics are separated into two categories, short-term statistics and long-term statistics. In some embodiments, these statistics may be put into a human-readable format for output in the form of a report. The traffic statistics compiled at block 415 may be provided to the VNMS for analysis.

[0043] At block 420, traffic statistics for a VWN of a particular VNO may be analyzed. The analysis of block 420 may be performed using a trained neural network. Additionally, the analysis of block 420 may include comparing the traffic statistics for a particular VWN to VNO QoS parameters (e.g., latency, throughput, data overall) specific to the VNO in which the VWN is operated. This comparison may be used to determine situations in which the QoS parameters are not being met, are being met but exceed a threshold, or both. The analysis of block 420 may further include analyzing current configuration data for the VWN.

[0044] One or more properties of the VWN may be determined to be modified in block 425. The modifications determined by the neural network in block 420 may be based on how the neural network was trained. A non-limiting list of properties that may be modified in block 425 is detailed in connection with FIG.

[0045] At block 430, one or more recommendations may be output based on the analysis performed by the neural network at block 420. The recommendations output at block 430 may be presented to an administrator in the form of a report. In some embodiments, an administrator's acceptance of a recommendation may cause the VNMS to implement the recommendation. In other situations, an administrator may need to manually implement the recommendation (such as by installing new hardware).

[0046] Following performance of block 430, blocks 420-430 may be performed for the second VWN. This process may continue until each VWN operated using the physical wireless network has been analyzed and modified if necessary.

[0047] The methods, systems, and devices discussed above are exemplary. Various configurations may omit, substitute, or add various procedures or components as appropriate. Illustratively, in alternative configurations, methods may be performed in different orders than described, and / or various steps may be added, omitted, and / or combined. Also, features described with respect to some configurations may be combined in various other configurations. Different aspects and elements of the configurations may be combined in a similar manner. Also, technology evolves, and thus many of the elements are exemplary and do not limit the scope of the disclosure or claims.

[0048] Specific details are given in the description to provide a thorough understanding of example configurations (including implementations). However, the configurations may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail to avoid obscuring the configurations. This description provides only example configurations and does not limit the scope, applicability, or configuration of the claims. Rather, the foregoing description of the configurations will provide one skilled in the art with an effective description for implementing the described techniques. Various changes may be made in the function and arrangement of elements without departing from the spirit or scope of the disclosure.

[0049] Also, the configurations may be described as processes depicted as flow diagrams or block diagrams. Although each may describe the operations as a sequential process, many of the operations may be performed in parallel or simultaneously. Also, the order of operations may be rearranged. A process may have additional steps not included in the figures. Furthermore, the example methods may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. If implemented by software, firmware, middleware, or microcode, the program code or code segments to perform the necessary tasks may be stored in a non-transitory computer-readable medium, such as a storage medium. A processor may perform the described tasks.

[0050] While several example configurations have been described, various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the disclosure. For example, the above elements may be components of a larger system, other rules may take precedence over or otherwise modify the application of the invention, and some steps may be undertaken before, during, or after considering the above elements.

Claims

1. a wireless network operated by a first entity; a first virtual wireless network operated as part of the wireless network on behalf of a second entity, the first virtual wireless network is mapped to a first set of service level operational parameters; the first virtual wireless network; a second virtual wireless network operated as part of the wireless network on behalf of a third entity, the second virtual wireless network is mapped to a second set of service level operational parameters that are different from the first set of service level operational parameters. the second virtual wireless network; a traffic monitoring system for monitoring and compiling separate short-term and long-term statistics for each of the first virtual wireless network and the second virtual wireless network, the short-term statistics covering a period of less than one week and the long-term statistics covering a period of more than one week; and a virtual network management system in communication with the traffic monitoring system, the virtual network management system uses a machine learning arrangement to determine how to modify properties of the first virtual wireless network to satisfy the first set of service level operational parameters, the machine learning arrangement using the short-term statistics and the long-term statistics for each of the first virtual wireless network and the second virtual wireless network as separate inputs; the virtual network management system modifies the first virtual wireless network based on the deployment of the machine learning. The virtual network management system; A multi-tenant network management system, including:

2. The multi-tenant network management system of claim 1 , wherein the virtual network management system modifying the first virtual wireless network includes changing an amount of wireless bandwidth allocated to the first virtual wireless network.

3. 2. The multi-tenant network management system of claim 1, wherein the virtual network management system modifying the first virtual wireless network includes changing a network topology of the first virtual wireless network to reduce latency.

4. The multi-tenant network management system of claim 1 , wherein the virtual network management system modifying the first virtual wireless network includes allocating additional processing resources to the first virtual wireless network.

5. The multi-tenant network management system of claim 1 , wherein the virtual network management system modifying the first virtual wireless network includes moving processing power closer to an edge of the first virtual wireless network.

6. The multi-tenant network management system of claim 5 , wherein moving processing power closer to the edge of the first virtual wireless network includes switching a data center hosting the processing power.

7. The multi-tenant network management system of claim 1 , wherein the machine learning arrangement is a neural network that provides an output.

8. The multi-tenant network management system of claim 1 , wherein the virtual network management system is further configured to output long-term recommendations.

9. 10. The multi-tenant network management system of claim 1, wherein the virtual network management system is further configured to determine how to modify properties of the second virtual wireless network to satisfy the second set of service level operational parameters.

10. 2. The multi-tenant network management system of claim 1, wherein the first virtual wireless network and the second virtual wireless network are each used exclusively for communication with Internet of Things (IoT) devices.

11. 1. A method for managing a multi-tenant wireless network, comprising: monitoring, by a wireless network, traffic associated with a first virtual wireless network operating on the wireless network, comprising: the wireless network is operated by a first entity; the first virtual wireless network is operated on behalf of a second entity; the first virtual wireless network being mapped to a first set of service level operational parameters; monitoring, by the wireless network, traffic associated with a second virtual wireless network operating on the wireless network; the second virtual wireless network is operated on behalf of a third entity; the second virtual wireless network being mapped to a second set of service level operational parameters that differ from the first set of service level operational parameters; compiling, by a virtual network management system, separate short-term and long-term statistics for each of the first virtual wireless network and the second virtual wireless network, the short-term statistics covering a period of less than one week and the long-term statistics covering a period of more than one week; determining, by the virtual network management system, using a machine learning deployment to determine how to modify properties of the first virtual wireless network to satisfy the first set of service level operational parameters, the machine learning deployment using the short-term statistics and the long-term statistics for each of the first virtual wireless network and the second virtual wireless network as separate inputs; modifying the first virtual wireless network with the virtual network management system based on the determining. The method includes:

12. 12. The method for managing a multi-tenant wireless network of claim 11, wherein the virtual network management system modifying the first virtual wireless network includes changing an amount of wireless bandwidth allocated to the first virtual wireless network.

13. 12. The method for managing a multi-tenant wireless network of claim 11, wherein the virtual network management system modifying the first virtual wireless network includes changing a network topology of the first virtual wireless network to reduce latency.

14. 12. The method for managing a multi-tenant wireless network of claim 11, wherein the virtual network management system modifying the first virtual wireless network includes allocating additional processing resources to the first virtual wireless network.

15. 12. The method for managing a multi-tenant wireless network of claim 11, wherein the virtual network management system modifying the first virtual wireless network includes moving processing power closer to an edge of the first virtual wireless network.

16. 20. The method for managing a multi-tenant wireless network of claim 15, wherein moving processing power closer to the edge of the first virtual wireless network includes switching a data center hosting the processing power.

17. 12. The method for managing a multi-tenant wireless network of claim 11, wherein the determining is performed using a neural network.

18. 12. The method for managing a multi-tenant wireless network of claim 11, further comprising determining, by the virtual network management system, how to modify properties of the second virtual wireless network to satisfy the second set of service level operational parameters.

Images