Fifth generation new radio edge computing mobility management

This document describes mobility management of edge computing resources in fifth generation new radio (5G NR) wireless networks. The techniques described enable authorizing user devices to access edge compute servers that execute applications for the user device. The techniques described also enable the migration of applications of user devices between edge compute servers based on mobility changes of user devices in a wireless network, such as handovers of a user device between base stations in the wireless network.

BACKGROUND

The evolution of wireless communication to fifth generation (5G) standards and technologies provides higher data rates and greater capacity, with improved reliability and lower latency, which enhances mobile broadband services. 5G technologies also provide new classes of services for vehicular networking, fixed wireless broadband, and the Internet of Things (IoT).

Latencies for distributed applications in existing wireless networks are limited by the latency associated with connecting a mobile application through the wireless access network and through the Internet to application servers. Computing resources for distributed applications may be placed at the edge of the 5G networks to reduce latency for mobile applications.

Distributed edge computing in 5G networks presents management and mobility issues not addressed in conventional wireless networks and distributed applications. Conventional distributed applications are unaware of user device mobility in wireless networks, and conventional wireless networks are not architected to manage configuration and mobility for edge computing resources.

SUMMARY

This summary is provided to introduce simplified concepts of fifth generation new radio edge computing mobility management. The simplified concepts are further described below in the Detailed Description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining the scope of the claimed subject matter.

In some aspects, a method of managing edge computing resources in a wireless communication network is described, in which an Edge Computing Access and Mobility Function (EC-AMF) server receives an indication of a handover of a user device and determines an edge compute server that is connected, via a base station, to the user device before the handover. Based on receiving the indication of the handover, the EC-AMF server identifies one or more candidate edge compute servers and transfers an application and associated data and context for the application to one of the candidate edge compute servers.

In other aspects, an edge computing-access and mobility server includes one or more processors and a memory comprising instructions for an Edge Computing-Access and Mobility Function (EC-AMF) application, the instructions being executable by the one or more processors to configure the one or more processors to receive an indication of a handover of a user device, and to determine an edge compute server that is connected to the user device via a base station. The instructions are further executable to, based on the reception of the indication of the handover, to identify one or more candidate edge compute servers, and to transfer an application and associated data and context for the application to one of the candidate edge compute servers.

In further aspects, a system includes multiple edge compute servers, each edge compute server being connected to a respective base station in a wireless communication network that includes multiple base stations, an access and mobility server, and an Edge Computing-Access and Mobility (EC-AMF) server. The EC-AMF server receives, from the access and mobility server, an indication of a handover of a user device from a first base station to a second base station in the wireless communication network and determines a first edge compute server that is connected to the user device via the first base station. Based on the reception of the indication of the handover, the EC-AMF server determines a second edge compute server that is connected to the second base station and transfers an application and associated data and context for the application from the first edge compute server to the second edge compute server.

DETAILED DESCRIPTION

Overview

This document describes mobility management of edge computing resources in fifth generation new radio (5G NR) wireless networks. The techniques described enable authorizing user devices to access edge compute servers that execute applications for the user device. The techniques described also enable the migration of applications of user devices between edge compute servers based on mobility changes of user devices in a wireless network, such as handovers of a user device between base stations in the wireless network.

As wireless communication systems evolve to 5G NR technologies, edge computing resources will be deployed at or near base stations to provide lower latency and higher bandwidth to mobile applications by eliminating or reducing communication through the Internet to application servers. In existing wireless access networks, the wireless access network manages a packet data context for each mobile device when the mobile device connects to the wireless access network and as the mobile device is handed off between base stations within the wireless access network. Distributing compute resources to the edge of 5G NR networks can provide lower latencies. Doing so, however, adds complexity to managing these compute resources. Distributing compute resources to the edge of 5G NR networks can also provide mobility management for applications along with data and context for the applications as mobile devices are handed off between the base stations. This again, however, adds complexity.

In aspects, fifth generation new radio edge computing mobility management provides new interfaces, messages, and management functions to support edge computing, to coordinate operations between the edge computing resources, and to manage mobility of applications and application data between edge computing resources in the radio access network.

