HYPERSCALE CLOUD PROVIDER (HCP) EDGE INTERWORKING WITH MULTIPLE PROTOCOL DATA UNIT (PDU) SESSIONS

A method performed by one or more network devices of a cloud platform for providing interworking between the cloud platform and a communication service platform. The method includes receiving, from a user of the cloud platform, input regarding desired characteristics for an edge cloud, providing, via an application programming interface, an indication of the desired characteristics for the edge cloud to the communication service platform, receiving, from the communication service platform via the application programing interface, an indication of a set of edge locations that is capable of supporting the desired characteristics for the edge cloud, provisioning an edge subnet at each edge location in the set of edge locations, and making the edge subnets visible to the user of the cloud platform.

TECHNICAL FIELD

Embodiments of the invention relate to the field of communication networks, and more specifically, to providing interworking between a cloud platform and a communication service platform.

BACKGROUND

Cloud computing refers to the on-demand delivery of computing resources, typically over a network (e.g., the Internet) with pay-as-you-go pricing. For example, instead of buying, owning, and maintaining physical data centers and servers, a user may access computing resources such as computing power, storage, and databases, on an as-needed basis from a cloud provider.

A communication service provider/platform (CSP) may offer telecommunications services or some combination of information and media services, content, entertainment and application services over networks, leveraging the network infrastructure as a rich, functional platform. A CSP may own and/or operate a mobile network such as a Fourth Generation (4G) Long-term Evolution (LTE) mobile network and/or a Fifth Generation (5G) mobile network.

A hyperscale cloud platform (HCP) is a multi-tenant platform where computing, network, and storage resources can be accessed by multiple tenants on demand. HCP developer ecosystems are potent channels for communication service providers/platforms to monetize their mobile networks (e.g., 5G mobile network) assets. For example, communication service providers/platforms may deploy HCP edge infrastructures inside their mobile network premises to provide mobile edge computing services (an example of this is Amazon Web Services (AWS) Wavelength).

Some communication service providers/platforms are planning to integrate with HCPs to monetize the capabilities provided by their mobile networks. HCP edge infrastructures may enable developers to deploy workloads on the “edge” of mobile networks, thereby reducing latency between client applications running on (mobile) client devices and server applications.

An application developer may use an HCP portal (e.g., an AWS virtual private cloud (VPC) page) to create a virtual private cloud. A virtual private cloud is a virtual network provided by a cloud platform that is logically isolated from other virtual networks provided by the cloud platform. The application developer may provision subnets in the virtual private cloud at various edge locations within a mobile network to enable low latency edge computing. A subnet may be a range of IP addresses in the virtual private cloud.

Currently, application developers have to manually select the edge locations when configuring their virtual private clouds. This approach is viable when the number of edge locations is small. However, the number of edge locations in mobile networks is expected to increase significantly in the coming years. As the number of edge locations increase, it will be possible to deploy different applications having different latency and availability demands in different subsets of edge locations. In these scenarios, selecting the appropriate edge locations to fulfill the application demands might be difficult.

SUMMARY

A method performed by one or more network devices of a cloud platform for providing interworking between the cloud platform and a communication service platform. The method includes receiving, from a user of the cloud platform, input regarding desired characteristics for an edge cloud, providing, via an application programming interface, an indication of the desired characteristics for the edge cloud to the communication service platform, receiving, from the communication service platform via the application programing interface, an indication of a set of edge locations that is capable of supporting the desired characteristics for the edge cloud, provisioning an edge subnet at each edge location in the set of edge locations, and making the edge subnets visible to the user of the cloud platform.

A set of non-transitory machine-readable media having computer code stored therein, which when executed by one or more processors of one or more network devices of a cloud platform, causes the one or more network devices to perform operations for providing interworking between the cloud platform and a communication service platform. The operations include receiving, from a user of the cloud platform, input regarding desired characteristics for an edge cloud, providing, via an application programming interface, an indication of the desired characteristics for the edge cloud to the communication service platform, receiving, from the communication service platform via the application programing interface, an indication of a set of edge locations that is capable of supporting the desired characteristics for the edge cloud, provisioning an edge subnet at each edge location in the set of edge locations, and making the edge subnets visible to the user of the cloud platform.

A method performed by one or more network devices of a communication service platform for providing interworking between a cloud platform and the communication service platform. The method includes receiving, from the cloud platform via an application programming interface, an indication of desired characteristics for an edge cloud, wherein the desired characteristics for the edge cloud were provided to the cloud platform by a user of the cloud platform, determining a network slice that is capable of supporting the desired characteristics for the edge cloud, determining a set of edge locations associated with the network slice, creating a user equipment route selection policy (URSP) rule that associates a traffic descriptor with the network slice, and providing, to the cloud platform via the application programming interface, an indication of the set of edge locations.

A set of non-transitory machine-readable media having computer code stored therein, which when executed by one or more processors of one or more network devices of a communication service platform, causes the one or more network device to perform operations for providing interworking between a cloud platform and the communication service platform. The operations include receiving, from the cloud platform via an application programming interface, an indication of desired characteristics for an edge cloud, wherein the desired characteristics for the edge cloud were provided to the cloud platform by a user of the cloud platform, determining a network slice that is capable of supporting the desired characteristics for the edge cloud, determining a set of edge locations associated with the network slice, creating a user equipment route selection policy (URSP) rule that associates a traffic descriptor with the network slice, and providing, to the cloud platform via the application programming interface, an indication of the set of edge locations.

