SYSTEMS AND METHODS FOR DETERMINING RELIABILITY OF CHANNEL QUALITY MEASUREMENTS PROVIDED BY USER EQUIPMENT

A system described herein may output, during a particular time window (e.g., in a simulation environment), a series of wireless transmissions to one or more User Equipment (“UEs”) of a particular type. The series of wireless transmissions may include first set of transmissions associated with a first set of parameters and a second set of transmissions associated with a second set of parameters. The system may receive channel quality measurements from the one or more UEs, and may identify a measure of variance between the channel quality measurements from the one or more UEs. The system may generate a reliability score associated with the particular type of UE based on the identified measure of variance, and may output, to a wireless network, the reliability score associated with the particular type of UE. The wireless network may communicate with UEs of the particular type based on the reliability score.

BACKGROUND

Wireless networks provide wireless connectivity to User Equipment (“UEs”), such as mobile telephones, tablets, Internet of Things (“IoT”) devices, Machine-to-Machine (“M2M”) devices, or the like. Networks may provide wireless coverage according to multiple frequency bands. Some wireless networks may offer Multiple-Input Multiple-Output (“MIMO”) connectivity, in which a given band is implemented by multiple antennas or other types of wireless network infrastructure. Networks may implement MIMO configurations or perform other operations based on UE-reported channel quality measurements.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Networks may implement MIMO configurations or perform other operations based on UE-reported channel quality metrics. Such channel quality metrics may include, for example, Channel Quality Indicator (“CQI”) values, Rank Indicator (“RI”) values, Precoding Matrix Indicator (“PMI”) values, and/or other types of information that indicate quality, strength, etc. of radio frequency (“RF”) signals as transmitted by the network and as received by UEs. For example, if channel quality metrics (e.g., RI values, PMI values, etc.) reported by a set of UEs are above one or more thresholds, the network may implement a MIMO configuration for transmissions to the UEs. If, on the other hand, channel quality metrics reported by a set of UEs are below the one or more thresholds, the network may forgo implementing a MIMO configuration for transmissions to the UEs, and/or may implement a different MIMO configuration than if the channel quality metrics were above the one or more thresholds. As such, the channel quality metrics reported by UEs may play a vital role in the operation of a wireless network.

Situations may arise in which a UE does not accurately report channel quality metrics such as RI values, which may potentially interfere with the operation of a wireless network such as by causing the wireless network to lower its rank assignment, which may cause a loss of network capacity. For example, particular makes, models, etc. of UEs may be misconfigured by a manufacturer or vendor, and/or may otherwise exhibit issues that prevent the accurate determination or reporting of channel quality metrics. Embodiments described herein provide for techniques that identify a measure of reliability with respect to types, groups, etc. of UEs. The measures of reliability may be used to, for example, certify or approve a type of device for use with a wireless network, provide an alert or notification to a manufacturer or vendor of a particular type of UE that the reliability of channel quality measurements by the type of UE is below a threshold measure of reliability, and/or other suitable operations.

As shown inFIG.1, UE-reported Channel Quality Reliability Testing System (“UCQRTS”)101may cause a series of downlink transmissions to be sent to various UEs103. For example, such transmissions may be sent via one or more base stations, antennas, or other suitable wireless network infrastructure equipment. In some embodiments, the transmissions may be simulated and/or otherwise made in a controlled or testing environment. For example, the one or more base stations, antennas, etc. may be simulated, and the transmissions to UEs103may be simulated. In some embodiments, UEs103may be physical UEs, and/or may be implemented in a simulated environment. Thus, in some embodiments, UEs103and/or the wireless network infrastructure equipment that outputs transmissions to UEs103may be simulated.

In view of the foregoing, operations described below with respect to the transmitting or receiving of RF signals, and/or the determining or reporting of channel quality metrics, may refer to operations that occur in a simulated environment. On the other hand, in some embodiments, the transmitting or receiving of RF signals, and/or the determining or reporting of channel quality metrics, may refer to operations that occur in a real-world environment with physical wireless network infrastructure equipment and/or physical UEs103.

As shown, UCQRTS101may output a series of downlink transmissions to various different UEs103. The different UEs103may include different types of UEs (referred to as “Type 1,” “Type 2,” and “Type 3”). The different “types” of UEs may refer to different makes and/or models of UEs, UEs with different hardware configurations (e.g., different types or quantities of antennas or other wireless hardware, different battery capacities, different housing materials, etc.), different operating systems, different carrier settings, different classifications or categories (e.g., “first responder,” “high data demand,” “low data demand,” etc.), or other identifiable and/or distinguishing attributes. The series of downlink transmissions may be sent via a set of wireless network infrastructure equipment, such as one or more antennas. In some embodiments, the wireless network infrastructure equipment may implement one or more MIMO configurations, in which multiple antennas are used to implement a single channel or layer.

As discussed above, the transmissions may be sent by real-world, physical wireless network infrastructure equipment to physical UEs103. In such scenarios, UCQRTS101may be communicatively coupled to a controller (e.g., a RAN controller) that causes the downlink transmissions to be wirelessly transmitted by the wireless network infrastructure equipment. In some embodiments, as also noted above, the transmissions may be simulated. For example, UCQRTS101may execute one or more simulations in which transmissions from wireless network infrastructure equipment to UEs103is simulated. In such scenarios, the wireless network infrastructure equipment and/or UEs103may also be simulated, modeled, etc. by UCQRTS101.