While features and concepts of the described systems and methods for fifth generation new radio edge computing mobility management can be implemented in any number of different environments, systems, devices, and/or various configurations, aspects of fifth generation new radio edge computing mobility management are described in the context of the following example devices, systems, and configurations.

Example Environment

FIG. 1illustrates an example environment100, which includes a user equipment102(user device102) that communicates with a base station104that acts as a serving cell, (serving cell base station104), through a wireless communication link106(wireless link106). In this example, the user equipment102is implemented as a smartphone. Although illustrated as a smartphone, the user equipment102may be implemented as any suitable computing or electronic device, such as a mobile communication device, a modem, cellular phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart appliance, vehicle-based communication system, and the like. The base station104(e.g., an Evolved Universal Terrestrial Radio Access Network Node B, E-UTRAN Node B, evolved Node B, eNodeB, eNB, Next Generation Node B, gNode B, gNB, and the like) may be implemented in a macrocell, microcell, small cell, picocell, and the like, or any combination thereof.

The base station104communicates with the user equipment102via the wireless link106, which may be implemented as any suitable type of wireless link. The wireless link106can include a downlink of data and control information communicated from the base station104to the user equipment102, an uplink of other data and control information communicated from the user equipment102to the base station104, or both. The wireless link106may include one or more wireless links or bearers implemented using any suitable communication protocol or standard, or combination of communication protocols or standards such as 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE), 5G NR, and so forth.

In aspects, the user equipment102communicates with another base station104(a neighbor base station108), via a wireless link110. The wireless link110may be implemented using the same communication protocol or standard, or a different communication protocol or standard, than the wireless link106. For example, the wireless link106is a 5G NR link and the wireless link110is an LTE link. The base station104, the neighbor base station108, and any additional base stations (not illustrated for clarity) are collectively a Radio Access Network112(RAN112, Evolved Universal Terrestrial Radio Access Network112, E-UTRAN112), which are connected via an Evolved Packet Core114(EPC114) network to form a wireless operator network. The base station104and the neighbor base station108can communicate using an Xn Application Protocol (XnAP), at116, to exchange user-plane and control-plane data. The user equipment102may connect, via the EPC114, to public networks, such as the Internet118to interact with a remote service120.

FIG. 2illustrates an example environment200in which various aspects of fifth generation new radio edge computing mobility management can be implemented. User-plane data flows to and from the serving cell base station104and the neighbor base station108via a serving gateway202in the evolved packet core114, as shown at204and206, respectively. The serving gateway202is connected to the Internet118. For the sake of clarity of illustration, the EPC114, and the connection of the serving gateway202to the Internet118are omitted fromFIG. 2.

An Access and Mobility Function (AMF)208provides control-plane functions such as registration and authentication of user devices102, authorization, mobility management, and the like. The AMF208communicates with the serving cell base station104and the neighbor base station108, as shown at210and212, respectively. The AMF208also communicates with the user device102, via the serving cell base station104, the neighbor base station108, or both.

Edge compute servers214(illustrated as214aand214b) provide edge computing resources for user applications on the user device102. Each edge compute server (ECS)214is connected to a base station using an Xe interface, shown at216. Control-plane functions such as granting access to edge compute server214resources, managing mobility of applications and associated data and context of the applications between edge compute servers214, and the like are managed by an Edge Computing Access and Mobility Function (EC-AMF)218. Control-plane communications between the ECSs214and the EC-AMF218are shown at220. When the user device102is handed over from the serving cell base station104to the neighbor base station108, the application and any data and context associated with the application is transferred from the edge compute server214ato the edge compute server214b. To correctly time the exchange of the application and the application context, the AMF208signals the EC-AMF218, as shown at222. The signaling indicates that there is a handover of the user device102, which triggers the EC-AMF218to transfer the application and data and context associated with the application from the edge compute server214ato the edge compute server214b.

Example Devices

FIG. 3illustrates an example device diagram300of the serving cell base station104, and the neighbor base station108, the edge compute server214, and the EC-AMF218. It should be noted that only the essential features of the serving cell base station104, and the neighbor base station108, the edge compute server214, and the EC-AMF218are illustrated here for the sake of clarity.