DETAILED DESCRIPTION

An electronic device stores and transmits (internally and/or with other electronic devices over a network) code (which is composed of software instructions and which is sometimes referred to as computer program code or a computer program) and/or data using machine-readable media (also called computer-readable media), such as machine-readable storage media (e.g., magnetic disks, optical disks, solid state drives, read only memory (ROM), flash memory devices, phase change memory) and machine-readable transmission media (also called a carrier) (e.g., electrical, optical, radio, acoustical or other form of propagated signals—such as carrier waves, infrared signals). Thus, an electronic device (e.g., a computer) includes hardware and software, such as a set of one or more processors (e.g., wherein a processor is a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, other electronic circuitry, a combination of one or more of the preceding) coupled to one or more machine-readable storage media to store code for execution on the set of processors and/or to store data. For instance, an electronic device may include non-volatile memory containing the code since the non-volatile memory can persist code/data even when the electronic device is turned off (when power is removed), and while the electronic device is turned on that part of the code that is to be executed by the processor(s) of that electronic device is typically copied from the slower non-volatile memory into volatile memory (e.g., dynamic random access memory (DRAM), static random access memory (SRAM)) of that electronic device. Typical electronic devices also include a set of one or more physical network interface(s) (NI(s)) to establish network connections (to transmit and/or receive code and/or data using propagating signals) with other electronic devices. For example, the set of physical NIs (or the set of physical NI(s) in combination with the set of processors executing code) may perform any formatting, coding, or translating to allow the electronic device to send and receive data whether over a wired and/or a wireless connection. In some embodiments, a physical NI may comprise radio circuitry capable of receiving data from other electronic devices over a wireless connection and/or sending data out to other devices via a wireless connection. This radio circuitry may include transmitter(s), receiver(s), and/or transceiver(s) suitable for radiofrequency communication. The radio circuitry may convert digital data into a radio signal having the appropriate parameters (e.g., frequency, timing, channel, bandwidth, etc.). The radio signal may then be transmitted via antennas to the appropriate recipient(s). In some embodiments, the set of physical NI(s) may comprise network interface controller(s) (NICs), also known as a network interface card, network adapter, or local area network (LAN) adapter. The NIC(s) may facilitate in connecting the electronic device to other electronic devices allowing them to communicate via wire through plugging in a cable to a physical port connected to a NIC. One or more parts of an embodiment of the invention may be implemented using different combinations of software, firmware, and/or hardware.

As mentioned above, manual selection of edge locations is a viable approach for cloud users designing virtual private clouds when the number of edge locations is small. However, the number of edge locations in mobile networks is expected to increase significantly in the coming years. As the number of edge locations increase, it will be possible to deploy different applications having different latency and availability demands in different subsets of edge locations. In these cases, selecting the appropriate edge locations that can fulfill the different application demands might not be straightforward.

As the number of edge locations increase, manual selection of edge locations will not be practical. An application might not need to be deployed at every edge location. The number of edge locations at which the application needs to be deployed may depend on the requirements of the application (e.g., latency requirements and geographics). It is foreseen by the present disclosure that application developers will need assistance in determining the edge locations at which to provision edge subnets for their virtual private clouds depending on application requirements.

To select the appropriate edge locations, an application developer would need to know the actual network performance characteristics of a large number of edge locations (e.g., using network measurement tools in the application) and then select/change the edge locations being used by the application (e.g., explicitly in the application) based on the network performance characteristics, which would unduly complicate the application. Also, communication service providers/platforms and hyperscale cloud providers/platforms might not want to share such detailed information regarding their infrastructures with application developers or with each other.

Embodiments disclosed herein provide solutions to these or other challenges. Embodiments leverage network slicing and multiple protocol data unit (PDU) sessions to fulfill service level agreements (SLA) and provide traffic steering to edge locations. From a workflow point of view, the approaches described herein can be considered as “VPC design-time SLA fulfilment” approaches that determine the edge locations at which to provision edge subnets for a virtual private cloud in a manner that specified SLAs are met. Then any workload deployed in such edge subnets may enjoy the specified SLAs. Embodiments achieve this using active interaction between the communication service provider/platform and cloud provider/platform.

According to some embodiments, a cloud platform receives user input (from a user of the cloud platform) regarding the desired characteristics for an edge cloud (e.g., via user selection of a “SLA tier” (e.g., “Bronze”/sub-100 millisecond latency, “Silver”/sub-50 millisecond latency, or “Gold”/sub-20 millisecond latency) and a geographic area (e.g., Texas)). The cloud platform provides an indication of the desired characteristics for the edge cloud to the communication service platform via an application programming interface (API). Responsive to receiving the indication of the desired characteristics for the edge cloud, the communication service platform determines a network slice that is capable of supporting the desired characteristics of the edge cloud (e.g., the specified SLA and geographic area). The communication service platform determines a set of edge locations associated with the network slice, creates a user equipment route selection policy (URSP) rule that associates a traffic descriptor with the network slice, and provides an indication of the set of edge locations to the cloud platform via the API. Responsive to receiving the indication of the set of edge locations, the cloud platform provisions an edge subnet at each edge location in the set of edge locations and makes the edge subnets visible to the cloud user. The cloud user may then deploy an application in the edge subnets.