The series of downlink transmissions, sent to each UE103, may be sent under varying conditions (e.g., simulated conditions) and/or parameters. For example, as discussed below, the downlink transmissions may be sent under varying amounts of downlink radio resource allocations in the time and/or frequency domains (e.g., downlink grants), may be sent with different levels of throughput, different downlink scheduling rates, and/or may have other varying attributes or parameters.

In some embodiments, the downlink transmissions sent to a particular UE103may include a first set of downlink transmissions under a first set of downlink radio resource allocations (e.g., the particular UE103may be granted a relatively large amount of RF resources in the time and/or frequency domains, such as a relatively large quantity of resource elements (“REs”) in the time domain, a relatively large quantity of REs in the frequency domain, and/or a relatively large quantity of REs in both the time and frequency domains). Further, downlink transmissions sent to the particular UE103may include a second set of downlink transmissions under a second set of downlink radio resource allocations, in which UE103may be granted a relatively small (e.g., lesser than the first set) quantity of REs in the time domain, a relatively small quantity of REs in the frequency domain, and/or a relatively small quantity of REs in both the time and frequency domains. When sending the transmissions to such UE103under varying RF resources allocations (e.g., when sending the first and second sets of downlink transmissions), UCQRTS101may keep other parameters or factors constant. For example, the location of UE103may be kept constant (or within a threshold level of minor variation), the transmit power of the wireless network infrastructure equipment may be kept constant (or within a threshold level of minor variation), and/or other factors that could otherwise potentially affect signal or channel quality may be kept constant (or within a threshold level of minor variation). In this manner, the only substantial variation in the attributes of the wireless network infrastructure equipment and/or UE103may be the differences in the amounts of resources allocated to UE103.

As another example, the downlink transmissions may include varying levels of throughput of traffic sent to UE103. For example, a first set of downlink transmissions may be sent to UE103with a relatively high throughput (e.g., a relatively large amount of traffic may be transmitted to UE103within a given timeframe), while a second set of downlink transmissions may be sent to UE103with a relatively low (e.g., lesser than the first set) throughput. As similarly noted above, when sending the downlink transmissions to UE103with the varying levels of throughput, UCQRTS101may keep other configuration parameters or attributes constant, such that only the varying levels of throughput of traffic sent to UE103changes. For example, UCQRTS101may keep an downlink radio resource allocation, for UE103, constant while sending traffic with varying levels of throughput to UE103. In this manner, the only substantial variation in the attributes of the wireless network infrastructure equipment and/or UE103may be the differences in the throughput of downlink traffic sent UE103.

As further shown, each UE103may provide, on a periodic or otherwise ongoing basis, channel quality measurements under the varying conditions. For example, UE103may generate and/or output CQI values, RI values, PMI values, and/or other types of information that indicate quality, strength, etc. of radio frequency RF signals as transmitted by the network and as received by UE103. UE103may output (or simulate outputting) the channel quality measurements to or via the wireless network infrastructure equipment from which the downlink transmissions were received. In some embodiments, the channel quality measurements may be included in measurement reports or other suitable messages from UEs103. The timing of the channel quality measurements may be used to associate particular channel quality measurements with parameters of the downlink transmissions sent to UE103.

For example, during a first time window (e.g., a 15-second time window, a 30-second time window, a 10-minute time window, etc.), UCQRTS101may output downlink transmissions to UE103under a first set of parameters (e.g., relatively high downlink radio resource allocation, relatively low downlink radio resource allocation, relatively high throughput, relatively low throughput, etc.). During the first time window, UCQRTS101may identify that channel quality measurements sent by UE103are associated with the first set of parameters. Similarly, during a second time window, UCQRTS101may output downlink transmissions to UE103under a second set of parameters and may identify that channel quality measurements sent by UE103, during the second time window, are associated with the second set of parameters. In this manner, UCQRTS101may associate particular channel quality measurements, as generated by or received from UEs103, with particular sets of parameters or conditions under which the channel quality measurements were generated.

As shown, UCQRTS101may send downlink transmissions, under varying sets of conditions or parameters, to different types of UEs103, such as UE103-1(e.g., a Type 1 UE), UE103-2(e.g., a Type 2 UE), UE103-3(e.g., a Type 3 UE), etc. In some embodiments, UCQRTS101may send the downlink transmissions to one particular UE of each type (e.g., one instance of UE103-1, one instance of UE103-2, and/or one instance of UE103-3). In some embodiments, UCQRTS101may send the downlink transmissions to multiple UEs of each type (e.g., multiple instances of UE103-1, multiple instances of UE103-2, multiple instances of UE103-3, etc.).

UCQRTS101may also receive channel quality measurements from UEs103-1,103-2,103-3, etc. As discussed above, UCQRTS101may associate particular channel quality measurements, received from each particular UE103, to conditions or parameters under which downlink transmissions were sent to each particular UE103. In this manner, UCQRTS101may receive or maintain channel quality measurements, that are associated with varying conditions or parameters of downlink transmissions, from multiple different types of UEs103.

