Cellular Network Capacity Slicing System and Method

Abstract

Various arrangements for managing cellular network slicing are detailed. A cellular network management system can obtain performance data from multiple cellular network components of a cellular network over time. The cellular network management system can analyze the performance data from the multiple cellular network components to create a cellular network model that describes the performance of discrete portions of the cellular network over time. A service request can be received from an external entity, defining quality of service (QoS) parameters. A cellular network access condition package can be created that defines one or more conditions under which the external entity is eligible to utilize the cellular network. The cellular network component can then be configured to allow a user equipment (UE) of the external entity access to the cellular network and can provide data services to the UE.

Description

Technical Field

[0001] Cross - Reference to Related Applications This application claims the benefit and priority of U.S. Patent Application No. 16 / 844,337, entitled "CELLULAR NETWORK CAPACITY SLICING SYSTEMS AND METHODS," filed on April 9, 2020, which is hereby incorporated by reference in its entirety.

Background Art

[0002] The architecture of a cellular network can be complex. Similarly, the demands of users in a cellular network can be complex in that they can vary significantly with time and location. External entities desiring wireless access to a cellular network can contact the network administrator to obtain access. Typically, a standard set of items defining access conditions is provided to the client. Such a configuration may not be optimal because it does not take into account the network load that the cellular network is experiencing at the location and time expected to be used by the client. The configurations detailed herein focus on how to efficiently allocate capacity in a cellular network based on client requirements and the capacity of the cellular network.

Summary of the Invention

[0003] Various embodiments are described for a method of managing cellular network slicing. In some embodiments, a method of managing cellular network slicing is described. The method can include obtaining performance data over time from a plurality of cellular network components of a cellular network by a cellular network management system. The plurality of cellular network components can include radio access network (RAN) components and a cellular network data center of a core cellular network. The method can include analyzing the performance data from the plurality of cellular network components by the cellular network management system to create a cellular network model indicative of the performance of discrete portions of the cellular network over time. The method can include receiving a service request by the cellular network management system from an external entity separate from the cellular network and the entity operating the cellular network management system. The service request can define a plurality of quality of service (QoS) parameters requested by the external entity. The method can include analyzing the cellular network model by the cellular network management system to determine if the cellular network has sufficient available resources to meet the plurality of QoS parameters of the service request. The method can include creating, by the cellular network management system, a cellular network access condition package. The cellular network access condition package can define one or more conditions for an external entity to be eligible to utilize the cellular network. The method can include transmitting, by the cellular network management system, the cellular network access condition package to the external entity. The method can include receiving, by the cellular network management system, acceptance of the cellular network access condition package from the external entity.The method can include configuring at least some of a plurality of cellular network components by a cellular network management system to permit access to a cellular network by a user equipment (UE) of an external entity according to a cellular network access condition package. The method can include providing a data service to a UE of an external entity by a cellular network according to a cellular network access condition package.

[0004] Embodiments of such a method can include one or more of the following features: The plurality of QoS parameters can include an indication of a location where the QoS parameters will be met. Performance data obtained from a plurality of cellular network components of a cellular network can include radio congestion data for a location where the QoS parameters will be met. The cellular network access condition package can include matching QoS parameters that can closely match the QoS parameters of a service request. The QoS parameters of a service request can include a period defining when it is required that the QoS parameters be realized. The cellular network access condition package can include a first set of modified QoS parameters that are different from the QoS parameters of a service request. The cellular network access condition package can further include a second set of QoS parameters that can match the QoS parameters of a service request. The cellular network access condition package can further include a first price mapped to the first set of QoS parameters and a second price mapped to the second set of QoS parameters. The cellular network access condition package can indicate a price.

[0005] In some embodiments, a cellular network management system is described. The system can comprise a communication interface that communicates with a plurality of cellular network components of a cellular network. The system can comprise one or more processors that communicate with the communication interface. The system can comprise a memory that stores instructions that, when executed by the processor, configure the apparatus to obtain performance data from a plurality of cellular network components of the cellular network over time via the communication interface. The apparatus can analyze the performance data from the plurality of cellular network components to create a cellular network model that represents the performance of discrete portions of the cellular network over time. The apparatus can receive a service request from an external entity separate from the cellular network and the entity operating the cellular network management system. The service request can define a plurality of quality of service (QoS) parameters requested by the external entity. The apparatus can analyze the cellular network model to determine if the cellular network has sufficient available resources to meet the plurality of QoS parameters of the service request. The apparatus can create a cellular network access condition package. The cellular network access condition package can define one or more conditions under which the external entity can be eligible to utilize the cellular network. The apparatus can transmit the cellular network access condition package to the external entity. The apparatus can receive acceptance of the cellular network access condition package from the external entity. The apparatus can configure at least some of the plurality of cellular network components to permit access to the cellular network by a user equipment (UE) of the external entity in accordance with the cellular network access condition package.

[0006] Embodiments of such a system can include one or more of the following features: The plurality of QoS parameters can include an indication of a location where the QoS parameters will be met. Performance data obtained from a plurality of cellular network components of a cellular network can include wireless congestion data for a location where the QoS parameters will be met. A cellular network access condition package can include matching QoS parameters that can closely match the QoS parameters of a service request. The QoS parameters of a service request can include a period that defines when it is required that the QoS parameters be realized. A cellular network access condition package can include a first set of modified QoS parameters that are different from the QoS parameters of a service request. A cellular network access condition package can further include a second set of QoS parameters that match the QoS parameters of a service request. A cellular network access condition package can further include a first price mapped to the first set of QoS parameters and a second price mapped to the second set of QoS parameters. A cellular network access condition package can indicate a price.

[0007] In some embodiments, a non-transitory computer-readable storage medium is described. When executed by a computer, the medium can include instructions that cause the computer to obtain performance data from a plurality of cellular network components of a cellular network over time. The plurality of cellular network components can include radio access network (RAN) components and a cellular network data center of a core cellular network. The medium can analyze the performance data from the plurality of cellular network components to create a cellular network model that represents the performance of discrete portions of the cellular network over time. The medium can receive a service request from an external entity separate from the entity operating the cellular network and the cellular network management system. The service request can define a plurality of quality of service (QoS) parameters requested by the external entity. The medium can analyze the cellular network model to determine if the cellular network has sufficient available resources to meet the plurality of QoS parameters of the service request. The medium can create a cellular network access condition package. The cellular network access condition package can define one or more conditions for an external entity to be eligible to use the cellular network. The medium can transmit the cellular network access condition package to the external entity. The medium can receive acceptance of the cellular network access condition package from the external entity. The medium can configure at least some of the plurality of cellular network components to permit access to the cellular network by a user equipment (UE) of the external entity in accordance with the cellular network access condition package.