In an embodiment, the traffic descriptor is a data network name (DNN). In such an embodiment, the communication service platform may provide the DNN to the cloud platform via the API. The cloud platform may then provide this DNN to the cloud user (e.g., display the DNN to the user via a graphical user interface (GUI)). The cloud user may use the DNN as a parameter in the client application for setting up the network socket to the application deployed in the edge cloud. A URSP mechanism may determine the network slice associated with the DNN and establish a PDU session for the client application that the client application can use to communicate with the application deployed in the edge cloud using the network slice.

In another embodiment, the traffic descriptor is a fully qualified domain name (FQDN) associated with the application deployed in the edge cloud. In such an embodiment, a URSP mechanism may determine the network slice associated with the FQDN and establish a PDU session for the client application that the client application can use to communicate with the application deployed in the edge cloud using the network slice.

Embodiments provide one or more advantages over existing solutions. An advantage of embodiments disclosed herein is that they provide simplicity for an application developer when configuring an edge cloud in which to deploy an application. The application developer does not have to be aware of the edge locations or network slicing, and does not have to perform network measurements to select the appropriate edge locations and network slices for an application.

Also, an advantage of embodiments is that they allow the application developer to rely on existing cloud platform workflows and best practices. For example, the application developer may design a virtual private cloud and deploy workloads into them, as usual. Also, the application developer may continue to use domain name system (DNS) and FQDNs to allow client applications to reach their applications, as usual.

Also, an advantage of embodiments is that they allow the communication service platform to hide away complexities and sensitive infrastructure information. The communication service platform does not have to openly expose detailed information about edge locations to application developers. Also, the communication service platform does not have to expose network slicing and edge location related APIs directly to application developers. Also, the communication service platform may optimize utilization by implementing load balancing mechanisms under the hood (e.g., using dynamically generated network slices, as will be described in additional detail herein).

Also, an advantage of embodiments is that they allow cloud platforms to hide away complexities and sensitive infrastructure information. A cloud platform does not have to directly share utilization information with the application developer or the communication service platform. Also, the cloud platform may leverage the existing developer ecosystem competence to provide a seamless developer experience. Embodiments are described in further detail herein below with reference to the accompanying figures.

FIG. 1is a diagram showing an environment in which interworking between a cloud platform and a communication service platform can be implemented, according to some embodiments. As shown in the diagram, the environment includes a communication service platform network (CSP NW)110, a cloud platform120, an interworking logic130, a virtual private cloud database (VPC DB)140, operation support systems (OSS)/probes160, and a user equipment (UE)170.

The communication service platform network110may offer communication services to users/subscribers. In an embodiment, the communication service platform network110is a Fourth Generation (4G) Long-term Evolution (LTE) mobile network and/or a Fifth Generation (5G) mobile network. The communication service platform network110may include multiple edge locations112(e.g., edge point of presence (PoP)). For example, as shown in the diagram, the communication service platform network110includes edge locations112A-G.

The cloud platform120may include a collection of hardware and software resources that enable cloud computing. For example, the cloud platform120may include computing resources, networking resources, and/or storage resources, as well as an interface (e.g., a GUI) for cloud users to access virtualized resources. In an embodiment, the cloud platform120is a hyperscale cloud platform (HCP).

The UE170may be a network device that can communicate wirelessly with the communication service platform network110. The UE170may be, for example, a mobile phone, a laptop, or similar device. The UE170may communicate wirelessly with the communication service platform network110to access an application deployed in the cloud platform120and/or the communication service platform network110(e.g., deployed at one of the edge locations112A-G of the communication service platform network110).

As shown in the diagram, the cloud platform120includes a virtual private cloud (VPC) management interface125(also referred to herein simply as “management interface”). A cloud user (e.g., an application developer) may use the management interface125(e.g., which might be implemented as a GUI that the cloud user accesses over a network) to create a virtual private edge cloud in the communication service platform network110and deploy an application in that edge cloud. In an embodiment, a cloud user provides input regarding the desired characteristics for an edge cloud to the cloud platform120via the management interface125. The desired characteristics may include geographic location (e.g., a U.S. state (e.g., Texas) or metropolitan area), mobile operator (“all” could be an option), latency tier (sub-50 millisecond, sub-20 millisecond, sub-10 millisecond, etc.), guaranteed bit rate (10 Mbps, 20 Mbps, 50 Mbps, etc.), high availability (non-redundant could provide 99.5% availability and redundant pairs could provide 99.95% availability), mobility options and session continuity (e.g., session and service continuity (SSC) modes 2, 3, 4). The cloud platform120may then provide this user input to the interworking logic130(e.g., via an application programming interface (API) exposed by the interworking logic130towards the cloud platform120). The interworking logic130may be a component of the communication service platform that provides interworking between the cloud platform120and the communication service platform. The interworking logic130may be implemented by one or more network devices of the communication service platform.

Responsive to receiving the desired characteristics for the edge cloud, the interworking logic130may send a request to the OSS/probes160to provide a network slice115that is capable of supporting the desired characteristics. Network slicing is a network architecture concept that enables the multiplexing of virtualized and independent logical networks on the same physical network infrastructure. Each network slice may be a logically isolated end-to-end network tailored to fulfill diverse requirements requested by a particular application.