The device diagram for the serving cell base station104and the neighbor base station108shown inFIG. 3includes a single network node (e.g., an E-UTRAN Node B or gNode B). The functionality of the serving cell base station104and/or the neighbor base station108may be distributed across multiple network nodes and/or devices and may be distributed in any fashion suitable to perform the functions described herein. The serving cell base station104and the neighbor base station108include antennas302, a radio frequency front end304(RF front end304), one or more transceivers306that includes LTE transceivers, and/or 5G NR transceivers for communicating with the user equipment102. The RF front end304of the serving cell base station104and the neighbor base station108can couple or connect the transceivers306to the antennas302to facilitate various types of wireless communication. The antennas302of the serving cell base station104and the neighbor base station108may include an array of multiple antennas that are configured similarly to or differently from each other. The antennas302and the RF front end304can be tuned to, and/or be tunable to, one or more frequency bands defined by the 3GPP LTE and 5G NR communication standards and implemented by the transceivers306. Additionally, the antennas302, the RF front end304, and/or the transceivers306may be configured to support beamforming, such as Massive-MIMO, for the transmission and reception of communications with the user equipment102.

The serving cell base station104and the neighbor base station108also include processor(s)308and computer-readable storage media310(CRM310). The processor308may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM310may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useful to store device data312of the serving cell base station104and the neighbor base station108. The device data312includes network scheduling data, radio resource management data, applications, and/or an operating system of the serving cell base station104and the neighbor base station108, which are executable by processor(s)308to enable communication with the user equipment102.

CRM310also includes a base station manager314, which, in one implementation, is embodied on CRM310(as shown). Alternately or additionally, the base station manager314may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the serving cell base station104and the neighbor base station108. In at least some aspects, the base station manager314configures the transceivers306for communication with the user equipment102, as well as communication with the EPC114via the EPC Interface316. The serving cell base station104and the neighbor base station108include an Xn interface318, which the base station manager314configures to exchange user-plane and control-plane data between the serving cell base station104and the neighbor base station108, to manage the communication of the serving cell base station104and/or the neighbor base station108with the user equipment102. The serving cell base station104and the neighbor base station108include an Xe interface320, which the base station manager314configures to transfer edge computing applications and associated data and context between edge compute servers214.

The edge compute server214includes processor(s)322and computer-readable storage media324(CRM324). The processor322may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM324may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), hard disk drives, or Flash memory useful to store device data326of the ECS214. The CRM324includes applications328and application data330used by the user device102, and/or an operating system of the ECS214, which are executable by processor(s)322to enable communication with the user equipment102, the base station104and the EC-AMF218.

The ECS214also includes an Xe interface320for communication with the base station for the transfer of edge computing applications to other edge compute servers214via base stations104using the Xn interface318between the base stations104. The edge compute server214includes the EPC interface316for communication of user-plane and control-plane data with the EC-AMF218.

The edge computing access and mobility function218may be provided as a service in the core network, distributed across multiple servers, or embodied on a dedicated server. For example, the edge computing access and mobility function218is illustrated as being embodied on a single server that includes processor(s)332and computer-readable storage media334(CRM334). The processor332may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM334may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), hard disk drives, or Flash memory useful to store device data336of the EC-AMF218. The device data336includes configuration and/or authorization data for user devices102and ECSs214, and/or an operating system of the EC-AMF218, which are executable by processor(s)332to enable communication with the user equipment102, the base station104, and the AMF208. The EC-AMF218also includes the EPC interface316for communication of user-plane and control-plane data with the AMF208and the ECS214.

CRM334also includes a mobility manager338, which, in one implementation, is embodied on CRM334(as shown). Alternately or additionally, the mobility manager338may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the EC-AMF218. In at least some aspects, the mobility manager338configures the ECSs214for communication with the user equipment102.

Edge Computing Configuration and Authorization