[0008] Embodiments of such a medium can include one or more of the following features: The plurality of QoS parameters can include an indication of a location where the QoS parameters will be met. Performance data obtained from a plurality of cellular network components of a cellular network can include wireless congestion data for a location where the QoS parameters will be met.

[0009] A further understanding of the nature and advantages of various embodiments can be realized by referring to the following figures. In the accompanying figures, like components or mechanisms may have the same reference label. Further, various components of the same type may be distinguished by appending a dash followed by a second label that differentiates between like components. If only the first reference label is used in the specification, the description is applicable to any of the like components having the same first reference label, regardless of the second reference label.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Best Mode for Carrying Out the Invention

[0011] Determining the conditions under which a client should be allowed to join a cellular network can be complex. A client may wish to use a particular cellular network for telephone service in order to access the Internet generally or to access a particular remote server system or cloud service provider. The client may have a number of user equipment (UE) (e.g., dozens, hundreds, thousands, etc.) that will access the cellular network. Additionally or alternatively, the client may have specific requirements with respect to the network bandwidth, minimum acceptable packet loss, and / or maximum acceptable latency and jitter (variation in delay when transferring packets) required to communicate with various remote server systems, which can be a function of time and location. For example, a video provider intending to stream video using a cellular network may require that various quality of service (QoS) parameters be met, and these requirements can be a function of the service parameters, time, and location.

[0012] Conventionally, a cellular network operator can define QoS parameters that the cellular network can be expected to meet over a large geographical area. However, such QoS parameters may not be accurate regarding what the cellular network can achieve in a particular unremarkable location. The capabilities of a cellular network can vary significantly depending on the geographical location, depending on the resources deployed in the cellular network. Whether the cellular network can support the QoS parameters requested by a client can vary significantly depending on the location where the cellular network is accessed, the time of day of such access, and the day of the week of such access. For example, a cellular network may have significantly more bandwidth available at night compared to during the day. In this example, the cellular network may be able to meet certain QoS parameters at night in a particular location, but may not be able to meet them during the day due to other commitments and network constraints.

[0013] The embodiments detailed in this specification focus on providing a cellular access network condition package to a client that defines the conditions for the client to have its UE access the cellular network. The cellular access network condition package can take into account factors such as the number of UEs, the location of the UEs, the amount of bandwidth desired in a particular location, the amount of latency permitted in a particular location, the days of the week when QoS parameters must be met, the time periods when those QoS parameters must be met, etc. The cellular access network condition package can be constructed taking into account the past, current, and predicted performance of the cellular core network and radio access network (RAN) of the cellular network. For example, the amount of radio resources in a given location that can be dedicated to a particular client can be determined. The client can choose to access the cellular access network condition package, and as a result, the cellular network will be configured for the client's UE to have access to the cellular network. Alternatively, in response, the client can choose to reject the cellular access network condition package or provide a new request with modified requirements.

[0014] Further details regarding such embodiments and other embodiments are provided in connection with the drawings. FIG. 1 is an embodiment of a hierarchical cellular network system 100 (the "System 100"). The cellular network can include a radio access network (RAN) and a core cellular network. UE 110 can connect to the cellular network using various types of base stations or access points. The UE can include: a mobile phone, a smartphone, a video camera, an audio streaming device, a video streaming device, a modem, a sensor device, or any other form of wireless device that communicates with the cellular network. UE 110 can be in different geographical locations and thus can communicate with the cellular network using different components of the RAN of the cellular network.

[0015] UE 110-1 and UE 110-2 can communicate with some or all of the RAN component 120-1 based on their location. The RAN component 120-1 can include a local AP 121-1, a small BS 122-1, and a large BS 123-1 (e.g., a gNodeB in a 5G New Radio (NR) cellular network). The local AP can provide coverage in a relatively small geographical area such as within a house or building. The small BS 122-1 can provide cellular network access over a medium-sized geographical area and can have the capacity to handle fewer instances of UEs than other base stations. For example, the small BS 122-1 can be installed in an urban environment to provide access in a neighboring environment. The large BS 123-1 can provide cellular network coverage for a relatively large geographical area such as along a highway or to cover a large neighboring environment. The large BS 123-1 can have the capacity to handle a larger number of instances of UEs than the small BS.

[0016] The UE associated with a specific client can have a reserved amount of radio bandwidth. Thus, in a specific cell of the hierarchical cellular network system 100, even if there is no large amount of radio traffic between the UE and the base station (and / or access point), it may be necessary to reserve the wireless radio resources of the RAN to meet the pre-agreed QoS metrics for a specific client.

[0017] The local AP 121-1, small BS 122-1, and large BS 123-1 can be part of a cellular network operating according to one or more radio access technologies (RATs). For example, the cellular network can be a 5G NR, 4G LTE, 3G, or GSM-based cellular network. The cellular network can operate according to multiple RATs. For example, the cellular network can be a hybrid 4G and 5G network.

[0018] Each of the local AP 121-1, small BS 122-1, and large BS 123-1 can communicate with an edge data center (EDC). In some embodiments, a dedicated EDC can be used for each component or each type of component of the RAN. For example, the EDC 131-3 can be dedicated to the large BS 123-1. In other embodiments, the EDC 131-3 can serve multiple base stations in a geographical area. The EDC 131-2 can be dedicated to the small BS 122-1 or can serve multiple base stations (e.g., only a small number of base stations or a mixture of base stations of different sizes). Similarly, the EDC 13-1 can be dedicated to the local AP 121-1 or a group of local APs.

[0019] The EDC130-1 group can serve as an interface to the cellular core network and communicate with components of the RAN. EDC131-1, 131-2, and 131-3 can route data within the cellular core network. For example, data received by EDC131-2 targeted at a UE communicating with large BS123-1 can be directly routed to EDC131-3. However, not all EDC131s communicate directly with each other. For example, EDC131-4 may not communicate directly with EDC131-2. Therefore, when EDC131-2 is routing data to a UE communicating with EDC131-3, the data may need to be routed through another data center of the cellular core network, such as through regional data center (RDC) 140-1. In this example, RDC140-1 serves as an intermediate node for routing data between EDC131-2 and EDC131-4.