In an embodiment, the communication service platform has preexisting network slices115A-N. In an embodiment, the network slices115A-N are preconfigured according to service level agreements (SLAs) (e.g., to fulfill different latency requirements such as sub-50 millisecond, sub-20 millisecond, and sub-10 millisecond tiers). Each network slice115may be associated with a set of edge locations112in the communication service platform network110. For example, as shown in the diagram, network slice115N is associated with edge locations112A,112E, and112G. Each edge location112may implement a user plane function (UPF)113(or other type of user/data plane component) or be geographically proximate to a UPF113. For example, as shown in the diagram, edge locations112A,112B,112C,112D,112E,112F, and112G implement (or are otherwise geographically proximate to) UPFs113A,113B,113C,113D,113E,113F, and113G, respectively. In general, a network slice115fulfilling a higher latency requirement (e.g., sub-50 millisecond latency) will typically be associated with a smaller number of UPFs/edge locations113/112compared to a network slice115fulfilling a lower latency requirement (e.g., sub-10 millisecond latency) in a given geography. The UPF selection policy for a network slice115may be configured such that UE170traffic terminates on the network slice's closest UPF113.

Responsive to receiving the request from the interworking logic130to provide a network slice115, the OSS/probes160may either select a preexisting network slice115that is capable of supporting the desired characteristics (referred to herein as a “static” network slice selection approach) or generate a new network slice115that is capable of supporting the desired characteristics (referred to herein as a “dynamic” network slice generation approach).

When using the static network slice selection approach, multiple users may share the same network slice115but it might be desirable to provide different bit rates, priority levels, and/or other type of quality of service (QoS) for different users sharing the same network slice115. Thus, in an embodiment, the interworking logic130determines the QoS API parameters for a cloud user.

When using the dynamic network slice generation approach, the OSS/probes160may generate a new network slice115that is capable of supporting the desired characteristics provided by the cloud user based on network status information and/or a network slice template (e.g., there could be templates for different latency tiers). In an embodiment, the communication service platform maintains a network status database150that stores various network status information such as latency information and network capacity utilization information for UPFs113and/or edge locations112and the availability status of the edge locations112(e.g., whether there are network failures) for network slices115.

The latency information may include latency estimates from tracking areas/cells to (relevant) UPFs113and/or latency estimates from UPFs to113interconnected edge nodes inside and/or outside the network infrastructure (e.g., multiple cloud platform nodes and external colocation centers with the cloud platform120and third-party provider (3PP) nodes (e.g., other edge platform providers beyond cloud platforms such as content distribution networking (CDN) players)). Latency measurements may be obtained by the OSS/network probes160or other suitable means. If real-time latency measurements are not possible or practical to obtain, a static database can be used based on dedicated (“day zero”) or historical latency measurements. Network capacities may be measured using UPFs113and/or other network gear functions or by dedicated probes. Although the diagram shows the network status database150as being separate from the OSS/probes160, in some embodiments, the network status database150is integrated with the OSS/probes160. In an embodiment, traffic patterns that are specific to the cloud user are determined/collected and stored in the network status database150to help optimize edge location selection in case a cloud user expands its existing solution.

Once the OSS/probes160selects or generates a network slice115, the OSS/probes160may provide information about the selected or created network slice115to the interworking logic130. The interworking logic130may determine the set of edge locations112associated with the network slice115and provide an indication of the set of edge locations112associated with the network slice115to the cloud platform120. In an embodiment, the interworking logic130“negotiates” (e.g., at an API level) with the cloud platform120regarding the set of edge locations112until an agreement is reached.

Responsive to receiving the indication of the set of edge locations112associated with the network slice115, the cloud platform120may provision an edge subnet at each edge location in the set of edge locations112and make these edge subnets visible to the cloud user (e.g., such that the edge subnets are visible to the cloud user in the management interface125). The cloud user may then use the management interface125to deploy an application in the edge subnets (which effectively deploys the application in the edge cloud).

The cloud user may create/update a DNS record for a FQDN associated with the application it deployed in the edge cloud. The DNS record may include the IP addresses of the application instances deployed in the edge cloud. The DNS record may be created in the cloud platform's120DNS service.

In an embodiment, a URSP rule is created that associates a traffic descriptor with the selected/created network slice115. In an embodiment, the traffic descriptor is a data network name (DNN). In such an embodiment, the interworking logic130(or other component of the communication service platform) may create the URSP rule in the communication service platform when the network slice115is selected/created. In an embodiment, the interworking logic130provides the DNN associated with the selected/created network slice115to the cloud platform120(e.g., together with the indication of the set of edge locations112associated with the network slice115). The cloud platform120may provide this DNN to the cloud user (e.g., by displaying the DNN in the management interface125). As will be described in further detail herein below, the cloud user may use the DNN as a parameter in a client application for setting up the network socket to the application deployed in the edge cloud. In an embodiment, the traffic descriptor is a FQDN associated with the application. In such an embodiment, the DNS service of the cloud platform120may interact with the communication service platform to create the URSP rule in the communication service platform (e.g., at the time when the DNS record for the FQDN is created in the DNS service of the cloud platform120).

In an embodiment, the interworking logic130creates a record for the cloud user in the VPC database140. The record for the cloud user may indicate the network slice115that was selected/created for the cloud user, which edge locations112are associated with the network slice115, the URSP rule, and/or QoS parameters. This record may be used for Internet Protocol (IP) address allocation and routing requests API for the cloud platform120.

For network slicing to take effect, the UE170implementing the client application should support multiple PDU sessions (e.g., different PDU sessions for different network slices115) and have downloaded the relevant URSP configurations. Since the cloud user might not know which UEs170will access its edge cloud application in advance, a UE bootstrapping mechanism may be provided. The UE bootstrapping mechanism may be implemented by introducing a “UE bootstrapping API” pointing to a bootstrap server uniform resource locator (URL) which the client application would invoke at the first time the edge cloud application is accessed (e.g., during authentication stage).