UCQRTS101may further determine, for each UE type, a measure of variance in the received channel quality measurements in the varying conditions. For example, for a given UE type, UCQRTS101may compare the channel quality measurements, provided by one or more UEs103of such UE type, as provided under different conditions or parameters of the downlink transmissions. UCQRTS101may further generate one or more scores, metrics, etc. (referred to herein as “reliability scores”) for each UE type based on the measure of variance in the received channel quality measurements in the varying conditions. Generally, when the channel quality measurements for a particular UE type exhibit a relatively low (or no) variance under varying conditions or parameters of downlink transmissions, then the particular UE type may be associated with a relatively high measure of reliability with respect to channel quality measurements received by the UE type (e.g., a relatively high reliability score). On the other hand, when the channel quality measurements for a particular UE type exhibit a relatively high (e.g., above a threshold) variance under varying conditions or parameters of downlink transmissions, then the particular UE type may be associated with a relatively low measure of reliability with respect to channel quality measurements received by the UE type (e.g., a relatively low reliability score). That is, the differences in the conditions or parameters of the downlink transmissions would be expected to cause little or no variance in the channel quality measurements from UEs103.

In some embodiments, one or more other factors may be used in determining the reliability of channel quality measurements from UEs103. For example, in addition to, or in lieu of the variance of channel quality measurements under differing conditions, the reliability of channel quality measurements from UEs103may be determined based on a variance or difference from “known” or “expected” channel quality measurements. For example, even in situations where channel quality measurements from a given UE type exhibit little or no variance from each other, the UE type may still be determined as having a relatively low measure of reliability of the channel quality measurements substantially vary (e.g., by at least a threshold amount or proportion) from a known or expected measure of channel quality under certain conditions.

As one example, assuming that a particular UE type exhibits relatively low variability between channel quality measurements determined under a particular downlink radio resource allocation parameter (e.g., low, medium, high, a sequence or series thereof, etc.), the reliability score for the UE type may still be relatively low if such channel quality measurements substantially differ from a known or expected set of channel quality measurements under the particular downlink radio resource allocation parameter. As another example, assuming that a particular UE type exhibits relatively low variability between channel quality measurements determined under a particular downlink transmission throughput parameter (e.g., low, medium, high, a sequence or series thereof, etc.), the reliability score for the UE type may still be relatively low if such channel quality measurements substantially differ from a known or expected set of channel quality measurements under the particular downlink transmission throughput parameter.

In situations where a given UE type reports varying channel quality measurements under the conditions or parameters of the downlink transmissions provided by UCQRTS101(e.g., different channel quality measurements when downlink radio resource allocations are high versus when downlink radio resource allocations are low, different channel quality measurements when measures of throughput are high versus when measures of throughput are low, etc.), such UE type may be determined as being relatively unreliable, and remedial measures may be taken with respect to such UE type.

For example, as discussed above, a vendor, manufacturer, etc. of the particular UE type may be alerted, such that the UE type may be adjusted, redesigned, corrected, or otherwise modified to provide expected results (e.g., little or no variance in reported channel quality measurements under the conditions described above). As another example, a wireless network may be configured to rely less heavily on channel quality measurements from such UE type when operating the network, configurating the network (e.g., configuring MIMO parameters, configuring beamforming parameters, etc.).

FIG.2illustrates an example of varying an downlink radio resource allocation associated with a particular UE type. As shown, for example, a set of wireless network infrastructure equipment (e.g., MIMO antennas201) may output a first set of downlink transmissions to a particular UE103, a second set of downlink transmissions, and a third set of downlink transmissions. In some embodiments, while sending the first set of transmissions to UE103, MIMO antennas201may allocate (e.g., grant) a relatively low amount of RF resources for UE103. For example, a Physical Downlink Shared Channel (“PDSCH”) allocated for UE103may have a relatively small amount of RF resources (e.g., REs). As discussed above, the relatively small amount of RF resources may be a relatively small quantity of REs in the time domain, the frequency domain, or both. While sending the first set of transmissions to UE103, MIMO antennas201may allocate a medium amount of RF resources for UE103(e.g., more REs than were granted for the first set of transmissions). While sending the first set of transmissions to UE103, MIMO antennas201may allocate a relatively high amount of RF resources for UE103(e.g., more REs than were granted for the second set of transmissions).

WhileFIG.2illustrates three sets of downlink transmissions, in some embodiments, additional or fewer sets of downlink transmissions may be used. Further, in some embodiments, one set of downlink transmissions may be associated with a relatively low quantity of REs in the time domain, while another set of downlink transmissions may be associated with a relatively low quantity of REs in the frequency domain. For example, one set of downlink transmissions may include multiple REs associated with different frequencies and one time slot, while another set of downlink transmissions may include multiple REs associated with different time slots and one frequency. As another example, one set of downlink transmissions may include multiple REs associated with a first set of frequencies and a first set of time slots, while another set of downlink transmissions may include multiple REs associated with a second set of frequencies and a second set of time slots.