[0020] Each RDC such as RDC140-1 can mainly serve the role of routing data between different data centers. RDC140-1 can communicate with multiple EDCs. When data is routed between EDCs that communicate directly with RDC140-1, the upper-level components of the cellular core network hierarchy may not need to be involved in the routing of the data. However, when data is routed to an EDC that does not communicate directly with RDC140-1, the upper-level components of the cellular core network hierarchy may need to be used to complete the routing.

[0021] The domestic data center (NDC) 150 can represent the top level in the cellular network hierarchy of the system 100. The NDC 150 can communicate with all the RDCs 140 of the cellular core network. And all the RDCs 140 can communicate with the EDC 131 of the cellular network. Such a hierarchy can enable data anywhere within the cellular network to be routed to other devices. The EDC, RDC, and NDC can collectively be called the nodes of the core cellular network.

[0022] As can be seen in FIG. 1, the configuration of the RAN component 120-1 and the group of EDCs 130-1 can be replicated in other geographical regions: UEs 110-3 and 110-4 communicate with the RAN component 120-2 (local AP 121-2, small BS 122-2, large BS 123-2), and the RAN component 120-2 communicates with the group of EDCs 130-2; UEs 110-4 and 110-5 communicate with the RAN component 120-3 (local AP 121-3, small BS 122-3, large BS 123-3), and the RAN component 120-3 communicates with the group of EDCs 130-3; UEs 110-7 and 110-8 communicate with the RAN component 120-4 (local AP 121-4, small BS 122-4, large BS 123-4), and the RAN component 120-4 communicates with the group of EDCs 130-4. The group of EDCs 130-2 (including EDCs 131-4, 131-5, and 131-6) communicates with the RDC 140-1. The groups of EDCs 130-3 (including EDCs 131-7, 131-8, and 131-9) and EDCs 130-4 (including EDCs 131-10, 131-11, and 131-12) communicate with the RDC 140-2. The RDC 140-2 communicates with the NDC 150.

[0023] In the example of system 100, only a few components are shown. For example, UE110-3 and UE110-4 are shown as communicating with RAN component 120-2. In reality, a much larger number of UEs can communicate with the cellular network using RAN component 120-2. Similarly, each group of RAN components 120 can include a much larger number of local APs 121, small BSs 122, and / or large BSs 123. There may be fewer or more EDCs 131. There may be fewer or more levels within the hierarchy of the core cellular network. For example, in a cellular network, if there are more EDCs, there may be one or more additional levels in the hierarchy below the NDC.

[0024] In system 100, the hierarchy is symmetric in that each grouping of RAN components 120 includes local APs, small BSs, and large BSs. Each of the RAN components communicates with an EDC, each group of EDCs communicates with an RDC, and the RDC communicates with an NDC. Such a configuration is unlikely to be implemented in the real world due to variations in the density of UEs in a given area, variations in the amount of uplink and downlink traffic by UEs in a given area, geographical variations, time-of-use trends, locations where UEs tend to gather, connections to cloud service providers, and bandwidth availability. FIG. 2 is an embodiment of a more complex hierarchical cellular network that more represents the real-world cellular network hierarchy that may exist.

[0025] In system 200, there may be variations in components within the cellular network. As described with respect to system 100, UE110-1 and UE110-2 can communicate with RAN component 120-1. However, in system 200, there may be only two EDCs present within the group of EDC130-1, and each EDC of group EDC130-1 may not be able to communicate directly with each other. Each EDC of the group of EDC130-1 can communicate with RDC140-1.

[0026] Various components such as RDC140-1 and NDC150 can communicate with cloud service provider (CSP) 240. The CSP can represent a third-party service provider that provides storage and processing functions that can be used by various entities. For example, a client that can operate a variety of UEs on system 200 can have storage and processing functions hosted by either cloud service provider 240-1 or CSP240-2. Further or alternatively, an entity can operate a private server system such as private server system 250 that has storage and processing functions dedicated to the entity. CSP240 and private server system 250 can have only dedicated bandwidth with specific components of the cellular core network. For example, cloud service provider 240-1 has dedicated bandwidth with RDC140-1. Thus, for example, when UE210-6 requests data from CSP240-1, the request may be routed through, in some cases, RDC140-2, NDC150, and RDC140-1, or RDC140-2 and RDC140-1.

[0027] In system 200, all wireless communications may not be terrestrial. Instead, UE210-1 may be a satellite modem or satellite phone that communicates via a low Earth orbit (LEO), medium Earth orbit (MEO), or geostationary Earth orbit (GEO) satellite 215. Satellite 215 can relay communications between UE210-1 and satellite gateway 217. Satellite gateway 217 can include or communicate with EDC231-1. As a possible deviation from the hierarchy of system 100, EDC231-1 may communicate directly with NDC150 instead of communicating with the RDC. Thus, for example, if data is routed from UE210-1 to UE110-1, EDC231-1 can route the data through NDC150 to RDC140-1 and then to EDC131-2.

[0028] In system 200, not all groups of RAN components include the same equipment. For example, the group of RAN components 220-1 includes three large BSs 223-1, 223-2, and 223-3, all served by EDC231-1. In the example of FIG. 2, there are a large number of UEs (represented by UE210-4, UE210-5, UE210-6, and UE210-7) that communicate with the group of RAN components 220-2. The RAN components 220-2, which include two small base stations 222-1 and 222-3 and a single large BS123-4, are served by two EDCs 231-3 and 231-4 of the group of EDC230-1. The group of EDC230-1 has a dedicated bandwidth for communicating with CSP240-2. Thus, it should be understood that the number and type of RAN components communicating with the EDC may vary. Furthermore, the components of the cellular core network with which the EDC communicates may also vary.

[0029] The amount of bandwidth available between components of a cellular core network can be adjusted to achieve a certain performance metric. For example, UE210-2 and 210-3 may require that certain minimum quality of service (QoS) metrics (such as latency, jitter, packet loss, bandwidth, etc.) be met for communication with some remote system such as private server system 250. To meet the QoS metric, additional dedicated bandwidth 244 can be established between EDC231-2 and RDC140-2, and dedicated bandwidth 241 can be established between RDC140-2 and NDC150.

