SYSTEMS AND METHODS FOR CONDITIONAL HANDOVER USING NON-TERRESTRIAL NODE TELEMETRY INFORMATION

A device described herein, such as a User Equipment (“UE”), may connect to a base station of a wireless network, receive telemetry information associated with a plurality of Non-Terrestrial Network (“NTN”) nodes, identify a particular handover condition, select, based on identifying the particular handover condition, a particular NTN node of the plurality of NTN nodes, initiate a handover procedure from the first base station of the wireless network to the selected particular NTN node, and connect to the particular NTN node based on the handover procedure. The NTN nodes may be implemented by satellites that orbit the Earth.

BACKGROUND

Wireless networks provide wireless connectivity to user equipment (“UE”), such as mobile telephones or other wireless communication devices. Wireless networks may include wireless network infrastructure, such as ground-based base stations, which may be installed on buildings, towers, or other structures. Some wireless networks may include Non-Terrestrial Networks (“NTNs”), which may utilize satellites or other machines, equipment, etc. that orbit the Earth and which may not have a fixed position relative to the ground.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Embodiments described herein provide for a UE to detect handover conditions and initiate handovers to and/or from NTN nodes, such as satellites or other wireless network infrastructure equipment that orbits the Earth and/or is otherwise mobile and/or airborne. For example, as discussed below, a UE may receive NTN telemetry information, based on which the UE may select a particular NTN node, and may initiate a handover to the selected particular NTN node. In this manner, the wireless coverage provided by a wireless network may be enhanced to include connectivity to NTN nodes. Further, since embodiments described herein afford UEs the opportunity to detect handover conditions (e.g., based on UE-detected signal strength metrics, UE-determined latency or other performance metrics, UE-determined application or traffic types, etc.), the options available to UEs to initiate handovers (e.g., handover targets) may be widened by the availability of NTN nodes, thus enhancing the coverage of wireless services offered to UEs.

As shown inFIG.1, multiple NTN nodes101may orbit the Earth and/or may otherwise be mobile and/or airborne. As discussed above, NTN nodes101may include and/or may be implemented by satellites and/or other suitable apparatus that includes wireless network infrastructure equipment (e.g., radios, antennas, etc.). NTN nodes101may implement, for example, a base station of RAN, a Distributed Unit (“DU”) of a RAN, and/or some other element of a wireless network that provides a wireless interface between UEs, such as mobile phones, Internet of Things (“IoT”) devices, etc. and a core network (e.g., an Evolved Packet Core (“EPC”), a Fifth Generation (“5G”) core (“5GC”), etc.). In the examples described herein, each NTN node101is described as being implemented by a single satellite or other suitable apparatus. However, concepts similar to those described herein apply to other arrangements or implementations, such as implementations in which a single satellite or other suitable apparatus implements multiple NTN nodes101.

As further shown inFIG.1, a set of NTN nodes may be associated with a particular NTN node group103. For example, NTN node group103may include NTN nodes101that are configured to communicate with each other and/or otherwise to receive information associated with each other, such as telemetry information as discussed below. In some implementations, NTN node group103may be referred to as, or implemented by, a “constellation” of satellites. In some embodiments, NTN node group103may not be a predetermined group, but may instead refer to a set of NTN nodes101that are within a threshold proximity of each other (e.g., within wireless communication range of each other). For example, NTN nodes101of NTN node group103may be “neighbors” of each other, inasmuch as NTN nodes101of NTN node group103may be located physically closer to each other than other NTN nodes101(e.g., other NTN nodes101that are orbiting the Earth).

Each NTN node101may generate, receive, or otherwise maintain a set of telemetry information, “ephemeris” information, etc. (referred to herein simply as “telemetry information” for the sake of brevity). For example, as shown inFIG.2, NTN node101-1may maintain a respective set of NTN node telemetry information201-1. NTN node telemetry information201-1may include, for example, a current position of NTN node101-1and a trajectory of NTN node101-1. The current position may be expressed in terms of latitude and longitude coordinates, altitude, and/or other suitable position information indicating where NTN node101-1is in relation to a reference point or line on the Earth (e.g., the North Pole, the Equator, the Prime Meridian, sea level, etc.). The trajectory may be expressed in terms of heading, speed, target location(s) and predicted or estimated time of arrival, a flight plan, and/or other suitable information based on which a future location of NTN node101-1may be determined. In some embodiments, NTN node telemetry information201-1may include other suitable information describing telemetry of NTN node101-1, such as angle, acceleration, or other suitable information. NTN node telemetry information201-1may be determined by NTN node101-1based on one or more onboard sensors, and/or may be received from some other source, such as a terrestrial-based control station, another NTN node101, and/or some other suitable device or system. NTN node telemetry information201-1may also include a timestamp, indicating a time at which the position, trajectory, etc. have been determined.