Further, in some embodiments, MIMO antennas201may output transmissions to UE103under varying sequences of downlink radio resource allocations. The sequence may be random, may be manually determined, may be determined via artificial intelligence/machine learning (“AI/ML”) techniques or other automated techniques, etc. For example, the sequence may include allocating a relatively small amount of RF resources (e.g., REs) in the time domain and a relatively large amount of REs in the frequency domain, then subsequently allocating a relatively large amount of REs in the time and frequency domains, then subsequently allocating a medium amount of REs in the time domain and a relatively small amount of REs in the frequency domain, etc. As noted above, these variations are not expected to cause substantial variations in the channel quality metrics reported by UE103under such varying conditions.

FIGS.3A and3Billustrate example data structures301and303, which may reflect different scenarios (e.g., which may be associated with different UE types) based on varying downlink radio resource allocations. As shown, data structures301and303include measures of UE-reported channel quality associated with each of a different set of varying network parameters (e.g., downlink radio resource allocations). Data structure301may, for example, be associated with one particular UE type while data structure303is associated with a different UE type. While data structures301and303reflect three example varying conditions (e.g., high, medium, and low resource allocations), in practice similar data structures may reflect different sets or sequences of varying conditions, as referred to above.

Data structures301and303depict channel quality metrics as “high,” “medium,” and “low” for the sake of explanation. In practice, the channel quality metrics may be indicated as raw measured or reported values (e.g., CQI values, RI values, PMI values, etc.). Additionally, or alternatively, in practice, the channel quality metric may be indicated as a score or other value that is derived from one or more channel quality measurements reported by particular UE types.

In the example ofFIG.3A, a particular UE type may indicate a relatively high channel quality when under the varying downlink radio resource allocations of downlink transmissions to the particular UE type. That is, the particular UE type may indicate the same, or approximately the same (e.g., with relatively low measure of variance), measure of channel quality under high, medium, and low downlink radio resource allocations. As discussed above, this relatively low measure of variance may indicate that this type of UE is relatively reliable with respect to channel quality measurements provided by this type of UE. Accordingly, based on the information depicted in data structure301, UCQRTS101may determine that a corresponding UE type has a relatively high reliability score.

On the other hand, in the example ofFIG.3B, another UE type may indicate differing levels of channel quality under the varying downlink radio resource allocations of downlink transmissions to this UE type. As these channel quality metrics vary by a relatively high amount (e.g., greater than a threshold level of variance or difference), the corresponding UE type may be determined by UCQRTS101as relatively unreliable (e.g., associated with a relatively low reliability score).

FIG.4illustrates an example of determining a reliability score for a particular UE type based on channel quality metrics received from the particular UE type under differing measures of downlink throughput (e.g., differing measures of throughput of traffic sent to one or more UEs103of the particular UE type via wireless network infrastructure equipment such as MIMO antennas201). As shown, UE103may receive, from MIMO antennas201, various sets of downlink transmissions. The sets of downlink transmissions may be sent with varying measures of throughput (e.g., referred to as low, medium, and high). As similarly noted above, the various sets of downlink transmissions may be sent in different sequences, which may be randomized, determined via AI/ML techniques, etc. Further, while three example sets of downlink transmissions are shown in the figure, in practice, UE103may receive additional sets of downlink transmissions with additional different measures of downlink throughput.

UCQRTS101may receive channel quality metrics from UE103(e.g., as measured or otherwise determined by UE103), and may determine a reliability score for UE103based on a measure of variance, difference, variability, etc. between the channel quality metrics. As discussed above, the different measures of downlink throughput of transmissions sent to UE103may not be expected to cause any substantial difference in the channel quality metrics determined by UE103. As such, UE103(e.g., the particular type of UE103) may be associated with a relatively high reliability score when the channel quality metrics do not vary (or vary less than a threshold amount) for the varying throughputs of downlink transmissions to UE103, while UE103may be associated with a relatively low reliability score when such metrics vary (or vary more than the threshold amount).

In some embodiments, as shown inFIG.5, UCQRTS101may generate multiple reliability scores for UE103based on different types of variations of network conditions or parameters. For example, as shown, UCQRTS101may determine a first reliability score for a given UE type based on a measure of variance in a first set of channel quality metrics reported by one or more UEs103of the given UE type under varying downlink radio resource allocations, and may determine a second reliability score for the UE type based on a measure of variance in a second set of channel quality metrics reported by one or more UEs103of the given UE type under varying throughputs of downlink transmissions to such UEs103of the given UE type.

In some embodiments, UCQRTS101may determine an overall reliability score for the UE type based on the first and second reliability scores, and/or based on other factors. In some embodiments, UCQRTS101may average the first and second reliability scores, may use the highest or the lowest score out of the first and second reliability scores as the overall reliability score, may more heavily weight the first or second reliability score when determining the overall reliability score, and/or may otherwise determine the overall reliability score based on the first and second reliability scores.