[0030] Dedicated bandwidth within the hierarchy of a cellular core network can be established between components to help achieve a specific QoS metric. For example, RDC140-1 and RDC140-2 can have a direct dedicated bandwidth between them for, among other things, increasing the bandwidth and reducing the latency for EDC231-1 and EDC231-3 to access CSP240-1.

[0031] System 200 may be capable of supporting smart routing and using this to compensate for unavailable connections. For example, RDC140-2 can normally have dedicated bandwidth 242 to CSP240-2, but dedicated bandwidth 242 may be unavailable due to a problem or maintenance being performed. Data that is normally routed directly between RDC140-2 and CSP240-2 can instead be routed through NDC150.

[0032] In system 200, the amount of bandwidth between the RAN component 120 and the UE 110 can be allocated based on the bandwidth QoS parameters of various clients. Therefore, in a given location, a particular client can have a reserved "slice" of radio resource blocks that are available. If a client's UE is not using its reserved bandwidth, this bandwidth can be used to provide services to other client UEs. Also, assuming that not all clients will request the maximum allowable amount of bandwidth simultaneously, it may be possible to overbook the bandwidth. The amount of radio bandwidth that is not reserved in a given location can be considered for whether to provide services to any new entity and under what conditions.

[0033] The number and arrangement of UEs, BSs, EDCs, RDCs, NDCs, CSPs, and the private server system of system 200 are only examples. Further, the connections between such components are only examples of how such a network can be arranged. A real-world cellular network deployed over a large geographic area is significantly more complex and will include a greater number of components.

[0034] Figure 3 is an embodiment of a cellular network management system operating within the core network of a cellular network system 300. The cellular network system 300 can represent an embodiment of system 200 with the addition of a cellular network management system (CNMS) 301.

[0035] CNMS301 can be implemented using a server system that obtains performance data from various components of a cellular core network. CNMS301 can request or automatically receive status data (which can be timestamped) from all EDCs, RDCs, and NDCs of the cellular core network. If a larger number of component layers exist within the core network of the cellular network, CNMS301 also receives status data from such components. The status data received by CNMS301 can include the number of UEs being served, the amount of bandwidth used, the amount of available bandwidth, packet loss, latency, jitter between components of the core network, and the available connections within the core network. CNMS301 can receive performance data regarding RAN components from the EDC. For example, CNMS301 can receive from the EDC status data indicating the available radio resources, radio bandwidth, radio performance metrics, and the number of UEs actively communicating with the BS or local AP.

[0036] CNMS301 can collect such status data for multiple purposes. First, the status data can be used to create models of the current end-to-end performance of the cellular core network and RAN, as well as the capabilities of the cellular core network and RAN. Second, the status data can be used to create usage models of the cellular network over time. For example, various parts of the cellular core network and RAN may be highly utilized during a particular time period or during a particular event (e.g., a sports event that results in a large number of UEs being present at a location such as a stadium).

[0037] In some embodiments, each component of the cellular network periodically or occasionally transmits status data to the CNMS 301. In other embodiments, the CNMS 301 transmits a query to each component of the cellular network and receives status data in response. In still other embodiments, a mixture of queries and periodic or intermittent reporting is used. Further or alternatively, the RAN component 120 can transmit usage data to the CNMS 301. The RAN component 120 can transmit data indicating the radio resources used and / or available between the UE and the RAN component transmitting the data. Thus, for example, the large BS 223-1 can transmit performance data indicating the usage of radio resources to the CNMS 301 as performance data 302. For example, such performance data can indicate the number or percentage of resource blocks available in the RAN (a resource block is a defined time slot on a subcarrier frequency capable of transmitting a plurality of OFDM signals). Depending on the embodiment, the RAN component can relay such performance data to the CMMS 301 via the cellular network system 300, such as via the EDC 231-2. In other embodiments, an RAN component such as the gNodeB of the large BS 223-1 can transmit performance data directly to the CNMS 301.

[0038] The client system 310 can include one or more server systems that enable a client to transmit service requests to the CNMS 301 via a network such as the Internet 315. The CNMS 301 can respond to the client system 310 using a cellular network access condition package. It should be understood that many client systems can communicate with the CNMS 301 via the Internet 315 and / or other networks.

[0039] Figure 4 shows an embodiment of a cellular network management system 400 (referred to as "CNMS400"). CNMS400 can represent the embodiment of CNMS301 in FIG. 3. CNMS400 can include a cellular network data collection interface 405 (referred to as "interface 405"), a cellular network model creator 410 (referred to as "model creator 410"), a network event log database 412, a network usage policy database 414, a cellular network model 415, a service request processing engine 420, an access condition database 422, an external client (or entity) interface 425, and a cellular network provisioning interface 430. CNMS400 can be implemented using one or more non-transitory processor-readable media and one or more computers servers systems including one or more processors. Various components of CNMS400 can be implemented using dedicated or general-purpose processors. Such dedicated processors can include processors specifically designed to perform the functions detailed herein. Such dedicated processors can be ASICs or FPGAs, which are general-purpose components physically and electrically configured to perform the functions detailed herein. Such general-purpose processors can 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).

[0040] Interface 405 can receive status data from each component of the cellular core network and from the RAN components of the cellular network. Interface 405 can query cellular core network components for such data, or can receive such data periodically or intermittently. When status data (which can include performance data) is received, it can be passed to the cellular network modeler 410. Interface 405 can pass this data to the modeler 410, which can collect status / performance data over a period of time (e.g., seconds, minutes, hours, etc.) and create a dataset representing the current characteristics of the cellular network, including the available capacity used, packet loss, latency, jitter between nodes, available bandwidth used, available radio resources (e.g., resource blocks) used per BS and AP, etc. Over time, the cellular network modeler 410 can create a cellular network model 415 representing the performance of the cellular network over various time periods, days of the week, months, etc.

[0041] The cellular network modeler 410 can communicate with a network event log database 412. The network event log database 412 can store data indicating the types of components of the RAN and the cellular core network. The network event log database 412 can also include a map of which nodes of the core cellular network can communicate directly with each other. The network event log database 412 can also indicate the maximum bandwidth available between specific nodes of the core cellular network and the total radio resources available at specific RAN components.