The configuration of the edge computing resources that are available to the user device102are communicated to the user device102from either a base station104or via the base station104from the EC-AMF218. The configuration of the edge computing resources is communicated to the user device102in an Edge Computing Configuration (ECC) message. The ECC message may include the location of an edge compute server214, the IP address of the ECS214, resource availability on the ECS214, a cost of using the ECS214, a configuration of the ECS214, and the like. The ECC message may be sent to the user device102periodically or at any time the configuration of the edge computing resources changes, such as after a handover of the user device102, when an ECS214becomes unavailable, when a new ECS214becomes available, and so forth. Additionally or alternatively, multiple edge compute servers214, such as edge compute servers214operated by different service providers, may be available at the base station104. In this alternative, the ECC message may include an identification of the service provider for each ECS214to enable the user device102to select a service provider for edge computing services from the different providers.

To access resources of the ECS214, the user device requests to be authorized to use the ECS214. The user device102sends an Edge Compute Authorization message to an Edge Compute Management Server (ECMS) to request access to resources of the ECS214. The ECMS determines if the requested resources are available and sends an Edge Compute Grant (ECG) message to the user device102indicating that access to the ECS214resources are authorized or denied. If access to the ECS resources are authorized, the ECMS also sends the ECG message to the ECS214to indicate to the ECS214that the user device102is authorized to use the resources of the ECS214. The ECMS may be included in the EC-AMF218, may be remote from the EC-AMF218, or may distributed in any suitable manner.

Edge Computing Mobility Management

The Access and Mobility Function208in 5G NR networks manages functions including network access control, authorization of user devices102, radio resource management, mobility management, and the like. As the user device102moves about an area served by the radio access network112, the user device102is handed over from one base station104to another to maintain communication services for the user device102. With the addition of edge computing, the mobility of applications as well as data and context for those applications also needs to be managed for each handover of the user device102.

In aspects, the EC-AMF218manages compute mobility for edge computing resources associated with user devices102during handovers. The EC-AMF218determines the edge compute server214to which the user device102is connected before a handover is initiated and identifies which edge compute servers214are available to the user device102after the handover. For example, the user device102is connected to the ECS214abefore the handover is initiated. The EC-AMF218receives information from the AMF208about one or more candidate base stations, including the neighbor base station108for a handover. Based on the received candidate base station information, the EC-AMF218identifies which of the edge compute servers214can be used to accept the transfer of applications and associated context for the user device102after the handover.

Optionally or additionally, if the EC-AMF218cannot identify any edge compute servers214to accept the transfer, the EC-AMF218may transfer the applications and associated context and data for the user device102to a default application server in the Internet118. When the EC-AMF218identifies that an ECS214, which can accept the transfer becomes available, the EC-AMF218transfers the applications and associated context for the user device102from the default application server to the newly identified ECS214.

The EC-AMF218receives an indication of the initiation or completion of the handover from the AMF208and the EC-AMF218initiates forwarding the applications and the data and context associated with the applications to another ECS214. The EC-AMF218sends a User Application Context message to the user device102that includes the location of the edge compute server214where the applications and the data and context associated with the applications of the user device102are being transferred. For example, the EC-AMF218receives an indication that the user device102is being handed over from the serving cell base station104to the neighbor base station108. The EC-AMF218transfers the applications and the data and context associated with the applications for the user device102from the ECS214ato the ECS214band sends the User Application Context message, including the location of the ECS214b, to the user device102. Alternatively, the applications and associated data and context can be transferred from the ECS214avia the Xe interface216to the serving cell base station104, which in turn transfers the applications and associated data and context via the Xn interface318to the neighbor base station108that forwards the applications and associated data and context via the Xe interface216to the ECS214b.

In another aspect, when the EC-AMF218determines there will be a handover of the user device102, the EC-AMF218can initiate the transfer a copy of the applications from the ECS214currently in use by the user device102to one or more candidate ECSs214before the handover. When the handover is initiated or completed, the EC-AMF218transfers the context and data for the application to the ECS214that is connected to the base station104that is receiving the handover of the user device102. By transferring a copy of the application before the handover the amount of data transferred during the handover is reduced and the latency of the transfer of the application and associated context for the user device102is reduced as well. For example, the user device102is connected to the ECS214abefore a handover is initiated. The EC-AMF218receives information about one or more candidate base stations for a handover from the AMF208, including the neighbor base station108. Based on the received candidate base station information, the EC-AMF218identifies which of the edge compute servers214can be used to accept the transfer of applications and associated data and context for the user device102after the handover. The EC-AMF218transfers copies of the application to each of the candidate edge compute servers214. The EC-AMF218receives an indication from the AMF208that the user device102is being handed over to the neighbor base station108and the EC-AMF218transfers the context and data for the application to the ECS214b.