In some embodiments, a particular network601may receive the reliability scores, as generated by UCQRTS101, for one or more UE types. Network601may utilize the reliability scores when communicating with one or more UEs103. For example, during an actual “run time” operation of network601and UE103, network601may identify a type of UE103(e.g., based on information stored in a UE repository such as a Unified Data Management function (“UDM”), Unified Data Repository (“UDR”), etc.) and may utilize the reliability score associated with the type of UE103when coming with UE103. For example, if the type of UE103is associated with a relatively low reliability score, network601may not take channel quality measurements from UE103into account when determining whether to implement MIMO for transmissions to UE103, and/or may otherwise less heavily weight or consider channel quality measurements from UE103when configuring parameters of network601. Network601may include, for example, one or more RANs that are implemented by wireless network infrastructure equipment such as base stations, radios, antennas, MIMO antennas, etc., the configuration or operation of which may be modified based on whether channel quality measurements from UEs103are reliable or not (e.g., based on reliability scores determined in accordance with some embodiments).

Further, as discussed above, one or more other devices, systems, or entities may receive the reliability scores from UCQRTS101. For example, a manufacturer associated with a particular UE type may receive reliability scores associated with the UE type, and may perform further configuring, testing, development, etc. of the UE type in order to increase the reliability scores associated with the UE type.

FIG.7illustrates an example process700for determining a measure of reliability of channel quality measurements associated with a particular UE type. In some embodiments, some or all of process700may be performed by UCQRTS101(e.g., in a simulated environment, in which wireless network infrastructure equipment, one or more UEs103, and/or transmissions between the wireless network infrastructure equipment and UEs103are simulated). In some embodiments, one or more other devices may perform some or all of process700in concert with, and/or in lieu of, UCQRTS101.

As shown, process700may include outputting (at702) a series of transmissions to one or more UEs103of a particular type. The series of transmissions may include transmissions with variations on a particular parameter. For example, as discussed above, the series of transmissions may include a first set of transmissions with a first RF allocation parameter (e.g., a first set of RF resources allocated to UE103by the wireless network infrastructure equipment), and a second set of transmissions with a second RF allocation parameter. As another example, the series of transmissions may include a first set of transmissions with a first throughput parameter, and a second set of transmissions with a second throughput parameter.

Process700may further include receiving (at704) UE-generated channel quality measurements associated with the series of transmissions. For example, as discussed above, the series of transmissions may include transmissions associated with particular times or time windows, and the UE-generated channel quality measurements may be received within such time windows and/or otherwise in a manner based on which it may be determined as to which transmission parameters are associated with which UE-generated channel quality measurements. For example, one set of UE-generated channel quality measurements may be associated with a first series of transmissions associated with varying RF allocation parameters, while another set of UE-generated channel quality measurements may be associated with a second series of transmissions associated with varying throughput parameters. As discussed above, the UE-generated channel quality measurements may include CQI values, RI values, PMI values, and/or other suitable channel or signal quality measurements.

Process700may additionally include identifying (at706) one or more measures of variance between the received channel quality measurements. For example, UCQRTS101may identify a percentage, proportion, or other suitable measure of variance in the UE-generated channel quality measurements. In some embodiments, UCQRTS101may determine a first measure of variance associated with UE-generated channel quality measurements based on variations in a first parameter (e.g., RF allocation parameters) and may determine a second measure of variance associated with UE-generated channel quality measurements based on variations in a second parameter (e.g., throughput parameters).

Process700may also include generating (at708) a reliability score for the UE type based on the identified measure(s) of variance. For example, UCQRTS101may determine whether the received channel quality measurements vary by a particular threshold (e.g., a particular percentage, a particular proportion, and/or some other suitable measure of variation). In some embodiments, UCQRTS101may generate different scores based on channel quality measurements that are associated with variations on different transmission parameters (e.g., a first score based on a variation in UE-generated channel quality measurements based on varying RF allocation parameters and a second score based on a variation in UE-generated channel quality measurements based on varying throughput parameters). In some embodiments, UCQRTS101may generate an overall reliability score for the UE type by averaging, aggregating, or otherwise combining multiple scores.

Process700may further include outputting (at710) the reliability score for the particular type of UE103. For example, UCQRTS101may output the reliability score for the particular type of UE103to network601, which may modify network parameters based on the reliability score, as discussed above. Additionally, or alternatively, UCQRTS101may output the reliability score to one or more other devices, systems, or entities, which may modify parameters, attributes, characteristics, etc. of UEs103of the particular type, in order to refine or improve the reliability scores of such UEs103.

FIG.8illustrates an example environment800, in which one or more embodiments may be implemented. In some embodiments, environment800may correspond to a Fifth Generation (“5G”) network, and/or may include elements of a 5G network. In some embodiments, environment800may correspond to a 5G Non-Standalone (“NSA”) architecture, in which a 5G radio access technology (“RAT”) may be used in conjunction with one or more other RATs (e.g., a Long-Term Evolution (“LTE”) RAT), and/or in which elements of a 5G core network may be implemented by, may be communicatively coupled with, and/or may include elements of another type of core network (e.g., an evolved packet core (“EPC”)). In some embodiments, portions of environment800may represent or may include a 5G core (“5GC”). As shown, environment800may include UE103, RAN810(which may include one or more Next Generation Node Bs (“gNBs”)811), RAN812(which may include one or more evolved Node Bs (“eNBs”)813), and various network functions such as Access and Mobility Management Function (“AMF”)815, Mobility Management Entity (“MME”)816, Serving Gateway (“SGW”)817, Session Management Function (“SMF”)/Packet Data Network (“PDN”) Gateway (“PGW”)-Control plane function (“PGW-C”)820, Policy Control Function (“PCF”)/Policy Charging and Rules Function (“PCRF”)825, Application Function (“AF”)830, User Plane Function (“UPF”)/PGW-User plane function (“PGW-U”)835, Unified Data Management (“UDM”)/Home Subscriber Server (“HSS”)840, and Authentication Server Function (“AUSF”)845. Environment800may also include one or more networks, such as Data Network (“DN”)850. Environment800may include one or more additional devices or systems communicatively coupled to one or more networks (e.g., DN850), such as UCQRTS101.