[0042] The network usage policy DB 414 can define how the cellular network (or various parts of the cellular network) is permitted to be utilized. For example, radio resources may be permitted to be overbooked by a certain percentage. Overbooking of radio resources can include allocating a total amount of bandwidth that is more than what the cellular network can deliver to clients in a given area over different periods of the cellular network. This arrangement is based on the principle that it is unlikely that all clients will be utilizing the maximum amount of their client bandwidth at any given point in time. By overbooking the amount of available bandwidth, the total amount of bandwidth of the cellular network at that location and point in time can be used more efficiently. The higher the overbooking percentage, the higher the likelihood that clients will not be able to achieve the maximum amount of bandwidth as a result of the overbooking. The network usage policy DB 414 can define the maximum percentage (if any) by which overcrowding is allowed in various parts of the cellular network.

[0043] The cellular network modeler 410 can create a cellular network model 415 using data received from the cellular network data collection interface 405, the network event ride database 412, and the network usage policy DB 414. The cellular network model 415 can present an accurate snapshot of the current performance and usage of all parts of the cellular network, including those of the radio resources, along with predictions of how the cellular network will be utilized in various locations in the future based on past data. For example, the cellular network model 415 can be used to estimate the likely usage of various parts of the cellular network for future weekdays, weeknight weekdays, weekend nights, weekends, special events (such as sports events), etc.

[0044] The cellular network model creator 410 can also incorporate predictions into the cellular network model 415. For example, although past information may not indicate that a particular location on a particular day of arrival has a large amount of traffic in a particular part of the cellular network, the cellular network model 415 can be adjusted using prediction data such as prediction data input by an administrator or determined by the system. As an example of this, a festival scheduled nearby (with no past similar events at that location), a sports event schedule, or other forms of special events may be expected to cause a significant increase in cellular network usage at a particular location. In some embodiments, the cellular network model creator 410 can have access to information regarding sports team schedules, local civic events, holidays, festivals, etc.

[0045] The cellular network model 415 can be used to determine portions of the cellular network that are at approximately maximum capacity, below maximum capacity, at maximum capacity, or above maximum capacity, by using past and current cellular network performance across locations in combination with indications of actual cellular network event entries (from the network event registry DB 412). Portions of the cellular network that are above, below, or at maximum capacity can vary significantly depending on location, time, and date.

[0046] Ideally, a cellular network operator may wish to increase the overall usage of the cellular network and reduce the usage of parts of the cellular network at or beyond maximum capacity. Thus, if a client wishes to add a UE to the cellular network, the cellular network operator can attempt to encourage the client to use the cellular network at locations and / or times when the cellular network has a large available capacity. The cellular network operator can do such encouragement by adjusting the price offered to the client based on the amount of network capacity available for the location, time, and / or date of the client's request.

[0047] The external client interface 425 can serve to receive from the client a request to access the cellular network using one or more UEs. The client can submit a service request to the external client interface 425 via the Internet or the like. The service request can include various parameters required to be met by the cellular network and information about the UEs. The parameters can include the number of UEs, the location of the UEs, the maximum bandwidth (per UE or in total) required by location (for a particular server system), the maximum latency (per UE or average) by location (for a particular server system), the QoS parameters of bandwidth, packet loss, latency, and jitter that must be met, the date and time by which the service must be effective, and the date and / or time (or range of dates / times) when the service becomes effective.

[0048] The external client interface can pass the received parameters to the service request processing engine 420. The service request processing engine 420 can determine the following: 1) whether the network can meet the QoS parameters submitted by the client, and 2) under what conditions access to the cellular network should be permitted. The service request processing engine 420 can access the cellular network model 415 to determine whether the current cellular network resources are sufficient to meet the service request. If the current cellular network resources are insufficient, depending on when the service will become available, the service request processing engine 420 can determine whether it is possible to change the cellular network (e.g., by adding bandwidth, connections between nodes, etc.) before the service becomes available.

[0049] The service request processing engine 420 can access the network usage policy DB 414 to determine what changes or modifications can be made to the cellular network and how quickly. For example, some changes such as purchasing or otherwise obtaining additional bandwidth between nodes in the cellular core network may be possible almost instantaneously. Other changes such as an increase in the number of UEs or the amount of bandwidth between the BS and UEs may require a physical upgrade to the RAN and may take days, weeks, or even months to implement. Further, in some situations, an upgrade may not be possible. The network usage policy DB 414 can store indications of which connections and components are valid for upgrade and the time required to perform such an upgrade. When analyzing the service request by the service request processing engine 420, such data from the network usage policy DB 414 can be used to determine whether the service request can be satisfied and / or the access conditions to be provided to the client in response to the service request.

[0050] The service request processing engine 420 can further communicate with the access condition DB 422. The access condition DB 422 can include rules and policies used to determine how the service request processing engine 420 will respond to service requests received via the external client interface 425. Using the access condition DB 422, the price to be provided to the client in response to the service request can be determined. The service request processing engine 420 analyzes the cellular network model 415 and the network usage policy DB 414 to determine the following: 1) whether the cellular network has the current capacity to handle the service request or whether a change to the cellular network is necessary, and 2) whether the service request requires the use of low, medium, or high demand cellular network resources. The rules and policies and the access condition DB 422 can be used in combination with the decisions made by the service request processing engine 420 to determine the offered price to satisfy the service request. The offered price is a function of, among other things, demand, existing and predicted network states, location, time, opportunity cost, marginal cost, average cost, and the expected return on investment for each service request.

[0051] The service request processing engine 420 can send a response to the service request, called a cellular network access condition package. The cellular network access condition package can indicate whether the cellular network system can fulfill the service request. The cellular network access condition package can further include the cost caused by the cellular network operator for the service request to be fulfilled. The cellular network access condition package can provide the service provider with the option to accept or reject the cellular network access condition package. If accepted, the service request processing engine 420 can receive a response indicating the client's consent to the cellular network access condition package. This positive response can trigger the service request processing engine 420 to configure the cellular network to fulfill the service request. The cellular network provisioning interface 430 can be used to configure the cellular network. This can include providing the identifier of the client's UE to the relevant components of the cellular network. The cellular network provisioning interface 430 can also be used to communicate the upgrades or changes that need to be made to the cellular network to fulfill the service request. In some embodiments, changes to the cellular network, such as obtaining additional bandwidth between nodes, can be made directly by the cellular network provisioning interface 430. Additionally or alternatively, a message indicating a manual upgrade to the cellular network that needs to be performed to fulfill the service request can be sent to the administrator.