In this manner, as shown inFIG.3, each NTN node101(e.g., NTN nodes101-1,101-2, and101-3) of NTN node group103may maintain its own respective NTN node telemetry information201(e.g., NTN node101-2may maintain NTN node telemetry information201-2and NTN node101-3may maintain NTN node telemetry information201-3). Additionally, as shown inFIG.4, each NTN node101of NTN node group103may maintain NTN node telemetry information201of some or all of the other NTN nodes101of NTN node group103. In the example shown, NTN nodes101-1,101-2, and101-3may maintain a set of group telemetry information401(e.g., an “almanac”), which may include the respective NTN node telemetry information201of each NTN node101of NTN node group103(e.g., NTN node telemetry information201-1,201-2, and201-3, in this example). For example, in addition to maintaining its own NTN node telemetry information201-1, NTN node101-1may also maintain NTN node telemetry information201-2and201-3associated with NTN nodes101-2and101-3, respectively. Similarly, in addition to maintaining its own NTN node telemetry information201-2, NTN node101-2may also maintain NTN node telemetry information201-1and201-3associated with NTN nodes101-1and101-3, respectively.

NTN nodes101may receive NTN node telemetry information201associated with other NTN nodes101by wirelessly communicating directly with such NTN nodes101. For example, NTN nodes101-1and101-2may wirelessly communicate with each other in order for NTN node101-1to provide NTN node telemetry information201-1to NTN node101-2, and for NTN node101-2to provide NTN node telemetry information201-2to NTN node101-1. Additionally, or alternatively, NTN nodes101may communicate indirectly via one or more relays, such as ground-based devices or systems and/or via one or more other airborne devices or systems. For example, NTN node101-1may provide NTN node telemetry information201-1to such relay device or system, which may forward NTN node telemetry information201-1to NTN nodes101-2and/or101-3. In some situations, group telemetry information401may include different versions of NTN node telemetry information201associated with respective NTN nodes101. For example, NTN node telemetry information201-2, maintained by NTN node101-1, may be less up-to-date than NTN node telemetry information201-2as maintained by NTN node101-2. For example, NTN node101-2may update a local copy of NTN node telemetry information201-2more frequently than NTN node101-1receives updated NTN node telemetry information201-2.

As discussed herein, group telemetry information401and/or NTN node telemetry information201associated with one or more NTN nodes101may be used by a UE when detecting handover conditions, selecting handover targets, and initiating handovers to such handover targets. For example, as shown inFIG.5A, UE501may scan for and connect (at502) to NTN node101-1. UE501may be an NTN-capable UE, inasmuch as one or more radios, antennas, etc. of UE501may operate according to the same frequency, frequency band, radio access technology (“RAT”), etc. implemented by NTN node101-1.

In some implementations, UE501may scan for and connect (at502) to NTN node101-1based on the absence of a ground-based base station. For example, prior to scanning (at502) for NTN node101-1(e.g., attempting to locate wireless signals such as Master Information Blocks (“MIBs”), System Information Blocks (“SIBs”), timing and/or synchronization signals, presence signals, etc. outputted by one or more NTN nodes101), UE501may have scanned for one or more ground-based base stations according to a frequency, frequency band, RAT, etc. implemented by such ground-based base stations. In such a situation, UE501may have not detected the presence of a ground-based base station, based on which UE501may scan (at502) according to a frequency, frequency band, RAT, etc. associated with NTN nodes101.

Connecting to NTN node101-1may include performing a Radio Resource Control (“RRC”) connection setup, exchanging one or more RRC messages, etc. As part of, in conjunction with, or subsequent to the respective connection setup, NTN node101may request attributes, capabilities, etc. of UE501. UE501may respond with an indication that UE501supports conditional handover procedures, and/or may respond with a request for conditional handover information.