In another aspect, the EC-AMF218sends information about the status of the transfer to the user device102in an Application State Message. The application State Message may include an indication that the transfer is in progress, completed, delayed, failed, and so forth. For example, when the time required for transfer of the application and the associated data and context is longer than the time required to complete a handover, the EC-AMF218sends a first Application State Message to the user device102indicating that the transfer is in progress. When the transfer is complete the EC-AMF218sends a second Application State Message to the user device102indicating that the transfer is complete.

Example Methods

Example methods400and500are described with reference toFIGS. 4 and 5in accordance with one or more aspects of fifth generation new radio edge computing mobility management. Generally, any of the components, modules, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods may be described in the general context of executable instructions stored on computer-readable storage memory that is local and/or remote to a computer processing system, and implementations can include software applications, programs, functions, and the like. Alternatively or in addition, any of the functionality described herein can be performed, at least in part, by one or more hardware logic components, such as, and without limitation, Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SoCs), Complex Programmable Logic Devices (CPLDs), and the like.

FIG. 4illustrates example method(s)400of fifth generation new radio edge computing mobility management as generally related to authorizing edge computing resources for the user device102. The order in which the method blocks are described are not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement a method or an alternate method.

At block402, an edge compute management server receives an authorization request from a user device for authorization to use resources of an edge compute server. For example, an edge compute management server included in the EC-AMF218receives an edge compute authorization message from the user device102that request authorization to use resources of the ECS214.

At block404, the edge compute management server determines if the user device is authorized to access the resources of the edge compute server. For example, the edge compute management server included in the EC-AMF218determines if the user equipment102is authorized to use the resources of the ECS214.

At block406, the edge compute management server sends an edge compute grant message to the user device that indicates whether access to the resources of the edge compute server are authorized or denied. For example, the edge compute management server included in the EC-AMF218sends an edge compute grant message to the user device102indicating that access to the resources of the ECS214are authorized or denied.

Optionally at block408, if the user device is authorized to access the resources of the edge compute server, the edge compute management server sends the edge compute grant message to the edge compute server. For example, the edge compute management server included in the EC-AMF218sends the edge compute grant message to the ECS214indicating that the user device102has been granted access to the ECS214.

FIG. 5illustrates example method(s)500of fifth generation new radio edge computing mobility management as generally related to mobility management of edge computing resources for the user device102by the EC-AMF218. The order in which the method blocks are described are not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement a method, or an alternate method.

At block502, an EC-AMF server receives an indication of a handover of a user device. For example, the EC-AMF218receives an indication of a handover of the user device102between base stations104in the wireless communication network from the AMF208. The received indication may include an identifier of the current base station104that provides the serving cell for the user device102, and another identifier that identifies the neighbor base station108that is a candidate to receive the user device102during the handover.

At block504, the EC-AMF server determines an edge compute server that is connected to the user device before the handover. For example, using the identifier of the current base station104, the EC-AMF218determines that the ECS214ais connected to the user device102via the base station104.

At block506, based on the reception of the indication of the handover, the EC-AMF server identifies a candidate edge compute server. For example, using the other identifier of the neighbor base station108, the EC-AMF218identifies that ECS214bis connected to the neighbor base station108.

At block508, the EC-AMF server transfers an application and associated data and context for the application to the candidate edge compute server. For example, the EC-AMF218transfers the application and associated data and context from the ECS214ato the ECS214b.

Although aspects of fifth generation new radio edge computing mobility management have been described in language specific to features and/or methods, the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations of fifth generation new radio edge computing mobility management, and other equivalent features and methods are intended to be within the scope of the appended claims. Further, various different aspects are described, and it is to be appreciated that each described aspect can be implemented independently or in connection with one or more other described aspects.