[0052] In addition to, or instead of, providing a response to a service request that indicates that the service request processing engine 420 can satisfy the service request with respect to price, the service request processing engine 420 can indicate various changes to the service request. Such changes can enable the service request to be satisfied or can enable the service request to be satisfied at a different (e.g., lower) price than otherwise. Accordingly, the cellular network access condition package can include various options that can be selected by the client. As an example, in a service request, the client may request that certain QoS parameters be satisfied between 1:00 p.m. and 5:00 p.m. The cellular network access condition package provided in the response can indicate a first price for satisfying the service request, including the certain QoS parameters. The cellular network access condition package can also include, in some cases, a lower second price that indicates that the service request is satisfied but the QoS parameters are satisfied between 3:00 p.m. and 7:00 p.m. (e.g., when there is less cellular network traffic). Depending on the response provided to the client in the cellular network access condition package, the service request processing engine 420 can appropriately configure the cellular network via the cellular network provisioning interface 430.

[0053] In addition to, or instead of, providing a cellular network access condition package that includes one or more options selected by a client, one or more options can be included. If an option is obtained by the client, the client can be enabled to obtain cellular service at a fixed price set at a maximum for a certain future time period (specified by a service request provided in response as part of the cellular network access condition package or a modified version of the service request). Thus, if it is not certain whether cellular network access will be required by the client at a certain future time, the client can decide to purchase an option for the service request. Until a certain future time, the client can exercise the option at the associated fixed price or can let the option lapse. Whether the client decides to exercise the option or let the option lapse, a fee may need to be paid to obtain the option from the cellular service provider via the service request processing engine 420. The service request processing engine 420 can determine how an option should be priced using data from the service request, the cellular network model 415, the network usage policy DB 414, and the access condition DB 422. Multiple versions of the option may be presented having different periods during which the option can be exercised.

[0054] Various methods can be performed using the various embodiments of the cellular network system and CNMS described in detail in connection with FIGS. 1-4. FIG. 5 is an embodiment of a method 500 for managing cellular network slicing. Method 500 can be performed using a system as described in detail in connection with FIGS. 1 and 2 (although it is likely to have variations in its hierarchy), as well as a CNMS as described in detail in connection with FIGS. 3 and 4. The CNMS can function as part of the cellular network system or can communicate with the cellular network (e.g., the CNMS can function outside the cellular network but may receive data regarding the cellular network).

[0055] At block 510, performance data can be obtained from some or all of the core cellular network nodes and RAN components. The performance data can be received by a CNMS that monitors the entire cellular network. The performance data can indicate how a particular cellular network component is currently performing. The performance data can indicate data such as the latency and jitter currently experienced by other nodes in the cellular network, the number of currently connected UEs, packet loss, the amount or percentage of total bandwidth utilized, total available bandwidth, the number or ratio of radio resource blocks used, etc.

[0056] In block 520, a cellular network model can be created or updated based on the received performance data. The cellular network model can reflect the load and capacity of the cellular network over time. Based on the past performance data received over time in block 510, the performance of individual cellular network components can be modeled over time. Thus, the performance of individual network components can be modeled for a specific time period, day of the week, etc. Using the model created in block 520, it is possible to predict the load present in various parts of the cellular network at different times, and which resources are likely to be available or used.

[0057] In block 530, service requests can be received from a client by the CNMS. The client can be an entity separate from the operator of the cellular network that desires access to the cellular network for a number of UEs. The service request can include data such as an indication of the UE for which the service is desired, the location where the service is to be provided to the UE, one or more QoS parameters that need to be satisfied, one or more periods during which the service is requested with the QoS parameters satisfied, and the time when the service starts, etc. Table 1 represents an example of a service request that can be transmitted by a client.

Table 1

[0058] In block 540, the service request received in block 530 can be analyzed in combination with the cellular network model created in block 520. Additionally or alternatively, the service request can be analyzed in combination with various network usage policies and access conditions. The network usage policy can specify how the network can be utilized to fulfill the service, such as the amount of permitted oversubscription. The access conditions can include various rules and policies used to determine the following: 1) whether the cellular network can fulfill the service request, and 2) how the service request should be priced, at least partially based on the data obtained from the cellular network model. Therefore, the pricing depends at least partially on the execution and utilization of the portion of the cellular network used to fulfill the service request.

[0059] In block 550, a cellular network access condition package can be created. The cellular network access condition package can indicate whether the service request can be fulfilled and can include one or more options for the client to evaluate, including deviations from the original service request received in block 530. The cellular network access condition package can include an indication of whether the service request can be fulfilled as is and the price. Table 2 provides an example of a cellular network access condition package including one alternative form.

Table 2

[0060] It should be understood that the example in Table 2 shows only one alternative form with multiple modified QoS parameters, but additional or different alternative forms with a smaller number of modified QoS parameters may be presented.

[0061] In block 570, it is possible to determine whether a response accepting the cellular network access condition package has been received. If multiple options are provided in the cellular network access condition package, the response received and analyzed in block 570 can indicate the option accepted by the client. Block 570 can include payments submitted by the client to a specific account or other location. Alternatively, in block 570, if a response rejecting all the options presented in the cellular network access condition package is received, no action may be taken in block 595. Therefore, the client's UE may not be able to access the cellular network according to any of the alternative forms presented in the cellular network access condition package.

[0062] If acceptance is received in block 570, method 500 can proceed to block 580 where one or more components of the cellular network are configured to permit access according to the accepted cellular network access condition package. Block 580 can include performing a provisioning process or some other form of configuration that enables the client's UE to access the cellular network according to the cellular network access condition package. Therefore, if the cellular network access condition package accepted by the client matches the initial service request provided by the client, the client's UE can receive access to the cellular network according to the items of the original service request. In block 590, cellular network services such as data services can be provided to the client's UE according to the accepted cellular network access condition package.

[0063] FIG. 6 is an embodiment of a method 600 for managing cellular network slicing using options for reserving cellular network capacity. The method 600 can be executed using a system as detailed in connection with FIGS. 1 and 2 (although it is highly likely to have variations in its hierarchy), as well as a CNMS as detailed in connection with FIGS. 3 and 4. The CNMS can function as part of the cellular network system or communicate with the cellular network (e.g., the CNMS may function outside the cellular network but may receive data regarding the cellular network). The method 600 can be executed as part of the method 500 or a similar method.

[0064] One or more options can be created at block 650, either as part of or separately from the cellular network access condition package created at block 550. The options can be created only if specifically requested by the client as part of the service request. The options can be created by the service request processing engine using one or more rules or policies from the access condition DB in combination with data from the cellular network model. In some embodiments, as part of the service request, the client can indicate the period for which the client desires an estimate of the options. The options presented by the service provider can be based, at least in part, on the duration indicated as part of the service request. As an example of options, Table 3 shows a cellular network access condition package of Table 2 that includes two options for each choice.