In response to the indication that UE501supports conditional handover procedures, in response to the request for conditional handover information, and/or based on one or more other factors (e.g., based on the connection of UE501to NTN node101-1), NTN node101-1may respond with a set of handover conditions503. NTN handover conditions503may specify conditions based on which UE501may request a handover from NTN node101-1(or other NTN nodes101and/or wireless network infrastructure, including ground-based base stations) to another NTN node101and/or to some other wireless network infrastructure. NTN node101-1may, in some embodiments, receive NTN handover conditions503from a core network or some other suitable source.

As one example, NTN handover conditions503may specify that UE501should request a handover from a particular NTN node101, to which UE501is connected, to another NTN node101if signal strength metrics between UE501and the particular NTN node101(e.g., as measured by UE501) are below a first threshold and if signal strength metrics between UE501and the other NTN node101are above a second threshold. As another example, NTN handover conditions503may specify that UE501should request a handover from the particular NTN node101, to which UE501is connected, to another NTN node101if a distance between UE501and the particular NTN node101(e.g., as determined by UE501based on receiving group telemetry information401) is greater than a first threshold distance and if distance metrics between UE501and the other NTN node101is less than a second threshold distance.

As shown, NTN node101-1may also provide (at504) group telemetry information401, which may include NTN node telemetry information201-1associated with NTN node101-1as well as NTN node telemetry information201associated with one or more other NTN nodes101(e.g., NTN nodes101of the same NTN node group103as NTN node101-1). In some embodiments, UE501may receive (at504) group telemetry information401as part of, in conjunction with, or subsequent to the connection (at502) of UE501to NTN node101-1. In some embodiments, UE501may additionally receive, on an ongoing basis and while UE501is connected to NTN node101-1, updated group telemetry information401(e.g., in the event that NTN node101-1receives updates to some or all of group telemetry information401over time, such as course changes or updated positions associated with NTN node101-1and/or one or more other NTN nodes101). In this manner, UE501may be “aware” of the positions of NTN node101-1and one or more other NTN nodes101at any given time, including future times (e.g., based on a present position and trajectory of respective NTN nodes101).

In some embodiments, UE501may receive group telemetry information401and/or NTN handover conditions503without connecting to a given NTN node101. For example, as shown inFIG.5B, UE501may receive (at506) NTN handover conditions503and/or group telemetry information401from a source other than NTN node101-1, and/or from NTN node101-1prior to connecting to NTN node101-1. For example, NTN node101-1, a ground-based base station, and/or some other device or system may provide (at506) NTN handover conditions503and group telemetry information401prior to UE501scanning for and connecting to (at508) NTN node101-1. In some embodiments, NTN node101-1, another NTN node101, and/or some other device or system may broadcast NTN handover conditions503and/or group telemetry information401as part of a MIB, SIB, or other type of control signaling. Additionally, or alternatively, NTN node101-1, another NTN node101, and/or some other device or system may broadcast NTN handover conditions503and/or group telemetry information401using a Multimedia Broadcast Multicast Service (“MBMS”) technique, an evolved MBMS (“eMBMS”) technique, and/or some other suitable type of broadcast technique. Additionally, or alternatively, UE501may have received (at506) NTN handover conditions503and/or group telemetry information401during an initial provisioning procedure, an Over-the-Air (“OTA”) update procedure, and/or via some other suitable procedure. Accordingly, based on the techniques described inFIG.5A or5B, and/or some other suitable technique, UE501may receive and maintain a set of NTN handover conditions503as well as group telemetry information401associated with one or more NTN nodes101(e.g., associated with one or more NTN node groups103).

FIGS.6and7illustrate an example handover that may be initiated by a given UE501when such UE501is currently connected to a given NTN node101. For example, as shown inFIG.6, UE501may be connected to NTN node101-1. At some point, while UE501is connected to NTN node101-1, UE501may detect (at602) a handover condition. For example, UE501may compare group telemetry information401(e.g., NTN node telemetry information201-1associated with NTN node101-1and/or NTN node telemetry information201-2associated with NTN node101-2), measures of signal strength or quality associated with NTN nodes101-1and/or101-2, and/or other factors, to one or more NTN handover conditions503.