The example shown inFIG.8illustrates one instance of each network component or function (e.g., one instance of SMF/PGW-C820, PCF/PCRF825, UPF/PGW-U835, UDM/HSS840, and/or AUSF845). In practice, environment800may include multiple instances of such components or functions. For example, in some embodiments, environment800may include multiple “slices” of a core network, where each slice includes a discrete and/or logical set of network functions (e.g., one slice may include a first instance of AMF815, SMF/PGW-C820, PCF/PCRF825, and/or UPF/PGW-U835, while another slice may include a second instance of AMF815, SMF/PGW-C820, PCF/PCRF825, and/or UPF/PGW-U835). The different slices may provide differentiated levels of service, such as service in accordance with different Quality of Service (“QoS”) parameters.

The quantity of devices and/or networks, illustrated inFIG.8, is provided for explanatory purposes only. In practice, environment800may include additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than illustrated inFIG.8. For example, while not shown, environment800may include devices that facilitate or enable communication between various components shown in environment800, such as routers, modems, gateways, switches, hubs, etc. In some implementations, one or more devices of environment800may be physically integrated in, and/or may be physically attached to, one or more other devices of environment800. Alternatively, or additionally, one or more of the devices of environment800may perform one or more network functions described as being performed by another one or more of the devices of environment800.

Elements of environment800may interconnect with each other and/or other devices via wired connections, wireless connections, or a combination of wired and wireless connections. Examples of interfaces or communication pathways between the elements of environment800, as shown inFIG.8, may include an N1 interface, an N2 interface, an N3 interface, an N4 interface, an N5 interface, an N6 interface, an N7 interface, an N8 interface, an N9 interface, an N10 interface, an N11 interface, an N12 interface, an N13 interface, an N14 interface, an N15 interface, an N26 interface, an S1-C interface, an S1-U interface, an S5-C interface, an S5-U interface, an S6a interface, an S11 interface, and/or one or more other interfaces. Such interfaces may include interfaces not explicitly shown inFIG.8, such as Service-Based Interfaces (“SBIs”), including an Namf interface, an Nudm interface, an Npcf interface, an Nupf interface, an Nnef interface, an Nsmf interface, and/or one or more other SBIs. In some embodiments, environment800may be, may include, may be implemented by, and/or may be communicatively coupled to network601. Additionally, UCQRTS101may simulate elements of environment800, such as wireless network infrastructure equipment (e.g., antennas, radios, etc.) of RAN810and/or RAN812, when simulating downlink transmissions to one or more simulated UEs103.

UE103may include a computation and communication device, such as a wireless mobile communication device that is capable of communicating with RAN810, RAN812, and/or DN850. UE103may be, or may include, a radiotelephone, a personal communications system (“PCS”) terminal (e.g., a device that combines a cellular radiotelephone with data processing and data communications capabilities), a personal digital assistant (“PDA”) (e.g., a device that may include a radiotelephone, a pager, Internet/intranet access, etc.), a smart phone, a laptop computer, a tablet computer, a camera, a personal gaming system, an Internet of Things (“IoT”) device (e.g., a sensor, a smart home appliance, a wearable device, a Machine-to-Machine (“M2M”) device, or the like), a Fixed Wireless Access (“FWA”) device, or another type of mobile computation and communication device. UE103may send traffic to and/or receive traffic (e.g., user plane traffic) from DN850via RAN810, RAN812, and/or UPF/PGW-U835.

RAN810may be, or may include, a 5G RAN that includes one or more base stations (e.g., one or more gNBs811), via which UE103may communicate with one or more other elements of environment800. UE103may communicate with RAN810via an air interface (e.g., as provided by gNB811). For instance, RAN810may receive traffic (e.g., user plane traffic such as voice call traffic, data traffic, messaging traffic, etc.) from UE103via the air interface, and may communicate the traffic to UPF/PGW-U835and/or one or more other devices or networks. Further, RAN810may receive signaling traffic, control plane traffic, etc. from UE103via the air interface, and may communicate such signaling traffic, control plane traffic, etc. to AMF815and/or one or more other devices or networks. Additionally, RAN810may receive traffic intended for UE103(e.g., from UPF/PGW-U835, AMF815, and/or one or more other devices or networks) and may communicate the traffic to UE103via the air interface.