Table 3

[0065] At block 660, a cellular network access condition package (including one or more available options) can be provided to the client.

[0066] In block 670, it is possible to receive a response that can be analyzed to determine whether one of the options included in the cellular network access condition package has been accepted. In the case of "yes", all or a certain percentage of the network capacity required to implement the services indicated in the cellular network access condition package can be reserved in block 692. The reservation of network capacity can include ensuring that sufficient network capacity is available when the cellular network access condition package is defined as active. Other clients or other cellular network access condition packages provided to the same client can take into account that these network capacities have been reserved. Therefore, due to the reservation of network capacity executed in block 692, there may be a need to reject other service requests, or they may only be available at a higher price.

[0067] In block 695, it is possible to receive a response indicating that the option has been exercised within the period specified by the option. This can include the client agreeing to pay the price previously offered as part of the cellular network access condition package presented by the cellular network service provider. Next, method 600 can proceed to block 680. If the response is not received within the period specified by the option, the option can expire, and the previously reserved network capacity can no longer be reserved and can become available to other clients.

[0068] If block 670 does not include an option that has been accepted, method 600 can proceed to block 675. At block 675, it can be determined whether a response has been received to accept the cellular network access condition package. If multiple alternative forms are provided in the cellular network access condition package, the response received and analyzed at block 670 can indicate the option selected by the client. Block 675 can include a payment submitted by the client to a specific account or other location. Alternatively, at block 675, if a response is received that rejects all of the options presented in the cellular network access condition package, no action may be taken at block 697. Thus, the client's UE may not be able to access the cellular network according to any of the alternative forms presented in the cellular network access condition package.

[0069] If acceptance is received at block 670, method 600 can proceed to block 680 where one or more components of the cellular network are configured to permit access according to the accepted cellular network access condition package. Block 680 can include performing a provisioning process or some other form of configuration that enables the client's UE to access the cellular network according to the cellular network access condition package. Thus, if the cellular network access condition package accepted by the client matches the initial service request provided by the client, the client's UE can receive access to the cellular network according to the items of the original service request. At block 690, cellular network services such as data services can be provided to the client's UE according to the accepted cellular network access condition package.

[0070] FIG. 7 is an embodiment of a method for client-side management of reserving cellular network capacity. Method 700 can be executed using a system as detailed in relation to FIGS. 1 and 2 (however, it is highly likely to have variations in its hierarchy), as well as a CNMS as detailed in relation to FIGS. 3 and 4. Method 700 can further be executed at least in part by a client's system communicating with an external client interface of the CNMS. For example, the blocks of method 700 can be executed using client system 310. The CNMS can function as part of a cellular network system or can communicate with the cellular network (for example, the CNMS may function outside the cellular network but may receive data regarding the cellular network). Method 700 can be executed as part of method 500 or a similar method.

[0071] In block 710, a service request can be created using the client system. The service request can be created by the client system based on rules and policies previously created by the client's administrator. Thus, the service request can be created without the intervention of the administrator. For example, when the client system determines that additional wireless capabilities are required, it can automatically create a service request based on previously established rules and policies. The service request created in block 710 can be similar to the exemplary service requests in Table 1. As part of block 710, the service request can also be sent to the cellular network service provider for evaluation.

[0072] In response to the sent service request, a cellular network access condition package can be received in the response from the cellular network service provider at block 720. The cellular network access condition package can be created using the CNMS according to method 500. In response to the cellular network access condition package, the requirements of the service request can be changed. For example, when evaluating the cellular network access condition package by the client system, it can be determined that one or more parameters of the cellular network access condition package are unacceptable. For example, the requested change to the QoS parameter may be unacceptable to the client. As another example, the price indicated in the cellular network access condition package may be excessively high. At block 730, the service request can be revised to change the period during which the QoS parameter needs to be realized, the details of the QoS parameter, the location where the UE will connect to the cellular network, and / or the number of UEs receiving the service via the cellular network. Alternatively, the service request can be changed to meet the conditions of the cellular network access condition package received at block 720. For example, while the initial service request is being invoked for a particular QoS parameter to be satisfied, the functionality of the client's system can be adjusted to adapt to the changed QoS parameter. (For example, on the client side, the resolution of the streaming video can be reduced to adapt to the fact that the cellular service provider cannot achieve the bandwidth requested in the original service request.)

[0073] In block 740, it is possible to select a service request revised according to the cellular network access condition package, or submit the revised service request to the CNMS. If the revised service request is submitted to the CNMS, method 700 can return to block 710. If the service request is revised to match the cellular network access condition package received in block 720, the cellular network access condition package can be selected and method 700 can proceed to block 750. In block 750, it is possible to send the acceptance of the cellular network access condition package to the CNMS. In block 760, the client's UE can use the cellular network according to the accepted cellular network access condition package.

[0074] The methods, systems, and devices discussed above are examples. Various configurations may appropriately omit, substitute, or add various procedures or components. For example, in an alternative configuration, the method may be executed in a different order than described, and / or various stages may be added, omitted, and / or combined. Also, features described with respect to a particular configuration may be combined in various other configurations. Different aspects and elements of the configurations may be combined as well. Also, technology evolves, and thus many of the elements are examples and do not limit the scope of the disclosure or the claims.

[0075] Specific details are set forth in this specification in order to provide a thorough understanding of the exemplary configurations (including implementations). However, the configurations may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques are shown without unnecessary detail to avoid obscuring the configurations. This specification provides only exemplary configurations and does not limit the scope of the claims, applicability, or configurations. Rather, the above description of the configurations provides an implementation description for those skilled in the art to implement the techniques described above. Various changes may be made to the functions and configurations of the elements without departing from the spirit or scope of the present disclosure.

[0076] Also, the configuration may be described as a process illustrated as a flowchart or block diagram. Each may describe operations as sequential processes, but many of the operations may be executed in parallel or simultaneously. Additionally, the order of operations may be rearranged. The process may have additional steps not included in the figures. Further, embodiments of the method may be implemented by hardware, software, firmware, middleware, microcode, a hardware description language, or a combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments for performing the necessary tasks may be stored in a non-transitory computer-readable medium such as a storage medium. A processor may execute the above-described tasks.