In this example, UE501may identify, based on group telemetry information401, a trajectory, course, heading, direction, etc. (hereinafter referred to as trajectory601) associated with each NTN node101. For example, UE501may identify trajectory601-1associated with NTN node101-1, and may identify trajectory601-2associated with NTN node101-2. Such trajectories601may indicate, in this example, that NTN node101-1is moving away from UE501(e.g., a distance between NTN node101-1and UE501may be increasing as a function of time) and that NTN node101-2is moving toward UE501(e.g., a distance between NTN node101-2and UE501may be decreasing as a function of time). In some embodiments, UE501may identify one or more other metrics, Key Performance Indicators (“KPIs”), events, etc. For example, UE501may identify that a measure of signal strength or quality (e.g., Signal-to-Interference-and-Noise-Ratio (“SINR”), Reference Signal Received Power (“RSRP”), Reference Signal Received Quality (“RSRQ”), etc.) between UE501and NTN node101-1is decreasing and/or is below a first threshold, and/or may identify that a measure of signal strength or quality between UE501and NTN node101-2is increasing and/or is above a second threshold.

Based on identifying the relative trajectories601of NTN nodes101-1and101-2and/or based on other factors, UE501may determine that a particular handover condition, associated with NTN handover conditions503, has been met. UE501may further identify that NTN node101-2is a suitable handover target based on criteria, instructions, or actions associated with the particular determined handover condition. In some embodiments, UE501may identify that NTN node101-2is a suitable handover target based on signal strength or quality measurements performed by UE501(e.g., NTN node101-2may be a NTN node101with the highest measure of signal strength or quality with which UE501is able to wirelessly communicate). In some embodiments, UE501may identify that NTN node101-2is a suitable handover target based on one or more other techniques.

UE501may accordingly initiate (at604) a handover to NTN node101-2. For example, UE501may output a handover request to NTN node101-1and/or to NTN node101-2, indicating NTN node101-2as a handover target and/or indicating NTN node101-1as a handover source. NTN nodes101-1and101-2may accordingly communicate with each other, with UE501, and/or one or more other devices or systems (e.g., an Access and Mobility Management Function (“AMF”), a Mobility Management Entity (“MME”), and/or some other network function) in order to effectuate the UE-initiated handover of UE501from NTN node101-1to101-2.

After the handover has been performed, and as shown inFIG.7, UE501may be connected to NTN node101-2and may no longer be connected to NTN node101-1. In some embodiments, the result of the handover may be different than the example shown inFIG.7. For example, the handover may result in a connection between UE501and NTN node101-2being established, and a connection between UE501and NTN node101-1remaining established and/or being set to a different mode or state (e.g., an idle mode, a secondary mode, etc.).

FIGS.7and8illustrate another example handover that may be initiated by UE501based on NTN node telemetry information201and/or group telemetry information401associated with one or more NTN nodes101and/or NTN node groups103. As shown, UE501may be connected (at802) to ground-based base station (also referred to as “ground base station”)801. For example, as discussed above, ground base station801may be mounted, installed, affixed, etc. to a building, a tower, a vehicle, and/or some other ground-based device or structure. UE501may further receive (at804) group telemetry information401(e.g., NTN node telemetry information201associated with one or more NTN nodes101, such as NTN nodes101-1and/or101-2) and/or may receive a set of NTN handover conditions503. For example, as discussed above with respect toFIG.5(at506), UE501may receive group telemetry information401and/or NTN handover conditions503from one or more NTN nodes101(e.g., which may broadcast such information), from ground base station801(e.g., which may serve as a relay for such information, which may be received from NTN nodes101and/or from some other device or system that provides such information), and/or from some other source. For example, UE501may receive group telemetry information401on an ongoing basis, such as when NTN node telemetry information201associated with one or more NTN nodes101is updated or otherwise provided.

At some point, UE501may determine (at806) a handover condition, such as detecting the UE501is moving away from ground base station801, that a signal strength between UE501and ground base station801is approaching or is below a threshold measure of signal strength, that UE501is initiating a particular application or service type indicated in a particular set of handover conditions503(e.g., is initiating an emergency call, is initiating a secure message session, etc.), and/or may identify the handover condition based on one or more other UE-determined metrics or events.