The bootstrap server may call the “AF Influence PCF decisions for URSP” API to trigger a policy control function (PCF) configuration and a UE configuration update to push the relevant URSP rule (e.g., that associates the DNN or FQDN with the selected/generated network slice115) to the UE170accessing the edge cloud application. The bootstrap server may extract the UE IP address to parameterize the API (the “UE Information API” can also be used). With the relevant URSP rule downloaded, the UE170(and specifically the client application implemented by the UE170) can access the edge cloud application via the selected/generated network slice115and the additional PDU session. In an embodiment, the bootstrap server may use a similar mechanism to trigger dynamic QoS configuration for the UE170(the pre-existing network slices115may be shared resources so the guaranteed bit rate may be secured with 5G QoS identifier (5QI) leveraging the dynamic QoS API—for each network slice115the appropriate quality classes may be preconfigured according to bandwidth tiers (e.g., 10 Mbps, 20 Mbps, 50 Mbps, etc.)).

The cloud user may configure the client application to use the specified DNN/alias in the IP socket setup API to set up the connectivity towards the closest edge server. Another option to provide UE bootstrapping is to integrate the UE bootstrapping API call into the client IP socket setup API (to download the relevant URSP rule(s)). If the IP socket configuration is not possible with the specified DNN/alias first, the reason might be the lack of UE bootstrapping which can then be triggered.

Thus, the interworking logic130allows the cloud platform120to interact with the communication service platform to determine the edge locations112at which to provision edge subnets to achieve the desired characteristics for the edge cloud. A UE bootstrapping mechanism may configure the UEs170implementing a client application to access an application deployed in the edge cloud using the appropriate network slice115(with UE traffic terminating at the closest UPF113to the UE170).

While a certain arrangement of components is shown in the diagram to illustrate a particular embodiment, it should be understood that other embodiments may include different components and/or have a different arrangement of components to achieve the same/similar functionality.

FIG. 2is a diagram showing network slice configurations, according to some embodiments. Three network slices, namely network slice115A, network slice115B, and network slice115C, are shown in the diagram. Different network slices115may provide different levels of latency. In general, a network slice115that is associated with more edge locations112(or UPFs113) provides lower latency. For example, network slice115A provides sub-80 millisecond latency and is associated with a single edge location112E (e.g., implementing UPF113E), network slice115B provides sub-50 millisecond latency and is associated with edge locations112B,112E, and112G (e.g., implementing UPFs113B,113E, and113G, respectively), and network slice115C provides sub-20 millisecond latency and is associated with edge locations112A,112B,112C,112D,112E,112F,112G,112H, and112I (e.g., implementing UPFs113A,113B,113C,113D,113E,113F,113G,113H, and113I, respectively).

A UE170may have multiple PDU sessions175that are each associated with a different network slice115. For example, as shown in the diagram, the UE170may have a PDU session175A associated with network slice115A and a PDU session175B associated with network slice115C. The UE170may use PDU session175A to communicate using network slice115A and use PDU session175B to communicate using network slice115C.

FIG. 3Ais a diagram showing component interactions for providing interworking between a cloud platform and a communication service platform using a static network slice selection approach, according to some embodiments.

As shown in the diagram, at operation A1, a cloud user provides desired characteristics for an edge cloud to the cloud platform120(e.g., the user selects the sub-50 millisecond latency tier for the Texas geography). At operation A2, the cloud platform provides the desired characteristics to the interworking logic130(e.g., via an API exposed by the interworking logic130towards the cloud platform). At operation A3, the interworking logic130sends a request to the OSS160to select a network slice that is capable of supporting the desired characteristics. In response, the OSS160selects the network slice (from a set of preexisting network slices) and provides information regarding the selected network slice to the interworking logic130. At operation A4, the interworking logic130creates a record for the cloud user in the VPC database140. The record may include information regarding the network slice that was selected, which edge locations are associated with the network slice, a URSP rule, and/or QoS parameters. At operation A5, the interworking logic130provides a set of edge locations associated with the network slice (and optionally a DNN) to the cloud platform120(e.g., via the API). At operation A6, the cloud platform120provisions an edge subnet at each edge location in the set of edge locations. At operation A7, the cloud platform makes the edge subnets visible to the user (and optionally provides the DNN to the user) (e.g., via the management interface125). At operation A8, the cloud user deploys an application in the edge subnets (e.g., as auto scale groups) to create an “edge cloud” application. At operation A9, the user creates a DNS record for a FQDN associated with the application.

In an embodiment, the cloud user configures the client network socket setup in the client application to use the provided DNN (or alias) as a parameter along with the application's FQDN. A UE bootstrapping mechanism and URSP mechanism may be used to set up the PDU session in the UE, as described above. The UE's network traffic pertaining to the client application may be routed via the closest UPF within the network slice according to the routing policy. The cloud platform's DNS service (e.g., which may be implemented by a proxy in a cloud platform edge node) resolves the FQDN and returns the IP address of the application deployed in the edge cloud. No smart DNS integration with the network is necessary.

FIG. 3Bis a diagram showing component interactions for providing interworking between a cloud platform and a communication service platform using a dynamic network slice generation approach, according to some embodiments.

With this approach, there may be SLA-specific templates for network slices (e.g., for sub-50 millisecond latency, sub-20 millisecond latency, sub-10 millisecond latency, etc.) but the network slices are not provisioned up front as with the static network slice selection approach. Instead, the templates may be used to generate and provision network slices on demand. This enables dynamic on-the-fly selection of UPFs at edge locations that leverage real-time and/or historical network statistics. This may also allow for “negotiating” with the cloud platform regarding edge locations (e.g., on an API level).