RAN812may be, or may include, a LTE RAN that includes one or more base stations (e.g., one or more eNBs813), via which UE103may communicate with one or more other elements of environment800. UE103may communicate with RAN812via an air interface (e.g., as provided by eNB813). For instance, RAN812may receive traffic (e.g., user plane traffic such as voice call traffic, data traffic, messaging traffic, signaling traffic, etc.) from UE103via the air interface, and may communicate the traffic to UPF/PGW-U835(e.g., via SGW817) and/or one or more other devices or networks. Further, RAN812may receive signaling traffic, control plane traffic, etc. from UE103via the air interface, and may communicate such signaling traffic, control plane traffic, etc. to MME816and/or one or more other devices or networks. Additionally, RAN812may receive traffic intended for UE103(e.g., from UPF/PGW-U835, MME816, SGW817, and/or one or more other devices or networks) and may communicate the traffic to UE103via the air interface.

AMF815may include one or more devices, systems, Virtualized Network Functions (“VNFs”), Cloud-Native Network Functions (“CNFs”), etc., that perform operations to register UE103with the 5G network, to establish bearer channels associated with a session with UE103, to hand off UE103from the 5G network to another network, to hand off UE103from the other network to the 5G network, manage mobility of UE103between RANs810and/or gNBs811, and/or to perform other operations. In some embodiments, the 5G network may include multiple AMFs815, which communicate with each other via the N14 interface (denoted inFIG.8by the line marked “N14” originating and terminating at AMF815).

MME816may include one or more devices, systems, VNFs, CNFs, etc., that perform operations to register UE103with the EPC, to establish bearer channels associated with a session with UE103, to hand off UE103from the EPC to another network, to hand off UE103from another network to the EPC, manage mobility of UE103between RANs812and/or eNBs813, and/or to perform other operations.

SGW817may include one or more devices, systems, VNFs, CNFs, etc., that aggregate traffic received from one or more eNBs813and send the aggregated traffic to an external network or device via UPF/PGW-U835. Additionally, SGW817may aggregate traffic received from one or more UPF/PGW-Us835and may send the aggregated traffic to one or more eNBs813. SGW817may operate as an anchor for the user plane during inter-eNB handovers and as an anchor for mobility between different telecommunication networks or RANs (e.g., RANs810and812).

SMF/PGW-C820may include one or more devices, systems, VNFs, CNFs, etc., that gather, process, store, and/or provide information in a manner described herein. SMF/PGW-C820may, for example, facilitate the establishment of communication sessions on behalf of UE103. In some embodiments, the establishment of communications sessions may be performed in accordance with one or more policies provided by PCF/PCRF825.

PCF/PCRF825may include one or more devices, systems, VNFs, CNFs, etc., that aggregate information to and from the 5G network and/or other sources. PCF/PCRF825may receive information regarding policies and/or subscriptions from one or more sources, such as subscriber databases and/or from one or more users (such as, for example, an administrator associated with PCF/PCRF825).

AF830may include one or more devices, systems, VNFs, CNFs, etc., that receive, store, and/or provide information that may be used in determining parameters (e.g., quality of service parameters, charging parameters, or the like) for certain applications.

UPF/PGW-U835may include one or more devices, systems, VNFs, CNFs, etc., that receive, store, and/or provide data (e.g., user plane data). For example, UPF/PGW-U835may receive user plane data (e.g., voice call traffic, data traffic, etc.), destined for UE103, from DN850, and may forward the user plane data toward UE103(e.g., via RAN810, SMF/PGW-C820, and/or one or more other devices). In some embodiments, multiple instances of UPF/PGW-U835may be deployed (e.g., in different geographical locations), and the delivery of content to UE103may be coordinated via the N9 interface (e.g., as denoted inFIG.8by the line marked “N9” originating and terminating at UPF/PGW-U835). Similarly, UPF/PGW-U835may receive traffic from UE103(e.g., via RAN810, RAN812, SMF/PGW-C820, and/or one or more other devices), and may forward the traffic toward DN850. In some embodiments, UPF/PGW-U835may communicate (e.g., via the N4 interface) with SMF/PGW-C820, regarding user plane data processed by UPF/PGW-U835.

UDM/HSS840and AUSF845may include one or more devices, systems, VNFs, CNFs, etc., that manage, update, and/or store, in one or more memory devices associated with AUSF845and/or UDM/HSS840, profile information associated with a subscriber. AUSF845and/or UDM/HSS840may perform authentication, authorization, and/or accounting operations associated with the subscriber and/or a communication session with UE103.

DN850may include one or more wired and/or wireless networks. For example, DN850may include an Internet Protocol (“IP”)-based PDN, a wide area network (“WAN”) such as the Internet, a private enterprise network, and/or one or more other networks. UE103may communicate, through DN850, with data servers, other UEs103, and/or to other servers or applications that are coupled to DN850. DN850may be connected to one or more other networks, such as a public switched telephone network (“PSTN”), a public land mobile network (“PLMN”), and/or another network. DN850may be connected to one or more devices, such as content providers, applications, web servers, and/or other devices, with which UE103may communicate.

FIG.9illustrates an example RAN environment900, which may be included in and/or implemented by one or more RANs (e.g., RAN810or some other RAN). As noted above, one or more elements of RAN environment900may be simulated by UCQRTS101. In some embodiments, a particular RAN810may include one RAN environment900. In some embodiments, a particular RAN810may include multiple RAN environments900. In some embodiments, RAN environment900may correspond to a particular gNB811of RAN810. In some embodiments, RAN environment900may correspond to multiple gNBs811. In some embodiments, RAN environment900may correspond to one or more other types of base stations of one or more other types of RANs. As shown, RAN environment900may include Central Unit (“CU”)905, one or more Distributed Units (“DUs”)903-1through903-N (referred to individually as “DU903,” or collectively as “DUs903”), and one or more Radio Units (“RUs”)901-1through901-M (referred to individually as “RU901,” or collectively as “RUs901”).