UE501may select (at808) NTN node101-2as a handover target based on determining (at806) the handover condition. For example, UE501may utilize group telemetry information401(e.g., NTN node telemetry information201-1associated with NTN node101-1and/or NTN node telemetry information201-2associated with NTN node101-2) to select (at808) NTN node101-2as a handover target for UE501. Based on group telemetry information401, UE501may determine that NTN node101-2is closer in position to UE501than one or more other NTN nodes101(e.g., NTN node101-1). As another example, UE501may receive or maintain information (e.g., from a user of UE501) indicating a predicted or expected route (e.g., a navigation route of UE501from one geographical location to another), and may further identify that a trajectory of NTN node101-2matches the predicted or expected route of UE501most closely out of a set of NTN nodes101. That is, UE501may select (at808) NTN node101-2based on factors in addition to, or in lieu of, signal strength or quality metrics between UE501and NTN node101-2, such as based on a trajectory of NTN node101-2and/or one or more other NTN nodes101. Thus, as shown inFIG.9, UE501may initiate (at910) a handover from ground base station801to NTN node101-2, resulting in a connection being established between UE501and NTN node101-2, and a connection between UE501being de-established or otherwise modified based on the handover.

FIG.10illustrates an example process1000for performing a UE-initiated handover based on NTN node telemetry information. In some embodiments, some or all of process1000may be performed by UE501. In some embodiments, one or more other devices may perform some or all of process1000in concert with, and/or in lieu of, UE501.

As shown, process1000may include connecting (at1002) to a base station of a wireless network. For example, UE501may connection to a base station implemented by a satellite (e.g., may connect to a particular NTN node101) or to a ground-based base station (e.g., ground base station801).

Process1000may further include receiving (at1004) handover condition information. For example, UE501may receive handover conditions503from the base station to which UE501is currently connected (e.g., from NTN node101, from ground base station801, etc.) and/or may receive handover conditions503from some other source (e.g., via a broadcast or some other suitable technique). As discussed above, handover conditions503may include factors, criteria, conditions, thresholds, etc. based on information that may be measured, collected, etc. by UE501. Such factors, criteria, etc. may be based on signal strength metrics measured by UE501, a predicted or expected location of UE501, and/or other UE-determined metrics or events. As another example, handover conditions503may include factors, criteria, etc. associated with NTN nodes101, such as relative location of a given NTN node101to UE501and/or a trajectory of NTN node101relative to UE501. For example, NTN handover conditions503may include conditions relating to whether NTN node101is moving towards UE501, is moving away from UE501, is within a threshold proximity of UE501for at least a threshold amount of time based on a trajectory of NTN node101and a predicted or estimated path of UE501, and/or other NTN node101trajectory-based conditions.

Process1000may additionally include receiving and/or monitoring (at1006) telemetry information associated with one or more NTN nodes101. For example, NTN nodes101may maintain their own respective NTN node telemetry information201(e.g., “ephemeris” data) as well as NTN node telemetry information201associated with one or more other NTN nodes101(e.g., an “almanac”), such that one particular NTN node101may provide NTN node telemetry information201associated with multiple NTN nodes101(e.g., group telemetry information401). As discussed above, UE501may receive NTN node telemetry information201and/or group telemetry information401from a particular NTN node101to which UE501is currently connected, may receive NTN node telemetry information201and/or group telemetry information401from a particular NTN node101to which UE501is not currently connected (e.g., via one or more broadcasts by the particular NTN node101), one or more relays, and/or from some other suitable source. UE501may receive NTN node telemetry information201and/or group telemetry information401on an ongoing basis, such as when such information changes or when other NTN node telemetry information201associated with one or more other NTN nodes101becomes available (e.g., such NTN nodes101may move towards another NTN node101that is currently providing NTN node telemetry information201and/or group telemetry information401to UE501).

Process1000may also include identifying (at1008) a handover condition. For example, UE501may compare UE-determined metrics or information, NTN node telemetry information201associated with one or more NTN nodes101, and/or other suitable information to handover conditions503and may identify that at least a particular handover condition is satisfied.

Process1000may further include selecting (at1010) a particular NTN node101as a handover target. For example, UE501may select the particular NTN node101, from a group of NTN nodes101for which UE501has received NTN node telemetry information201, based on a trajectory of the particular NTN node101, a location of NTN node101, and/or one or more other factors. In some embodiments, the selected NTN node101may be a different NTN node101from which UE501received NTN node telemetry information201and/or group telemetry information401. Generally, UE501may identify that the particular NTN node101is the closest NTN node101to UE501, is predicted or estimated to be the closest NTN node101or within a particular distance of UE501for at least a threshold amount of time (e.g., based on a location of UE501and/or based on a predicted or estimated path or route of UE501), and/or is otherwise a “best match” for a handover target for UE501based on NTN node telemetry information201associated with the particular NTN node101and/or other NTN nodes101.