As shown in the diagram, at operation B1, a cloud user provides desired characteristics for an edge cloud to the cloud platform120(e.g., the user selects the sub-50 millisecond latency tier for the Texas geography). At operation B2, the cloud platform provides the desired characteristics to the interworking logic130(e.g., via an API exposed by the interworking logic130towards the cloud platform). At operation B3, the interworking logic130sends a request to the OSS160to generate a new network slice that is capable of supporting the desired characteristics. In response, the OSS160generates a new network slice using a template and real time and/or historical network statistics data (which may be accessed from the network status database150). Optionally, the communication service platform provides multiple options to the cloud platform120to choose from (to allow for “negotiations”), and then generates the new network slice based on the result of the negotiation with the cloud platform120. The OSS160may provide information regarding the newly generated network slice to the interworking logic130. At operation B4, the interworking logic130creates a record for the cloud user in the VPC database140. The record may include information regarding the network slice that was generated, which edge locations are associated with the network slice, a URSP rule, and/or QoS parameters. At operation B5, the interworking logic130provides a set of edge locations associated with the network slice (and optionally a DNN) to the cloud platform120(e.g., via the API). At operation B6, the cloud platform120provisions an edge subnet at each edge location in the set of edge locations. At operation B7, the cloud platform makes the edge subnets visible to the user (and optionally provides the DNN to the user) (e.g., via the management interface125). At operation B8, the cloud user deploys an application in the edge subnets (e.g., as auto scale groups) to create an “edge cloud” application. At operation B9, the cloud user creates a DNS record for a FQDN associated with the application.

The configuration of the UE and client application may be the same or similar to that described above with regard toFIG. 3A, and thus is not repeated here for sake of conciseness.

FIG. 4is a flow diagram showing a method performed by a cloud platform for providing interworking between the cloud platform and a communication service platform, according to some embodiments. The method may be implemented using hardware, software, or a combination thereof.

The operations in the flow diagrams will be described with reference to the exemplary embodiments of the other figures. However, it should be understood that the operations of the flow diagrams can be performed by embodiments of the invention other than those discussed with reference to the other figures, and the embodiments of the invention discussed with reference to these other figures can perform operations different than those discussed with reference to the flow diagrams.

At operation410, the cloud platform receives, from a user of the cloud platform, input regarding desired characteristics for an edge cloud. In an embodiment, the desired characteristics for the edge cloud include one or more of: a desired geographical location, a desired latency tier, and a desired bit rate tier.

At operation420, the cloud platform provides, via an API, an indication of the desired characteristics for the edge cloud to the communication service platform.

At operation430, the cloud platform receives, from the communication service platform via the API, an indication of a set of edge locations that is capable of supporting the desired characteristics for the edge cloud. In an embodiment, the cloud platform also receives from the communication service platform via the API, a DNN and provides the DNN to the user of the cloud platform.

At operation440, the cloud platform provisions an edge subnet at each edge location in the set of edge locations.

At operation450, the cloud platform makes the edge subnets visible to the user of the cloud platform.

In an embodiment, the cloud platform creates a DNS record for a FQDN associated with an application to be deployed in the edge cloud. In an embodiment, the cloud platform provides the FQDN associated with the application to the communication service platform, wherein the communication service platform is to create a URSP rule that associates the FQDN with a network slice associated with the set of edge locations. In an embodiment, the cloud platform provides a bootstrapping mechanism that is to cause a URSP rule to be pushed to a UE when the UE accesses an application deployed in the edge cloud. With the bootstrapping mechanism in place, the user of the cloud platform (e.g., an application developer) does not need to specify the user subscriptions in advance—it is enough if the client application (implemented by the UE) authenticates itself towards a bootstrap server (e.g., using the credentials associated with a particular edge configuration and/or network slice) and that is sufficient to identify the appropriate URSP rule to be pushed to the UE.

FIG. 5is a flow diagram showing a method performed by a communication service platform for providing interworking between a cloud platform and the communication service platform, according to some embodiments. The method may be implemented using hardware, software, or a combination thereof.

At operation510, the communication service platform receives, from the cloud platform, an indication of desired characteristics for an edge cloud, wherein the desired characteristics for the edge cloud were provided to the cloud platform by a user of the cloud platform.

At operation520, the communication service platform determines a network slice that is capable of supporting the desired characteristics for the edge cloud. In an embodiment, the network slice is determined based on selecting the network slice from a plurality of existing network slices. In an embodiment, the network slice is determined based on generating a new network slice. In an embodiment, the new network slice is generated based on network status information obtained from a network status database and/or a network slice template.

At operation530, the communication service platform determines a set of edge locations associated with the edge cloud.

At operation540, the communication service platform creates a URSP rule that associates a traffic descriptor with the network slice. In an embodiment, the traffic descriptor is a DNN. In an embodiment, the communication service platform provides the DNN to the cloud platform via the API. In an embodiment, the traffic descriptor is a FQDN (that is associated with an application that is deployed or to be deployed in the edge cloud).

At operation550, the communication service platform provides, to the cloud platform via the API, an indication of the set of edge locations.

FIG. 6is a diagram showing an example of a communication system, according to some embodiments.