CU905may communicate with a core of a wireless network (e.g., may communicate with one or more of the devices or systems described above with respect toFIG.8, such as AMF815and/or a UPF). In the uplink direction (e.g., for traffic from UEs103to a core network), CU905may aggregate traffic from DUs903, and forward the aggregated traffic to the core network. In some embodiments, CU905may receive traffic according to a given protocol (e.g., Radio Link Control (“RLC”)) from DUs903, and may perform higher-layer processing (e.g., may aggregate/process RLC packets and generate Packet Data Convergence Protocol (“PDCP”) packets based on the RLC packets) on the traffic received from DUs903.

In accordance with some embodiments, CU905may receive downlink traffic (e.g., traffic from the core network) for a particular UE103, and may determine which DU(s)903should receive the downlink traffic. DU903may include one or more devices that transmit traffic between a core network (e.g., via CU905) and UE103(e.g., via a respective RU901). DU903may, for example, receive traffic from RU901at a first layer (e.g., physical (“PHY”) layer traffic, or lower PHY layer traffic), and may process/aggregate the traffic to a second layer (e.g., upper PHY and/or RLC). DU903may receive traffic from CU905at the second layer, may process the traffic to the first layer, and provide the processed traffic to a respective RU901for transmission to UE103.

RU901may include hardware circuitry (e.g., one or more RF transceivers, antennas, radios, and/or other suitable hardware) to communicate wirelessly (e.g., via an RF interface) with one or more UEs103, one or more other DUs903(e.g., via RUs901associated with DUs903), and/or any other suitable type of device. In the uplink direction, RU901may receive traffic from UE103and/or another DU903via the RF interface and may provide the traffic to DU903. In the downlink direction, RU901may receive traffic from DU903, and may provide the traffic to UE103and/or another DU903.

One or more elements of RAN environment900may, in some embodiments, be communicatively coupled to one or more Multi-Access/Mobile Edge Computing (“MEC”) devices, referred to sometimes herein simply as a “MECs,”907. For example, DU903-1may be communicatively coupled to MEC907-1, DU903-N may be communicatively coupled to MEC907-N, CU905may be communicatively coupled to MEC907-2, and so on. MECs907may include hardware resources (e.g., configurable or provisionable hardware resources) that may be configured to provide services and/or otherwise process traffic to and/or from UE103, via a respective RU901.

For example, DU903-1may route some traffic, from UE103, to MEC907-1instead of to a core network via CU905. MEC907-1may process the traffic, perform one or more computations based on the received traffic, and may provide traffic to UE103via RU901-1. In some embodiments, MEC907may include, and/or may implement, some or all of the functionality described above with respect to a UPF, AF830, and/or one or more other devices, systems, VNFs, CNFs, etc. In this manner, ultra-low latency services may be provided to UE103, as traffic does not need to traverse DU903, CU905, links between DU903and CU905, and an intervening backhaul network between RAN environment900and the core network.

FIG.10illustrates example components of device1000. One or more of the devices described above may include one or more devices1000. Device1000may include bus1010, processor1020, memory1030, input component1040, output component1050, and communication interface1060. In another implementation, device1000may include additional, fewer, different, or differently arranged components.

Bus1010may include one or more communication paths that permit communication among the components of device1000. Processor1020may include a processor, microprocessor, or processing logic that may interpret and execute instructions (e.g., processor-executable instructions). In some embodiments, processor1020may be or may include one or more hardware processors. Memory1030may include any type of dynamic storage device that may store information and instructions for execution by processor1020, and/or any type of non-volatile storage device that may store information for use by processor1020.

Input component1040may include a mechanism that permits an operator to input information to device1000and/or other receives or detects input from a source external to input component1040, such as a touchpad, a touchscreen, a keyboard, a keypad, a button, a switch, a microphone or other audio input component, etc. In some embodiments, input component1040may include, or may be communicatively coupled to, one or more sensors, such as a motion sensor (e.g., which may be or may include a gyroscope, accelerometer, or the like), a location sensor (e.g., a Global Positioning System (“GPS”)-based location sensor or some other suitable type of location sensor or location determination component), a thermometer, a barometer, and/or some other type of sensor. Output component1050may include a mechanism that outputs information to the operator, such as a display, a speaker, one or more light emitting diodes (“LEDs”), etc.

Communication interface1060may include any transceiver-like mechanism that enables device1000to communicate with other devices and/or systems. For example, communication interface1060may include an Ethernet interface, an optical interface, a coaxial interface, or the like. Communication interface1060may include a wireless communication device, such as an infrared (“IR”) receiver, a Bluetooth® radio, or the like. The wireless communication device may be coupled to an external device, such as a remote control, a wireless keyboard, a mobile telephone, etc. In some embodiments, device1000may include more than one communication interface1060. For instance, device1000may include an optical interface and an Ethernet interface.