Process1000may additionally include initiating (at1012) a handover to the selected NTN node101. For example, as discussed above, UE501may output one or more messages to the base station to which UE501is currently connected, and/or may output one or more messages to the selected NTN node101, to initiate the handover. The currently connected base station, the selected NTN node101, and/or one or more other devices or systems may communicate in order to effectuate the handover, after which UE501may communicate with the wireless network via the particular NTN node101(e.g., may be handed over from the source base station, to which UE501was previously connected, to the selected NTN node101.

FIG.11illustrates an example environment1100, in which one or more embodiments may be implemented. In some embodiments, environment1100may correspond to a Fifth Generation (“5G”) network, and/or may include elements of a 5G network. In some embodiments, environment1100may 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 environment1100may represent or may include a 5G core (“5GC”). As shown, environment1100may include UE501, RAN1110(which may include one or more Next Generation Node Bs (“gNBs”)1111), RAN1112(which may include one or more evolved Node Bs (“eNBs”)1113), and various network functions such as AMF1115, MME1116, Serving Gateway (“SGW”)1117, Session Management Function (“SMF”)/Packet Data Network (“PDN”) Gateway (“PGW”)-Control plane function (“PGW-C”)1120, Policy Control Function (“PCF”)/Policy Charging and Rules Function (“PCRF”)1125, Application Function (“AF”)1130, User Plane Function (“UPF”)/PGW-User plane function (“PGW-U”)1135, Unified Data Management (“UDM”)/Home Subscriber Server (“HSS”)1140, and Authentication Server Function (“AUSF”)1145. Environment1100may also include one or more networks, such as Data Network (“DN”)1150.

The example shown inFIG.11illustrates one instance of each network component or function (e.g., one instance of SMF/PGW-C1120, PCF/PCRF1125, UPF/PGW-U1135, UDM/HSS1140, and/or AUSF1145). In practice, environment1100may include multiple instances of such components or functions. For example, in some embodiments, environment1100may 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 SMF/PGW-C1120, PCF/PCRF1125, UPF/PGW-U1135, UDM/HSS1140, and/or AUSF1145, while another slice may include a second instance of SMF/PGW-C1120, PCF/PCRF1125, UPF/PGW-U1135, UDM/HSS1140, and/or AUSF1145). 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.11, is provided for explanatory purposes only. In practice, environment1100may 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.11. For example, while not shown, environment1100may include devices that facilitate or enable communication between various components shown in environment1100, such as routers, modems, gateways, switches, hubs, etc. In some implementations, one or more devices of environment1100may be physically integrated in, and/or may be physically attached to, one or more other devices of environment1100. Alternatively, or additionally, one or more of the devices of environment1100may perform one or more network functions described as being performed by another one or more of the devices of environment1100.

Elements of environment1100may 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 environment1100, as shown inFIG.11, 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 N2 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.11, 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.

UE501may include a computation and communication device, such as a wireless mobile communication device that is capable of communicating with RAN1110, RAN1112, and/or DN1150. UE501may 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), or another type of mobile computation and communication device. UE501may send traffic to and/or receive traffic (e.g., user plane traffic) from DN1150via RAN1110, RAN1112, and/or UPF/PGW-U1135.

RAN1110may be, or may include, a 5G RAN that includes one or more base stations (e.g., one or more gNBs1111), via which UE501may communicate with one or more other elements of environment1100. UE501may communicate with RAN1110via an air interface (e.g., as provided by gNB1111). For instance, RAN1110may receive traffic (e.g., user plane traffic such as voice call traffic, data traffic, messaging traffic, etc.) from UE501via the air interface, and may communicate the traffic to UPF/PGW-U1135and/or one or more other devices or networks. Further, RAN1110may receive signaling traffic, control plane traffic, etc. from UE501via the air interface, and may communicate such signaling traffic, control plane traffic, etc. to AMF1115and/or one or more other devices or networks. Additionally, RAN1110may receive traffic intended for UE501(e.g., from UPF/PGW-U1135, AMF1115, and/or one or more other devices or networks) and may communicate the traffic to UE501via the air interface. In some embodiments, ground base station801may be, may include, and/or may be implemented by one or more gNBs1111. In some embodiments, one or more NTN nodes101may be, may include, may implement, etc. one or more gNBs1111. As such, RAN1110may include one or more ground base stations801and/or one or more NTN nodes101.