In the example, the communication system600includes a telecommunication network602that includes an access network604, such as a radio access network (RAN), and a core network606, which includes one or more core network nodes608. The access network604includes one or more access network nodes, such as network nodes610aand610b(one or more of which may be generally referred to as network nodes610), or any other similar 3rdGeneration Partnership Project (3GPP) access node or non-3GPP access point. The network nodes610facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs612a,612b,612c, and612d(one or more of which may be generally referred to as UEs612) to the core network606over one or more wireless connections.

The UEs612may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes610and other communication devices. Similarly, the network nodes610are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs612and/or with other network nodes or equipment in the telecommunication network602to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network602.

In the depicted example, the core network606connects the network nodes610to one or more hosts, such as host616. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network606includes one more core network nodes (e.g., core network node608) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node608. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

The host616may be under the ownership or control of a service provider other than an operator or provider of the access network604and/or the telecommunication network602, and may be operated by the service provider or on behalf of the service provider. The host616may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

In some examples, the telecommunication network602is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network602may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network602. For example, the telecommunications network602may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs.

In the example, the hub614communicates with the access network604to facilitate indirect communication between one or more UEs (e.g., UE612cand/or612d) and network nodes (e.g., network node610b). In some examples, the hub614may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub614may be a broadband router enabling access to the core network606for the UEs. As another example, the hub614may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes610, or by executable code, script, process, or other instructions in the hub614. As another example, the hub614may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub614may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub614may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub614then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub614acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.

The hub614may have a constant/persistent or intermittent connection to the network node610b. The hub614may also allow for a different communication scheme and/or schedule between the hub614and UEs (e.g., UE612cand/or612d), and between the hub614and the core network606. In other examples, the hub614is connected to the core network606and/or one or more UEs via a wired connection. Moreover, the hub614may be configured to connect to an M2M service provider over the access network604and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes610while still connected via the hub614via a wired or wireless connection. In some embodiments, the hub614may be a dedicated hub—that is, a hub whose primary function is to route communications to/from the UEs from/to the network node610b. In other embodiments, the hub614may be a non-dedicated hub—that is, a device which is capable of operating to route communications between the UEs and network node610b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

In an embodiment, the telecommunication network602includes an interworking logic130(and possibly other components) to provide interworking between a cloud platform120and a communication service platform, as described herein.

The UE700includes processing circuitry702that is operatively coupled via a bus704to an input/output interface706, a power source708, a memory710, a communication interface712, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown inFIG. 7. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

The processing circuitry702is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory710. The processing circuitry702may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry702may include multiple central processing units (CPUs).

In some embodiments, the power source708is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source708may further include power circuitry for delivering power from the power source708itself, and/or an external power source, to the various parts of the UE700via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source708to make the power suitable for the respective components of the UE700to which power is supplied.

The memory710may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory710includes one or more application programs714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data716. The memory710may store, for use by the UE700, any of a variety of various operating systems or combinations of operating systems.

The processing circuitry702may be configured to communicate with an access network or other network using the communication interface712. The communication interface712may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna722. The communication interface712may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter718and/or a receiver720appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter718and receiver720may be coupled to one or more antennas (e.g., antenna722) and may share circuit components, software or firmware, or alternatively be implemented separately.

In an embodiment, the UE700implements a client application that can access an application deployed in a cloud platform or an edge cloud.

The network node800includes a processing circuitry802, a memory804, a communication interface806, and a power source808. The network node800may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node800comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node800may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory804for different RATs) and some components may be reused (e.g., a same antenna810may be shared by different RATs). The network node800may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node800, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node800.

The processing circuitry802may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node800components, such as the memory804, to provide network node800functionality.

In some embodiments, the processing circuitry802includes a system on a chip (SOC). In some embodiments, the processing circuitry802includes one or more of radio frequency (RF) transceiver circuitry812and baseband processing circuitry814. In some embodiments, the radio frequency (RF) transceiver circuitry812and the baseband processing circuitry814may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry812and baseband processing circuitry814may be on the same chip or set of chips, boards, or units.

The memory804may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry802. The memory804may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry802and utilized by the network node800. The memory804may be used to store any calculations made by the processing circuitry802and/or any data received via the communication interface806. In some embodiments, the processing circuitry802and memory804is integrated.

The communication interface806is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface806comprises port(s)/terminal(s)816to send and receive data, for example to and from a network over a wired connection. The communication interface806also includes radio front-end circuitry818that may be coupled to, or in certain embodiments a part of, the antenna810. Radio front-end circuitry818comprises filters820and amplifiers822. The radio front-end circuitry818may be connected to an antenna810and processing circuitry802. The radio front-end circuitry may be configured to condition signals communicated between antenna810and processing circuitry802. The radio front-end circuitry818may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry818may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters820and/or amplifiers822. The radio signal may then be transmitted via the antenna810. Similarly, when receiving data, the antenna810may collect radio signals which are then converted into digital data by the radio front-end circuitry818. The digital data may be passed to the processing circuitry802. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node800does not include separate radio front-end circuitry818, instead, the processing circuitry802includes radio front-end circuitry and is connected to the antenna810. Similarly, in some embodiments, all or some of the RF transceiver circuitry812is part of the communication interface806. In still other embodiments, the communication interface806includes one or more ports or terminals816, the radio front-end circuitry818, and the RF transceiver circuitry812, as part of a radio unit (not shown), and the communication interface806communicates with the baseband processing circuitry814, which is part of a digital unit (not shown).

The antenna810may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna810may be coupled to the radio front-end circuitry818and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna810is separate from the network node800and connectable to the network node800through an interface or port.