[0077] Although some exemplary configurations have been described, various modifications, alternative structures, and equivalents may be used without departing from the spirit of the present disclosure. For example, the elements described above may be components of a larger system, where other rules may take precedence over the application of the present invention, or the application of the present invention may be modified otherwise. Also, many steps may be executed before, between, or after the elements described above are considered.

Claims

1. A method for managing a cellular network, the method comprising: obtaining performance data from a plurality of cellular network components of the cellular network over time by a cellular network management system, wherein the plurality of cellular network components includes a radio access network (RAN) component and a cellular network data center of the core cellular network; analyzing the performance data from the plurality of cellular network components by the cellular network management system to create a cellular network model indicative of the performance of the cellular network over time; receiving, by the cellular network management system, a service request from an external entity separate from the cellular network and the entity operating the cellular network management system, wherein the service request defines a plurality of quality of service (QoS) parameters requested by the external entity; analyzing the cellular network model by the cellular network management system to determine whether the cellular network has sufficient available resources to meet the plurality of QoS parameters of the service request; creating, by the cellular network management system, a cellular network access condition package, wherein the cellular network access condition package defines one or more conditions for the external entity to be eligible to use the cellular network; wherein the cellular network access condition package includes a first set of modified QoS parameters different from the QoS parameters of the service request; wherein the cellular network access condition package further includes a second set of QoS parameters that match the QoS parameters of the service request; transmitting, by the cellular network management system, the cellular network access condition package to the external entity; receiving, by the cellular network management system, acceptance of the cellular network access condition package from the external entity; The cellular network management system configures at least some of the plurality of cellular network components to permit access to the cellular network by a user equipment (UE) of the external entity according to the cellular network access condition package; The cellular network provides a data service to the UE of the external entity according to the cellular network access condition package; A method comprising the steps of. **Claim 2** The method for managing a cellular network according to claim 1, wherein the plurality of QoS parameters includes an indication of a location where the QoS parameters will be satisfied. **Claim 3** The method for managing a cellular network according to claim 2, wherein the performance data obtained from the plurality of cellular network components of the cellular network includes wireless congestion data of the location where the QoS parameters will be satisfied. **Claim 4** The method for managing a cellular network according to claim 1, wherein the cellular network access condition package includes matching QoS parameters that exactly match the QoS parameters of the service request. **Claim 5** The method for managing a cellular network according to claim 1, wherein the QoS parameters of the service request include a period defining when it is required that the QoS parameters be realized. **Claim 6** The method for managing a cellular network according to claim 1, wherein the cellular network access condition package further includes a first price mapped to a first set of the QoS parameters and a second price mapped to a second set of the QoS parameters. **Claim 7** The method for managing a cellular network according to claim 1, wherein the cellular network access condition package indicates a price. **Claim 8** A cellular network management system, comprising: A communication interface for communicating with a plurality of cellular network components of a cellular network; One or more processors communicating with the communication interface; A memory storing instructions which, when executed by the processor, Acquire performance data from the plurality of cellular network components of the cellular network over time via the communication interface, Analyze the performance data from the plurality of cellular network components to create a cellular network model indicative of the performance of the cellular network over time, Receive a service request from an external entity separate from the entity operating the cellular network and the cellular network management system, The service request defines a plurality of quality of service (QoS) parameters requested by the external entity, Analyze the cellular network model to determine whether the cellular network has sufficient available resources to meet the plurality of QoS parameters of the service request, Create a cellular network access condition package, The cellular network access condition package defines one or more conditions for the external entity to be eligible to use the cellular network, The cellular network access condition package includes a first set of modified QoS parameters different from the QoS parameters of the service request, The cellular network access condition package further includes a second set of QoS parameters that match the QoS parameters of the service request, Transmit the cellular network access condition package to the external entity, Receive acceptance of the cellular network access condition package from the external entity, Compose at least some of the plurality of cellular network components to permit access to the cellular network by a user equipment (UE) of the external entity according to the cellular network access condition package, A memory configured to, A cellular network management system comprising.

9. The cellular network management system according to claim 8, wherein the plurality of QoS parameters include an indication of a location where the QoS parameters will be met.

10. The cellular network management system according to claim 9, wherein the performance data obtained from the plurality of cellular network components of the cellular network includes wireless congestion data of the location where the QoS parameters will be satisfied.

11. The cellular network management system according to claim 8, wherein the cellular network access condition package includes matching QoS parameters that exactly match the QoS parameters of the service request.

12. The cellular network management system according to claim 8, wherein the QoS parameters of the service request include a period defining when it is required that the QoS parameters be realized.

13. The cellular network management system according to claim 8, wherein the cellular network access condition package further includes a first price mapped to a first set of the QoS parameters and a second price mapped to a second set of the QoS parameters.

14. The cellular network management system according to claim 8, wherein the cellular network access condition package indicates a price.

15. A non-transitory computer-readable storage medium, the non-transitory computer-readable storage medium includes instructions that, when executed by a computer, cause the computer to acquire performance data from a plurality of cellular network components of a cellular network over time, the plurality of cellular network components include a radio access network (RAN) component and a cellular network data center of a core cellular network, analyze the performance data from the plurality of cellular network components to create a cellular network model indicating the performance of the cellular network over time, receive a service request from an external entity separate from the entity operating the cellular network and the cellular network management system, the service request defines a plurality of quality of service (QoS) parameters requested by the external entity, analyze the cellular network model to determine whether the cellular network has sufficient available resources to satisfy the plurality of QoS parameters of the service request. Create a cellular network access condition package, The cellular network access condition package defines one or more conditions for the external entity to be eligible to use the cellular network, The cellular network access condition package includes a first set of modified QoS parameters different from the QoS parameters of the service request, The cellular network access condition package further includes a second set of QoS parameters that match the QoS parameters of the service request, Cause the cellular network access condition package to be sent to the external entity, Receive acceptance of the cellular network access condition package from the external entity, A non-transitory computer-readable storage medium that configures at least some of the plurality of cellular network components to permit access to the cellular network by a user equipment (UE) of the external entity in accordance with the cellular network access condition package.

16. The plurality of QoS parameters include an indication of a location where the QoS parameters will be satisfied, The non-transitory computer-readable storage medium according to claim 15, wherein the performance data obtained from the plurality of cellular network components of the cellular network includes wireless congestion data of the location where the QoS parameters will be satisfied.

Images