RAN1112may be, or may include, a LTE RAN that includes one or more base stations (e.g., one or more eNBs1113), via which UE501may communicate with one or more other elements of environment1100. UE501may communicate with RAN1112via an air interface (e.g., as provided by eNB1113). For instance, RAN1112may receive traffic (e.g., user plane traffic such as voice call traffic, data traffic, messaging traffic, signaling traffic, etc.) from UE501via the air interface, and may communicate the traffic to UPF/PGW-U1135(e.g., via SGW1117) and/or one or more other devices or networks. Further, RAN1112may receive signaling traffic, control plane traffic, etc. from UE501via the air interface, and may communicate such signaling traffic, control plane traffic, etc. to MME1116and/or one or more other devices or networks. Additionally, RAN1112may receive traffic intended for UE501(e.g., from UPF/PGW-U1135, MME1116, SGW1117, and/or one or more other devices or networks) and may communicate the traffic to UE501via the air interface. In some embodiments, ground base station801may be, may include, and/or may be implemented by one or more eNBs1113. In some embodiments, one or more NTN nodes101may be, may include, may implement, etc. one or more eNBs1113. As such, RAN1112may include one or more ground base stations801and/or one or more NTN nodes101.

AMF1115may include one or more devices, systems, Virtualized Network Functions (“VNFs”), Cloud-Native Network Functions (“CNFs”), etc., that perform operations to register UE501with the 5G network, to establish bearer channels associated with a session with UE501, to hand off UE501from the 5G network to another network, to hand off UE501from the other network to the 5G network, manage mobility of UE501between RANs1110and/or gNBs1111, and/or to perform other operations. In some embodiments, the 5G network may include multiple AMFs1115, which communicate with each other via the N14 interface (denoted inFIG.11by the line marked “N14” originating and terminating at AMF1115).

MME1116may include one or more devices, systems, VNFs, CNFs, etc., that perform operations to register UE501with the EPC, to establish bearer channels associated with a session with UE501, to hand off UE501from the EPC to another network, to hand off UE501from another network to the EPC, manage mobility of UE501between RANs1112and/or eNBs1113, and/or to perform other operations.

SGW1117may include one or more devices, systems, VNFs, CNFs, etc., that aggregate traffic received from one or more eNBs1113and send the aggregated traffic to an external network or device via UPF/PGW-U1135. Additionally, SGW1117may aggregate traffic received from one or more UPF/PGW-Us1135and may send the aggregated traffic to one or more eNBs1113. SGW1117may 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., RANs1110and1112).

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

PCF/PCRF1125may include one or more devices, systems, VNFs, CNFs, etc., that aggregate information to and from the 5G network and/or other sources. PCF/PCRF1125may 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/PCRF1125).

AF1130may 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-U1135may 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-U1135may receive user plane data (e.g., voice call traffic, data traffic, etc.), destined for UE501, from DN1150, and may forward the user plane data toward UE501(e.g., via RAN1110, SMF/PGW-C1120, and/or one or more other devices). In some embodiments, multiple UPFs1135may be deployed (e.g., in different geographical locations), and the delivery of content to UE501may be coordinated via the N9 interface (e.g., as denoted inFIG.11by the line marked “N9” originating and terminating at UPF/PGW-U1135). Similarly, UPF/PGW-U1135may receive traffic from UE501(e.g., via RAN1110, RAN1112, SMF/PGW-C1120, and/or one or more other devices), and may forward the traffic toward DN1150. In some embodiments, UPF/PGW-U1135may communicate (e.g., via the N4 interface) with SMF/PGW-C1120, regarding user plane data processed by UPF/PGW-U1135.

UDM/HSS1140and AUSF1145may include one or more devices, systems, VNFs, CNFs, etc., that manage, update, and/or store, in one or more memory devices associated with AUSF1145and/or UDM/HSS1140, profile information associated with a subscriber. AUSF1145and/or UDM/HSS1140may perform authentication, authorization, and/or accounting operations associated with the subscriber and/or a communication session with UE501.

DN1150may include one or more wired and/or wireless networks. For example, DN1150may 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. UE501may communicate, through DN1150, with data servers, other UEs501, and/or to other servers or applications that are coupled to DN1150. DN1150may 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. DN1150may be connected to one or more devices, such as content providers, applications, web servers, and/or other devices, with which UE501may communicate.