The antenna810, communication interface806, and/or the processing circuitry802may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna810, the communication interface806, and/or the processing circuitry802may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source808provides power to the various components of network node800in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source808may further comprise, or be coupled to, power management circuitry to supply the components of the network node800with power for performing the functionality described herein. For example, the network node800may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source808. As a further example, the power source808may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

Embodiments of the network node800may include additional components beyond those shown inFIG. 8for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node800may include user interface equipment to allow input of information into the network node800and to allow output of information from the network node800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node800.

In an embodiment, the network node800implements an interworking logic130(and possibly other components) to provide interworking between a cloud platform120and a communication service platform, as described herein.

FIG. 9is a block diagram of a host, according to some embodiments. The host900may be an embodiment of the host616ofFIG. 6, in accordance with various aspects described herein. As used herein, the host900may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host900may provide one or more services to one or more UEs.

The host900includes processing circuitry902that is operatively coupled via a bus904to an input/output interface906, a network interface908, a power source910, and a memory912. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such asFIGS. 7 and 8, such that the descriptions thereof are generally applicable to the corresponding components of host900.

The memory912may include one or more computer programs including one or more host application programs914and data916, which may include user data, e.g., data generated by a UE for the host900or data generated by the host900for a UE. Embodiments of the host900may utilize only a subset or all of the components shown. The host application programs914may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs914may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host900may select and/or indicate a different host for over-the-top services for a UE. The host application programs914may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

Hardware1004includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers1006(also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs1008aand1008b(one or more of which may be generally referred to as VMs1008), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer1006may present a virtual operating platform that appears like networking hardware to the VMs1008.

The VMs1008comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer1006. Different embodiments of the instance of a virtual appliance1002may be implemented on one or more of VMs1008, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, a VM1008may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs1008, and that part of hardware1004that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs1008on top of the hardware1004and corresponds to the application1002.

Hardware1004may be implemented in a standalone network node with generic or specific components. Hardware1004may implement some functions via virtualization. Alternatively, hardware1004may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration1010, which, among others, oversees lifecycle management of applications1002. In some embodiments, hardware1004is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system1012which may alternatively be used for communication between hardware nodes and radio units.

FIG. 11is a communication diagram showing a host communicating via a network node with a UE over a partially wireless connection, according to some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE612aofFIG. 6and/or UE700ofFIG. 7), network node (such as network node610aofFIG. 6and/or network node800ofFIG. 8), and host (such as host616ofFIG. 6and/or host900ofFIG. 9) discussed in the preceding paragraphs will now be described with reference toFIG. 11.

Like host900, embodiments of host1102include hardware, such as a communication interface, processing circuitry, and memory. The host1102also includes software, which is stored in or accessible by the host1102and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE1106connecting via an over-the-top (OTT) connection1150extending between the UE1106and host1102. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection1150.

The network node1104includes hardware enabling it to communicate with the host1102and UE1106. The connection1160may be direct or pass through a core network (like core network606ofFIG. 6) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

The UE1106includes hardware and software, which is stored in or accessible by UE1106and executable by the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE1106with the support of the host1102. In the host1102, an executing host application may communicate with the executing client application via the OTT connection1150terminating at the UE1106and host1102. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection1150may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection1150.

The OTT connection1150may extend via a connection1160between the host1102and the network node1104and via a wireless connection1170between the network node1104and the UE1106to provide the connection between the host1102and the UE1106. The connection1160and wireless connection1170, over which the OTT connection1150may be provided, have been drawn abstractly to illustrate the communication between the host1102and the UE1106via the network node1104, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via the OTT connection1150, in step1108, the host1102provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE1106. In other embodiments, the user data is associated with a UE1106that shares data with the host1102without explicit human interaction. In step1110, the host1102initiates a transmission carrying the user data towards the UE1106. The host1102may initiate the transmission responsive to a request transmitted by the UE1106. The request may be caused by human interaction with the UE1106or by operation of the client application executing on the UE1106. The transmission may pass via the network node1104, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step1112, the network node1104transmits to the UE1106the user data that was carried in the transmission that the host1102initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step1114, the UE1106receives the user data carried in the transmission, which may be performed by a client application executed on the UE1106associated with the host application executed by the host1102.

In some examples, the UE1106executes a client application which provides user data to the host1102. The user data may be provided in reaction or response to the data received from the host1102. Accordingly, in step1116, the UE1106may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE1106. Regardless of the specific manner in which the user data was provided, the UE1106initiates, in step1118, transmission of the user data towards the host1102via the network node1104. In step1120, in accordance with the teachings of the embodiments described throughout this disclosure, the network node1104receives user data from the UE1106and initiates transmission of the received user data towards the host1102. In step1122, the host1102receives the user data carried in the transmission initiated by the UE1106.

One or more of the various embodiments improve the performance of OTT services provided to the UE1106using the OTT connection1150, in which the wireless connection1170forms the last segment. More precisely, the teachings of these embodiments may improve the latency (e.g., by provisioning edge subnets at different edge locations that allow for fulfilling application demands) and thereby provide benefits such as reduced user wait times and better responsiveness.

In an example scenario, factory status information may be collected and analyzed by the host1102. As another example, the host1102may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host1102may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host1102may store surveillance video uploaded by a UE. As another example, the host1102may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host1102may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection1150between the host1102and UE1106, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host1102and/or UE1106. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection1150passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection1150may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node1104. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host1102. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection1150while monitoring propagation times, errors, etc.