FIG.12illustrates an example RAN environment1200, which may be included in and/or implemented by one or more RANs (e.g., RAN1110, RAN1112, or some other RAN). In some embodiments, a particular RAN may include one RAN environment1200. In some embodiments, a particular RAN may include multiple RAN environments1200. In some embodiments, RAN environment1200may correspond to a particular gNB1111of a 5G RAN (e.g., RAN1110). In some embodiments, RAN environment1200may correspond to multiple gNBs1111. In some embodiments, RAN environment1200may correspond to one or more other types of base stations of one or more other types of RANs. As shown, RAN environment1200may include Central Unit (“CU”)1205, one or more Distributed Units (“DUs”)1203-1through1203-N (referred to individually as “DU1203,” or collectively as “DUs1203”), and one or more Radio Units (“RUs”)1201-1through1201-M (referred to individually as “RU1201,” or collectively as “RUs1201”).

CU1205may 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.11, such as AMF1115and/or UPF/PGW-U1135). In the uplink direction (e.g., for traffic from UEs501to a core network), CU1205may aggregate traffic from DUs1203, and forward the aggregated traffic to the core network. In some embodiments, CU1205may receive traffic according to a given protocol (e.g., Radio Link Control (“RLC”)) from DUs1203, 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 DUs1203.

In accordance with some embodiments, CU1205may receive downlink traffic (e.g., traffic from the core network) for a particular UE501, and may determine which DU(s)1203should receive the downlink traffic. DU1203may include one or more devices that transmit traffic between a core network (e.g., via CU1205) and UE501(e.g., via a respective RU1201). DU1203may, for example, receive traffic from RU1201at 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). DU1203may receive traffic from CU1205at the second layer, may process the traffic to the first layer, and provide the processed traffic to a respective RU1201for transmission to UE501.

RU1201may 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 UEs501, one or more other DUs1203(e.g., via RUs1201associated with DUs1203), and/or any other suitable type of device. In the uplink direction, RU1201may receive traffic from UE501and/or another DU1203via the RF interface and may provide the traffic to DU1203. In the downlink direction, RU1201may receive traffic from DU1203, and may provide the traffic to UE501and/or another DU1203.

One or more elements of RAN environment1200may, in some embodiments, be communicatively coupled to one or more Multi-Access/Mobile Edge Computing (“MEC”) devices, referred to sometimes herein simply as “MECs”1207. For example, DU1203-1may be communicatively coupled to MEC1207-1, DU1203-N may be communicatively coupled to MEC1207-N, CU1205may be communicatively coupled to MEC1207-2, and so on. MECs1207may 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 UE501, via a respective RU1201.

For example, DU1203-1may route some traffic, from UE501, to MEC1207-1instead of to a core network via CU1205. MEC1207-1may process the traffic, perform one or more computations based on the received traffic, and may provide traffic to UE501via RU1201-1. In some embodiments, MEC1207may include, and/or may implement, some or all of the functionality described above with respect to AF1130, UPF1135, and/or one or more other devices, systems, VNFs, CNFs, etc. In this manner, ultra-low latency services may be provided to UE501, as traffic does not need to traverse DU1203, CU1205, links between DU1203and CU1205, and an intervening backhaul network between RAN environment1200and the core network.

FIG.13illustrates example components of device1300. One or more of the devices described above may include one or more devices1300. Device1300may include bus1310, processor1320, memory1330, input component1340, output component1350, and communication interface1360. In another implementation, device1300may include additional, fewer, different, or differently arranged components.

Bus1310may include one or more communication paths that permit communication among the components of device1300. Processor1320may include a processor, microprocessor, or processing logic that may interpret and execute instructions. In some embodiments, processor1320may be or may include one or more hardware processors. Memory1330may include any type of dynamic storage device that may store information and instructions for execution by processor1320, and/or any type of non-volatile storage device that may store information for use by processor1320.

Input component1340may include a mechanism that permits an operator to input information to device1300and/or other receives or detects input from a source external to input component1340, 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 component1340may 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 component1350may include a mechanism that outputs information to the operator, such as a display, a speaker, one or more light emitting diodes (“LEDs”), etc.

Communication interface1360may include any transceiver-like mechanism that enables device1300to communicate with other devices and/or systems. For example, communication interface1360may include an Ethernet interface, an optical interface, a coaxial interface, or the like. Communication interface1360may 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, device1300may include more than one communication interface1360. For instance, device1300may include an optical interface and an Ethernet interface.