Edge service deployment by invoking network slicing

Abstract

An edge service deployment via a network slice invocation is provided, which includes acquiring one or more service-related parameters for a network slice invocation to support an edge service instance, and requesting a network slice from a network based on the acquired one or more service-related parameters. The requesting from the network is performed via a collaborative platform. Further, the edge service deployment and network slice invocation includes receiving a network slice invocation code from the network based on the request for the network slice, and initiating activation of the edge service instance on the network slice of the network using the network slice invocation code.

Description

[Background technology]

[0001] One or more aspects relate generally to edge computing, and more particularly to enhancing edge computing across networks through improved edge service deployment and invoking network slicing.

[0002] In cloud environments, edge computing (i.e., computing at or near the edge) allows data processing and / or storage to be provided at or near the device on which the operation is performed. Thus, edge computing can eliminate the need for data to be processed or stored to be transmitted to a central location (e.g., a central cloud server), which may be physically located a significant distance from the device. While this configuration may not result in a substantial change to the services offered from the perspective of the individual device, the Internet of Things (IoT) and the massive growth of other electronic devices, including mobile devices, will exponentially increase the network requirements for using cloud services, which can cause increased latency and potentially result in reduced service quality, higher bandwidth costs, and the like. Advantageously, edge computing can help mitigate these issues.

[0003] For example, multi-access edge computing (MEC) provides a computing approach in which cloud computing capabilities in information technology (IT) service environments are delivered at the edge of the network, providing an ecosystem for flexible and rapid deployment of applications and services.

[0004] In cellular communications, 5G is the next generation of broadband cellular networks, enabling significant increases in communication speeds. MEC has implementations for a variety of networks, and 5G implementations are expanding as service providers adopt this latest, technologically advanced system for their customers. Combined, MEC and 5G can become a powerful force in the computing world. The emergence of 5G network capabilities will continue to grow along with the number of connected devices on the network, thereby increasing the need for edge computing to help distribute networking demands. Applications that heavily rely on seamless network connectivity, rapid deployment, and low latency include burgeoning technologies such as artificial intelligence (AI), IoT, virtual reality (VR), and augmented reality (AR). Both MEC and 5G networking will enable the simultaneous use of a vast number of connected technologies without network outages due to traffic disruptions. Summary of the Invention

[0005] Certain shortcomings of the prior art are overcome and additional advantages are provided herein by provisioning a computer program product to facilitate processing within a computing environment. The computer program product includes one or more computer-readable storage media and program instructions embodied therein. The program instructions are readable by a processing circuit to cause the processing circuit to execute a method including: acquiring one or more service-related parameters for a network slice invocation to support an edge service instance; and requesting a network slice from a network based on the acquired one or more service-related parameters, the requesting from the network being performed via a collaborative platform. The method also includes receiving a network slice invocation code from the network based on the request for the network slice; and initiating activation of the edge service instance on the network slice of the network using the network slice invocation code.

[0006] Computer-implemented methods and computer systems relating to one or more aspects are also described and claimed herein. Additionally, services relating to one or more aspects may also be described and claimed herein.

[0007] Additional features and advantages are realized through the techniques described herein. Other embodiments and aspects are described in detail herein and are considered a part of the claimed aspects. [Brief explanation of the drawings]

[0008] One or more aspects are particularly pointed out and individually claimed as examples in the claims at the end of this specification. The above, as well as objects, features, and advantages of one or more aspects, will be apparent from the following detailed description taken in conjunction with the accompanying drawings.

[0009] [Figure 1] 1 illustrates an example of a computing environment for including and / or using one or more aspects of the present invention.

[0010] [Figure 2] 1 illustrates one embodiment of a workflow for edge service instance deployment and network slice invocation in accordance with one or more aspects of the present invention.

[0011] [Figure 3] 1 illustrates another embodiment of a computing environment for incorporating and / or using one or more aspects of the present invention.

[0012] [Figure 4] 4 illustrates one embodiment of a workflow for edge service instance deployment and network slice invocation for the computing environment of FIG. 3 in accordance with one or more aspects of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0013] The accompanying drawings, which are incorporated in and form a part of this specification, further illustrate the present invention and, together with this detailed description of the invention, serve to explain aspects of the invention. It should be noted in this regard that descriptions of well-known systems, devices, processing techniques, and the like have been omitted so as not to unnecessarily obscure the invention in detail. It should be understood, however, that the detailed description and the specific examples, while illustrating aspects of the invention, are provided by way of illustration only, not limitation. Various substitutions, modifications, additions, and / or other configurations within the scope of the underlying inventive concept will be apparent to those skilled in the art from this disclosure. It should also be noted that, although multiple aspects or features of the invention are disclosed herein, unless inconsistent, each disclosed aspect or feature can be combined with any other disclosed aspect or feature as desired for a particular application of the disclosed concept.

[0014] It should also be noted that exemplary embodiments are described below by way of example only, and not by way of limitation, using specific code, designs, architectures, protocols, layouts, diagrams, or tools. Furthermore, the exemplary embodiments are described in particular instances using specific software, tools, or data processing environments, and as examples only, for clarity of explanation. The exemplary embodiments may be used in conjunction with other comparable or similarly purposed structures, systems, applications, or architectures. One or more aspects of the exemplary embodiments may be implemented in hardware, software, or a combination thereof.

[0015] As will be appreciated by those skilled in the art, program code referred to herein can include software and / or hardware. For example, the program code in certain embodiments of the present invention can utilize software-based implementations of the described functionality, while other embodiments can include fixed-function hardware. Certain embodiments combine both types of program code. In the exemplary computing environment 100 of FIG. 1 , examples of program code, also referred to as one or more programs, are shown in FIG. 1 as an operating system 122 stored on persistent storage 113, an edge service instance 126 with network slice code, and a cloud orchestration module 141, a set of virtual machines 143, and a set of containers 144 that are part of the public cloud 105.

[0016] For context, containerization is the packaging of software code (e.g., to implement a service or microservice) and its dependencies, such as operating system libraries and / or other dependencies, used to execute the software code to create a single, lightweight executable, referred to as a container. Containers are portable in that they run consistently and reliably on any information technology infrastructure. In one or more embodiments, in the case of edge-based computing, the software code can be an application, such as an edge application or edge service instance. Containers are created from container images, which are static files containing executable program code that can run as isolated processes on computing or information technology (IT) infrastructure. A single image can be used to run one or more containers, which are runtime instances of the container image. Containers are lightweight (e.g., they share the machine's operating system), efficient, easy to manage, secure, and portable.

[0017] One example of a product used to provide and manage containers is Kubernetes®, an open-source system for automating the deployment, scaling, and management of containerized applications. (Kubernetes® is a registered trademark of the Linux Foundation in at least one jurisdiction.) Kubernetes groups the containers that make up an application into logical units for easier management and discovery. In operation, Kubernetes orchestrates containerized applications to run on a cluster of hosts (or nodes) and automates the deployment and management of cloud-native applications using on-premises infrastructure or public cloud platforms. Kubernetes systems are designed to run containerized applications across a cluster of nodes (or servers or devices) that may be in a single geographic location or distributed across multiple geographic locations. In one or more implementations, a cluster is a set of nodes (whether physical or virtual computing resources) running a Kubernetes agent managed by the Kubernetes control plane.

[0018] Container orchestration is the automation of much of the operational effort required to run containerized workloads and services. Orchestration encompasses a wide range of processes required to maintain the lifecycle of containers, including provisioning, deployment, scaling (scaling up and down), networking, load balancing, etc. Note that Kubernetes is just one example of an orchestration platform that can be used to manage service deployments, such as those disclosed herein. In one or more embodiments, other platforms, such as Docker™, Function as a Service (FaaS), etc., can be used to manage service deployments in accordance with one or more aspects of the disclosure. (Docker™ is a trademark or registered trademark of Docker, Inc., of California, USA.)

[0019] The use of edge-based computing, including edge application services, advantageously reduces the volume of data to be transferred and the subsequent traffic and distance the data must travel. This results in lower latency and reduces transmission costs. Offloading computing to the edge (e.g., to one or more edge devices or systems on a network such as a cellular network) can advantageously benefit the response time of real-time applications. In one or more implementations, edge-based containers are decentralized computing resources located at or near end-user equipment (e.g., devices or systems) to, for example, reduce latency, conserve bandwidth, and improve the overall digital experience.

[0020] As mentioned, 5G is a next-generation broadband cellular network that enables significantly increased communication speeds. In one or more implementations, the cellular network includes multiple edge sites, each having a respective cell tower that wirelessly interfaces with various types of user equipment within range of the cell tower. In one embodiment, each edge site can include a radio access network (RAN) that interfaces with any edge site computing infrastructure and a next-generation (5G) core network. The core network (in one embodiment) can facilitate communication with one or more cloud-based computing resources, such as those discussed herein. In one implementation, the next-generation core network can include, for example, a radio access network (RAN) and a user plane function (UPF) that interfaces with a data network, such as a local area network (LAN), a wide area network (WAN), such as the Internet, or a combination thereof. The data network can include one or more wired and / or wireless networks capable of receiving and transmitting data, such as data related to one or more of the edge services or applications mentioned herein. Additionally, the core network may include, for example, an access mobility function (AMF), which in one embodiment interfaces the radio access network (RAN) at the edge site with a session management function (SMF) facility and a unified data management (UDM) facility. The session management function (SMF) further, in one embodiment, interfaces with a policy control function (PCF), as will be appreciated by those skilled in the art.In operation, the user equipment (or edge device) accessing the cellular network may, in one or more embodiments, be one or more wireless user devices, such as, for example, a smartphone, a mobile device, a gaming device, a wireless vehicle device / system, a wireless computer, etc.

[0021] With the advent of 5G networks, certain cloud computing capabilities, such as for information technology (IT) service environments, can be provided at the edge of the network, with particularly latency-sensitive applications increasingly being run as edge services or microservices, e.g., entertainment applications, manufacturing applications, IoT applications, healthcare applications, etc. For example, in one or more embodiments, a container orchestrator interfaces with multiple nodes or edge devices that include one or more service applications or edge services of a host service.

[0022] Application orchestration deployed at edge sites, such as that considered herein, balances two often-conflicting requirements. The first requirement is to maximize quality of service (QoS), e.g., by minimizing response time for each edge user. This means that more copies of an application are needed, e.g., by moving the application closer to the edge. The second requirement is to minimize the required cluster resources, thereby reducing overhead, due to resource limitations at the edge, e.g., by optimizing application placement so that fewer copies of the application are running. Balancing the two requirements can be difficult.

[0023] Currently, when an end user requires an application service outside the network's current configuration, it can be difficult to reconfigure the network to drive service requests consistent with the inherent benefits of edge computing. Disclosed herein are computer program products, computer-implemented methods, and computer systems, in which program code executing on one or more processors performs a novel hybrid edge provisioning process using secure collaborative platform invoke in conjunction with a next-generation network or network provider. For example, a framework is provided for building virtualized network functions (or services) from existing (or previous) instances of edge services to capture the power of narrowband-based network slices. In one or more implementations, activating a new edge service instance can include cloning the new edge service instance from an existing or previous instance of the edge service along with specifications for revising (e.g., scaling up or down) the resource edge service to match the bandwidth provisioned in the network slice. Furthermore, in one or more implementations, a solution is provided for cloning an edge service instance that can request the exact network slice from the next-generation network to match the edge service's needs.

[0024] Before further describing embodiments of the present invention, an example of a computing environment that can include and / or use one or more aspects of the present invention is discussed below with reference to FIG.

[0025] Various aspects of the present disclosure are described by text, flowcharts, block diagrams of computer systems, and / or block diagrams of machine logic included in computer program product (CPP) embodiments. For any flowchart, depending on the technology involved, operations may be performed in an order different from that shown in a given flowchart. For example, again depending on the technology involved, two operations shown in successive flowchart blocks may be performed in reverse order, as a single integrated step, simultaneously, or in at least a partially overlapping manner.

[0026] A computer program product embodiment (“CPP embodiment” or “CPP”) is a term used in this disclosure to describe any set of one or more storage media (also referred to as “media”) collectively contained in a set of one or more storage devices that collectively contain machine-readable code corresponding to instructions and / or data for performing the computer operations specified in a given CPP claim. A “storage device” is any tangible device that can hold and store instructions for use by a computer processor. The computer-readable storage medium may be, but is not limited to, an electronic storage medium, a magnetic storage medium, an optical storage medium, an electromagnetic storage medium, a semiconductor storage medium, a mechanical storage medium, or any suitable combination of the foregoing. Some known types of storage devices that include these media include diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), compact disk read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanically encoded device (such as pits / lands formed on a major surface of a punch card or disk), or any suitable combination of the foregoing. Computer-readable storage media, as the term is used in this disclosure, is not to be construed as storage in the form of a transient signal per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide, light pulses passing through fiber optic cables, electrical signals communicated over wires, and / or other transmission media. As those skilled in the art will appreciate, data is typically moved at some infrequent time during the normal operation of the storage device, such as during access, defragmentation, or garbage collection, but the above does not qualify a storage device as transient because the data is not transient while it is stored.

[0027] Computing environment 100 encompasses an example of an environment for executing at least a portion of the computer code involved in performing the methodology of the present invention, such as an edge service instance having network slice code 126. In addition to block 126, computing environment 100 includes, for example, computer 101, wide area network (WAN) 102, end user device (EUD) 103, remote server 104, public cloud 105, and private cloud 106. In this embodiment, computer 101 includes a processor set 110 (including processing circuitry 120 and cache 121), a communications fabric 111, volatile memory 112, persistent storage 113 (including operating system 122 and block 126 shown above), a peripheral device set 114 (including a user interface (UI) device set 123, storage 124, and an Internet of Things (IoT) sensor set 125), and a network module 115. Remote server 104 includes a remote database 130. The public cloud 105 includes a gateway 140, a cloud orchestration module 141, a set of host physical machines 142, a set of virtual machines 143, and a set of containers 144.

[0028] Computer 101 may take the form of a desktop computer, a laptop computer, a tablet computer, a smartphone, a smartwatch or other wearable computer, a mainframe computer, a quantum computer, or any other form of computer or mobile device now known or later developed that is capable of executing programs, accessing a network, or querying a database, such as remote database 130. As is well understood in the field of computer technology, and depending on the technology, execution of a computer-implemented method may be distributed among multiple computers and / or among multiple locations. However, in this description of computing environment 100, for purposes of brevity, the detailed discussion focuses on a single computer, specifically computer 101. While computer 101 is not shown in FIG. 1 within a cloud, it may be located within a cloud. However, computer 101 is not required to reside within a cloud except to any extent that may be expressly indicated.

[0029] Processor set 110 includes one or more computer processors of any type now known or later developed. Processing circuitry 120 may be distributed across multiple packages, e.g., multiple linked integrated circuit chips. Processing circuitry 120 may implement multiple processor threads and / or multiple processor cores. Cache 121 is memory located within the processor chip package and is typically used for data or code that should be available for fast access by threads or cores executing on processor set 110. Cache memory is typically organized into multiple levels depending on relative proximity to the processing circuitry. Alternatively, some or all of the cache for a processor set may be located “off-chip.” In some computing environments, processor set 110 may be designed to operate with qubits and perform quantum computing.

[0030] Computer-readable program instructions are typically loaded onto computer 101 to cause processor set 110 of computer 101 to perform a series of operational steps, thereby realizing a computer-implemented method, such that the instructions so executed instantiate the method specified in the flowcharts and / or descriptions of the computer-implemented methods contained herein (collectively referred to as the "methods of the present invention"). These computer-readable program instructions are stored in various types of computer-readable storage media, such as cache 121 and other storage media discussed below. The program instructions and associated data are accessed by processor set 110 to control and direct the execution of the methods of the present invention. In computing environment 100, at least some of the instructions for executing the methods of the present invention may be stored in block 126 in persistent storage 113.

[0031] Communications fabric 111 is the signal-conducting pathway that allows various components of computer 101 to communicate with one another. Typically, this fabric is made of switches and conductive pathways, such as switches and conductive pathways that make up buses, bridges, physical input / output ports, etc. Other types of signal communication pathways may be used, such as fiber optic and / or wireless communication pathways.

[0032] Volatile memory 112 may be any type of volatile memory now known or later developed. Examples include dynamic random access memory (RAM) or static RAM. Typically, volatile memory is characterized by random access, although this is not required unless expressly indicated. In computer 101, volatile memory 112 is located in a single package and is internal to computer 101; however, alternatively or additionally, volatile memory may be distributed across multiple packages and / or located external to computer 101.

[0033] Persistent storage 113 is any form of non-volatile storage for a computer, now known or later developed. The non-volatility of this storage means that stored data remains regardless of whether power is supplied to computer 101 and / or to persistent storage 113 directly. While persistent storage 113 can be read-only memory (ROM), typically at least a portion of persistent storage allows data to be written, data to be deleted, and data to be rewritten. Some well-known forms of persistent storage include magnetic disks and solid-state storage devices. Operating system 122 may take several forms, such as various known proprietary operating systems or open-source Portable Operating System Interface-type operating systems that utilize a kernel. The code contained in block 126 typically includes at least some of the computer code involved in performing the methods of the present invention.

[0034] Peripheral device set 114 includes a set of peripheral devices of computer 101. Data communication connections between peripheral devices and other components of computer 101 may be implemented in various ways, such as Bluetooth® connections, near field communication (NFC) connections, connections formed by cables (such as universal serial bus (USB)-type cables), insertion-type connections (e.g., Secure Digital (SD) cards), connections formed through local area communication networks, and even connections formed through wide area networks such as the Internet. In various embodiments, UI device set 123 may include components such as display screens, speakers, microphones, wearable devices (such as goggles and smartwatches), keyboards, mice, printers, touchpads, game controllers, and haptic devices. Storage 124 is external storage, such as an external hard drive, or insertable storage, such as an SD card. Storage 124 may be persistent and / or volatile. In some embodiments, storage 124 may take the form of a quantum computing storage device for storing data in the form of qubits. In embodiments where computer 101 is required to have a large amount of storage (e.g., where computer 101 stores and manages large databases locally), this storage may be provided by a peripheral storage device designed to store very large amounts of data, such as a storage area network (SAN) shared by multiple, geographically distributed computers. IoT sensor set 125 consists of sensors that can be used in Internet of Things applications. For example, one sensor may be a thermometer and another sensor may be a motion detector.

[0035] Network module 115 is a collection of computer software, hardware, and firmware that enables computer 101 to communicate with other computers over WAN 102. Network module 115 may include hardware such as a modem or Wi-Fi® signal transceiver, software for packetizing and / or depacketizing data for communications network transmission, and / or web browser software for communicating data over the Internet. In some embodiments, the network control and network forwarding functions of network module 115 are performed on the same physical hardware device. In other embodiments (e.g., embodiments utilizing Software-Defined Networking (SDN)), the control and forwarding functions of network module 115 are performed on physically separate devices, such that the control function manages several different network hardware devices. Computer-readable program instructions for implementing the methods of the present invention may be downloaded to computer 101 from an external computer or external storage device, typically through a network adapter card or network interface included in network module 115.

[0036] WAN 102 is any wide area network (e.g., the Internet) capable of communicating computer data over non-local distances by any technology for communicating computer data now known or later developed. In some embodiments, a WAN may be replaced and / or supplemented by a local area network (LAN) designed to communicate data between devices located in a local area, such as a Wi-Fi network. WANs and / or LANs typically include copper transmission cables, optical fiber transmissions, wireless transmissions, and computer hardware such as routers, firewalls, switches, gateway computers, and edge servers.

[0037] End-user device (EUD) 103 is any computer system used and controlled by an end user (e.g., a customer of the enterprise operating computer 101) and may take any of the forms discussed above in connection with computer 101. EUD 103 typically receives useful and useful data from the operation of computer 101. For example, in a hypothetical case in which computer 101 is designed to provide recommendations to end users, the recommendations would typically be communicated from computer 101's network module 115 over WAN 102 to EUD 103. In this manner, EUD 103 can display or otherwise present the recommendations to the end user. In some embodiments, EUD 103 may be a client device such as a thin client, a heavy client, a mainframe computer, a desktop computer, and the like.

[0038] Remote server 104 is any computer system that provides at least some data and / or functionality to computer 101. Remote server 104 may be controlled and used by the same entity that operates computer 101. Remote server 104 represents a machine that collects and stores useful and useful data for use by other computers, such as computer 101. For example, in the hypothetical case where computer 101 is designed and programmed to provide recommendations based on historical data, this historical data may be provided to computer 101 from remote database 130 of remote server 104.

[0039] A public cloud 105 is any computer system available for use by multiple entities that provides on-demand availability of computer system resources and / or other computer functionality, particularly data storage (cloud storage) and computing power, without direct active management by users. Cloud computing typically leverages resource sharing to achieve coherence and economies of scale. Direct active management of the computing resources of the public cloud 105 is performed by the computer hardware and / or software of a cloud orchestration module 141. The computing resources provided by the public cloud 105 are typically implemented by virtual computing environments running on various computers comprising a host physical machine set 142, which is the universe of physical computers within and / or available in the public cloud 105. A virtual computing environment (VCE) typically takes the form of a virtual machine from a virtual machine set 143 and / or a container from a container set 144. It is understood that these VCEs can be stored as images and transferred among and between various physical machine hosts, either as images or after instantiation of the VCE. Cloud orchestration module 141 manages image transfer and storage, deploys new instantiations of VCE, and manages active instantiations of VCE deployments. Gateway 140 is a collection of computer software, hardware, and firmware that enables public cloud 105 to communicate over WAN 102.

[0040] Some further description of virtualized computing environments (VCEs) is now provided. A VCE can be stored as an "image." A new, active instance of a VCE can be instantiated from the image. Two well-known types of VCEs are virtual machines and containers. A container is a VCE that uses operating system-level virtualization. This refers to a feature of an operating system in which the kernel allows the existence of multiple isolated user space instances, called containers. These isolated user space instances typically behave as actual computers from the perspective of programs running within them. A computer program running on a typical operating system can utilize all of the computer's resources, such as connected devices, files and folders, network shares, CPU power, and quantifiable hardware capabilities. However, a program running inside a container can only use the contents of the container and the devices assigned to the container; this feature is known as containerization.

[0041] A private cloud 106 is similar to a public cloud 105, except that its computing resources are available only for use by a single enterprise. While the private cloud 106 is shown in communication with the WAN 102, in other embodiments, the private cloud may be completely disconnected from the Internet and accessible only through a local / private network. A hybrid cloud is a composite of multiple clouds of different types (e.g., private, community, or public cloud types), often implemented by different vendors. While each of the multiple clouds remains a separate, discrete entity, the larger hybrid cloud architecture is bound together by standardized or proprietary technologies that enable orchestration, management, and / or data / application portability between the constituent clouds. In this embodiment, both the public cloud 105 and the private cloud 106 are part of a larger hybrid cloud.

[0042] As discussed, embodiments of the present invention include computer program products, computer-implemented methods, and computer systems, where program code executing on one or more processors performs edge service deployment using a network slice invocation method, such as method 200 shown in FIG. 2 . As shown, method 200, in one embodiment, may include step 202, by one or more processors, obtaining one or more service-related parameters for the network slice invocation to support the edge service instance, and step 204, by the one or more processors, requesting a network slice from a network based on the obtained one or more service-related parameters. The request may be made via a collaboration platform, such as a secure subscription-based collaboration platform. In one or more embodiments, the collaboration platform may be separate from the service provider and the network provider. The method further includes step 206, in one embodiment, receiving a network slice invocation code from the network based on the request for the network slice. Additionally, the method (in one embodiment) includes step 208, by using the network slice invocation code, initiating activation of the edge service instance on the network slice of the network.

[0043] In one or more embodiments, obtaining one or more service-related parameters relates to service-related parameters of a previous instance of the edge service. Further, in one or more embodiments, initiating activation of the edge service instance can include cloning the edge service instance from another previous instance of the edge service. In one embodiment, initiating activation of the edge service instance is at the edge device, and cloning the edge service instance includes cloning the edge service instance from another instance of the edge service on another edge device, such as another instance of the edge service located geospatially near the edge device or node edge for deploying the service.

[0044] In one or more embodiments, the one or more retrieved service-related parameters for the network slice invocation include an expected bandwidth required for the edge service instance and an expected execution time of the edge service instance. Further, in one implementation, the one or more retrieved service-related parameters further include an expected time for cloning the edge service instance from another instance of the edge service. In one embodiment, requesting the network slice from the network includes requesting a network slice from the network adjusted to the expected bandwidth required for the edge service instance, the expected execution time of the edge service instance, and the expected time for cloning the other instance of the edge service.

[0045] Numerous aspects of the present invention are disclosed herein in presented concepts. For example, computer program products, systems, and methods are presented for edge service deployment via network slice invocation, where a collaborative platform separate from the next-generation network is used to request, at runtime, a point-to-point network slice of an identified channel of a given bandwidth and a given time interval. Additionally, runtime identification and cloning of edge services or applications (e.g., binaries or executable code functions) geospatially closer to the edge device requesting the service is provided. In one or more embodiments, real-time provisioning of optimized and derived low-bandwidth network slice requests is disclosed, enabling efficient cloning of edge services or edge service binaries.

[0046] Also presented are methods for enabling service request validation and provisioning of host edge transactions that pass processing control from a previously known host service, e.g., running on cloud-based resources, to a newly created edge service (e.g., based on a geospatial filter). In one or more embodiments, program products, systems, and methods are disclosed herein that enable cloning of edge services (or edge service binaries) from, e.g., a node edge source to a node edge device or edge server by provisioning the exact network slice required for edge service cloning and edge service implementation from a next-generation (5G) network provider, which aligns network costs with expected edge service usage. Certain aspects disclosed herein are referred to as hybrid edge service provisioning, where a framework is provided for cloning edge services based on invocation of a collaborative platform or secure subscription-based platform through which service providers and network providers communicate securely. For example, a requesting system or device triggers a service request through a collaborative platform, and an activation process provisions the transfer of a vertical slice of the referenced architecture at a determined bandwidth, thereby facilitating obtaining the exact amount of network slice bandwidth required for the edge service instance from the next-generation network.

[0047] In one or more implementations, hybrid edge provisioning disclosed herein includes a method for cloning, for example, based on collaborative platform invocation. A requesting system, for example, a node spawner, triggers a service request after identifying a service hosted in the collaborative platform marketplace. The activation process provisions the transfer of a vertical slice of the referenced architecture over the calculated bandwidth, thereby facilitating obtaining the exact amount of network slice bandwidth required for the edge service instance from the next-generation network.

[0048] The service provider must ensure a synchronized state of the services made available on the edge device. Runtime provisioning may be determined depending on resource requirements. Based on a specified acceptable latency, the process may configure the service either at the NodalEdgeSource (edge provisioning server) or at the edge device (NodalEdge or edge server). In one or more implementations, the wait time for provisioning the edge service is minimized. In one embodiment, the system may transfer one or more binaries from the host service (e.g., NodalEdgeSource) only if a nearby edge server in the same geographic area or zone does not have the binaries that can be cloned to deploy a new edge service instance on the edge device. After identifying the service provider during the activation process, node complementation can help identify whether new binaries are needed or not. In one or more embodiments, a state manager may be used, where details of the state of the edge service binaries are stored. Based on the initial and final configuration state on the edge device, partition (binary) replicas are either migrated or deleted. In one or more embodiments, a solution is provided for efficiently cloning binaries to the required edge devices through host service components NodalSpawner, NodalReplicatingVector, and NodalEdgeSource, which invoke network slice requests to the 5G network.

[0049] Advantageously, an improvement to the edge computing paradigm that leverages a specific novel hybrid edge provisioning process to create a network slice from a 5G network is disclosed herein. In one or more embodiments, multiple edge nodes (or edge devices) are contemplated, running similar services (or binaries), with the services or functions maintained via a central host service, such as a cloud-based service provider. When a specific edge device is identified as eligible for an update to run the edge service, the central host (which maintains a repository of edge service updates) uses the process and system framework disclosed herein to determine the call parameters necessary to create a network slice customized for the specific edge service function running on the edge device. A full set of parameters, configurations, and operating system updates can be defined for the edge device. Real-time provisioning requests for optimized and derived narrowband network slices are disclosed, which can also be combined with the ability to clone edge services or binaries, thereby stabilizing the new hybrid edge and activating the edge service to support end-to-end transactions for specific end users on the edge as a cloud function. The entire transaction can be supported by using a commercially available enabling platform, referred to herein as a collaborative platform, through which network slices can be invoked as a service from 5G network providers, with the entire history of transaction configurations (for example) maintained centrally at the host service.

[0050] FIG. 3 illustrates another embodiment of a computing environment 300 incorporating and / or using one or more aspects of the present invention. Those skilled in the art will appreciate that, in one or more embodiments, certain aspects of the computing environment 300 may be the same or similar to those described above in connection with the computing environment 100 of FIG. 1 . The computing environment 300 illustrates, by way of example, a technical environment or system in which various aspects of some embodiments of the present invention may be implemented. By way of example, the computing environment 300 includes a next-generation cellular network, e.g., a 5G network, shown as 305, for wirelessly interfacing with various types of edge devices or systems 320. In one embodiment, the next-generation network 305 facilitates edge device communication with and / or data transfer to one or more computing resources 310, e.g., one or more cloud-based computing resources. In the illustrated embodiment, the computing resources 310 execute program code implementing one or more aspects of a service provider 311, including, for example, a database containing one or more binary or executable code implementing the virtualization functionality and / or services of the service provider 311, such as a host service 312 and one or more edge services. As shown, in one embodiment, the program code implementing the host service 312 may further include program code implementing a node spawner (NodalSpawner) 313, a node replicator (NodalReplicatingVector) 314, and a node orchestrator (NodalEdgeSource) 315, which are further described below with reference to the process embodiment of FIG. 4.

[0051] In the embodiment of Figure 3, next generation (5G) network 305 provides network slices 306. As understood in the art, network slicing is a network configuration that allows multiple (virtualized and independent) networks to be created over a common physical infrastructure. In one embodiment, each virtual or logical network may be designed to deliver an identified function and may include all necessary network resources configured and connected end-to-end.

[0052] In one embodiment, edge device 310 includes an edge service instance (or node edge) 321 for performing edge computing functions, for example, at or near an end-user device. In one or more embodiments, edge device 310 may further include one or more binaries 322, such as stored, virtualized functions and / or services. For example, in one embodiment, an edge device such as edge device 320 may include previously executed instances of an edge service as binaries in persistent storage.

[0053] As shown, computing environment 300 further includes collaboration platform 330, which in one embodiment is a secure, subscription-based collaboration platform, such as those commercially available from various sources. For example, in one or more embodiments, collaboration platform 330 is a blockchain-based decentralized platform or marketplace for digital assets and services. In one or more other embodiments, collaboration platform 330 can be a secure data exchange with blockchain-based artificial intelligence (AI) and / or machine learning orchestration. As used herein, a data marketplace facilitates data trading and exchange processes in a secure manner. In one or more embodiments, security is provided between service providers and network providers using encryption and decryption processes along with persistent cryptographic objects to implement edge service deployments with network slice calls, such as those described herein.

[0054] 3 embodiment, network 305 also includes encryption and decryption (crypto / decrypt) program code 307 and one or more persistent crypto objects 308, for use in communicating with service providers, e.g., across collaborative platform 330. Collaborative platform 330 further includes encryption / decryption (crypto / decrypt) code 331 and persistent crypto objects 332, for use in facilitating secure communications between service providers 311 and network 305, e.g., across collaborative platform 330. In one or more embodiments, collaborative platform 330 provides a framework to enable cloning of edge service instances to required edge devices or servers, e.g., via NodalSpawner 313, NodalReplicatingVector 314, and NodalEdgeSource 315, which (in one embodiment) invoke network slice requests to providers of third-party 5G networks 305.

[0055] In one or more embodiments, a collaborative platform framework / interface is used for hybrid edge provisioning, such as that disclosed herein. The disclosed method and framework provide a solution based on collaborative platform invocation, decision binder, orchestrator, and collaborative platform crypto objects that support digital, autonomous deployment of edge service instances via network slice invocation. A requesting system (e.g., a host system) triggers a service request, and the decision binder identifies appropriate, available services in the marketplace supported by the collaborative platform. Service providers and network providers implement the necessary guidelines for services to become available in the collaborative platform marketplace. In one or more embodiments, decision binding elements are added and protocols are established to enable automated deployment.

[0056] Because latency can adversely affect edge applications, service providers ensure that the state of edge services made available at edge devices meets requirements. Computationally intensive operations may be performed at the edge provisioning server (or NodalEdgeSource), while less computationally intensive operations may be performed at the edge devices. Depending on runtime resource requirements, a process such as that shown in FIG. 4 may be adopted. For example, runtime parameters may be determined depending on latency requirements. In one or more embodiments, the framework may consider how much data, computational capacity, bandwidth, etc. are required during service provisioning at the edge. Based on a specified acceptable latency, the framework configures the service either at the host service (e.g., cloud-based) or at the edge device (e.g., hybrid edge). In one or more implementations, the wait time for end users should approach zero. The framework disclosed herein ensures transaction consistency across a computing environment system, including the host service, network, and edge device.

[0057] In one or more implementations, a method and framework for hybrid edge provisioning and computing is based on the use of a collaborative platform in conjunction with protocol invocation, decision binding, orchestration, cryptographic objects, etc. to support digital, autonomous deployment of edge service instances and invocation of customized network slices. The protocol framework for executing edge services or edge cloud functions may depend on the type of Quality of Service (QoS) requirements (e.g., agreed-upon delay, bandwidth availability, etc.) that can be determined at runtime. Depending on this aspect, the runtime may vary between the host service (i.e., edge provisioning server) and the edge device. Service providers provision services by implementing the agreement protocol through the collaborative platform. Client requests may be received via a third-party provider for a specific service and / or profile via a caller to ensure that an appropriate service and / or profile is invoked from various available services supported by the collaborative platform. The third-party provider / caller passes the request object to a third-party binder, i.e., a decision binder, which, after resolving the cryptographic objects underlying the protocol, ensures that profile selections of registered service providers are available in the marketplace in the collaborative platform. After the successful call and safety verification by resolving the crypto object, the third-party binder can invoke the authorized call after adding the crypto object, and thus the framework ensures that safety constraints are not violated throughout.As soon as the service provider (or host service) receives the request, it is redirected to the host's lead orchestrator, which sends a positive response (after successful validation of the crypto object), thus confirming the trade agreed to be involved with the third-party provider entity.

[0058] Depending on the edge device, edge cloud functions or edge service instances can be provided with or without replication. The framework introduces virtualized functions or virtualized edge services, whose execution requires context and availability. Possible quality of service (QoS) deficiencies can be mitigated by determining the likely partitioning of the function runtime. Due to the time-series, disorganized schema definition for persistence, the Capacitor data model can be considered preferable, allowing selected block replication over file-driven replication. Invoking an edge service instance can be achieved by changing the required state of the virtualized function, which is referred to as configuring a partition replica. If the server has a replica of the partition in the initial and final configurations, no action is required; in that case, there should be no migration of the partition replica to the edge device. However, this may be the case for a small subset of scenarios. The need for replica migration is captured when the servicer (edge device) does not have a replica of the partition in the initial configuration.

[0059] One embodiment of the process is shown in FIG. 4 and described below. Depending on the type of quality of service (QoS) required (e.g., agreed-upon latency), the required bandwidth is determined at runtime. In one or more embodiments, host services 312 (FIG. 3) provisions edge services using collaboration platform 330, implementing, for example, service registration, service identification, and / or service provisioning. As noted, the disclosed process provides a framework for cloning vertical slices of the referenced architecture onto edge devices for provisioning of edge service instances. As shown in FIG. 4, certain aspects of the process can be managed by node replicator 314 (or NodalReplicatingVector) at the request of node spawner (NodalSpawner) 313. NodalReplicatingVector 314 is a program code agent or facility that (in one embodiment) provides the required bandwidth, the time and size of previous clone partitions, and the predicted time for the current cloning process of an edge service instance.

[0060] Based on the available bandwidth for the edge service instance, the previous partition clone time, and the estimated cloning time, NodalSpawner 313 requests bandwidth and time for a network slice invocation from NodalEdgeSource 315. NodalEdgeSource (or server) 315 receives the request from NodalSpawner, and the crypto object is resolved (or decrypted) at NodalEdgeSource 315 to ensure the validity of the request. As noted, NodalSpawner 313 passes the predicted bandwidth required for the clone to NodalEdgeSource 315, and based on these inputs, NodalEdgeSource invokes the 5G network 305 and virtualization functions via the collaborative platform, which (in one embodiment) provisions a narrowband activation slice, which is a customized or tailored network slice of the required bandwidth provided by NodalSpawner after the 5G network resolves the crypto object. Once resolved, 5G network 305 returns the virtualization network slice invocation code to NodalEdgeSource 315. NodalEdgeSource 315 clones and activates NodalEdges (or edge service instances) via network slices, and activation of the clones as service instances is provided to edge devices (NodalEdge) 320. In one or more embodiments, the edge device or server updates SSH to root and executes the edge service instance activation code, i.e., vertical scaling. Upon activation, NodalEdge 320 passes the crypto object along with its configuration back to NodalSpawner 313. Upon successful resolution of the crypto object, NodalSpawner 313 updates the binary state in a database maintained by NodalReplicatingVector 314 for future reference.

[0061] In one or more embodiments, the edge service instance to be cloned is a virtualized function or service, such as a cloud function, running on an edge device. In one embodiment, to clone an edge service instance, context and availability are determined (e.g., by NodalSpawner and NodalReplicatingVector) to make the process efficient. As an example, a partition (P) can refer to a vertical slice of the required virtualized layer in the referenced architecture. A partition is analogous to an executable binary (or edge service instance) customized for a desired service. As illustrated by the following definition, the efficiency of the process can be improved by determining where the service instance for cloning is available based on the initial configuration. Additionally, bandwidth can be determined and created for where the edge service instance clone needs to be geospatially transferred and how much time is needed to enable the cloning.

[0062] Edge Partitioning - Entity Definition S = the set of servers across all data sensors (1) where: S={s1,s2,...,s i ,···,s k ,···s |S|} C I = |S|×|P| matrix representing the initial configuration (2) where:

number

number

[0063] Identification / Participation

[0064] Partition p in the first configuration j z (which represents a potential source of a replica) by restricting servers that hold replicas of z from participating in replica migration. i,j,t From partition p at time t j Server S holds a replica of i is identified.

number

[0065] A server keeps a copy of a replica if: The sum of all bandwidth allocated to partition migrations (by graph traversal) i,j,k,t' Sources j From Destination k to that partition p j A replica of Previous time instance ∀t' <tにおいて Partition p j equal to the size of

[0066] Therefore, to identify partitions that may potentially be migrated in a migration epoch, the following is considered:

number

[0067] Now, for equation (7), a lower bound is found as equation (8), which restricts participants to only those geographic areas where an edge service instance (or binary) can be cloned within a given time.

number

[0068] Bandwidth

[0069] The bandwidth allocated to replica migration is determined by the variable v i,k,t In s i From s k It depends on the capacity of the shortest path to

number

[0070] Those skilled in the art will recognize from the description provided herein that a hybrid edge provisioning process and framework is provided in which secure collaborative platform invocation is used for collaboration between service providers, network providers, and edge devices. For example, a framework is provided for building virtualized network functions (or services) from existing (or previous) instances of edge services to capture the power of narrowband network slices. In one or more implementations, activating a new edge service instance can include cloning the new edge service instance from an existing or previous instance of the edge service, possibly with specifications to revise (e.g., scale up or down) the resource edge service to match the bandwidth provisioned in the network slice. Furthermore, in one or more implementations, a solution is provided for cloning edge service instances that can request a precise network slice from a next-generation network (e.g., a 5G network) to match the needs of the edge service.

[0071] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It is further understood that the terms "comprise" (and any form of comprise, e.g., "comprises" and "comprising"), "have" (and any form of have, e.g., "has" and "having"), "include" (and any form of include, e.g., "includes" and "including"), and "contain" (and any form of include, e.g., "contains" and "containing") are open-ended linking verbs. Consequently, a method or device that "comprises," "has," "includes," or "contains" one or more steps or elements possesses those one or more steps or elements, but is not limited to possessing only those one or more steps or elements. Similarly, a method step or device element that "comprises," "has," "includes," or "contains" one or more features possesses those one or more features, but is not limited to possessing only those one or more features. Furthermore, a device or structure that is configured in a particular way is configured in at least that way, but may also be configured in ways not listed.

[0072] It is intended to include corresponding structure, material, or acts of any means or step-plus-function element in the following claims, and their equivalents, where available, as specifically claimed, or as a structure, material, or act for performing that function in combination with other claimed elements. The description of one or more embodiments has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosed form. Many modifications and variations will be apparent to those skilled in the art. The embodiments were chosen and described to best explain various aspects and practical applications and to enable others skilled in the art to appreciate various embodiments, with various modifications adapted to the particular use contemplated.

Claims

1. 1. A computer program product for facilitating processing within a computing environment, said computer program product comprising: One or more computer-readable storage media and program instructions embodied therein, the program instructions comprising: obtaining one or more service-related parameters for a network slice invocation to support an edge service instance; requesting a network slice from a network based on the one or more service-related parameters obtained, wherein the requesting from the network is performed via a collaborative platform; receiving a network slice invocation code from the network based on the request for the network slice; and Initiating activation of the edge service instance on the network slice of the network using the network slice invocation code.

10. A computer program product readable by a processing circuit to cause the processing circuit to perform a method having the steps:

2. The computer program product of claim 1 , wherein the obtaining one or more service-related parameters relates to service-related parameters of a previous instance of the edge service.

3. The computer program product of claim 1 , wherein initiating activation of the edge service instance comprises cloning the edge service instance from another instance of the edge service.

4. 4. The computer program product of claim 3, wherein the step of initiating activation of the edge service instance occurs at an edge device, and the step of cloning the edge service instance includes cloning the edge service instance from another instance of the edge service at another edge device.

5. 4. The computer program product of claim 3, wherein the obtained one or more service-related parameters for a network slice invocation include an expected bandwidth required for the edge service instance and an expected execution time of the edge service instance.

6. The computer program product of claim 5 , wherein the obtained one or more service-related parameters further comprise an expected time for cloning the edge service instance from another instance of the edge service.

7. 7. The computer program product of claim 6, wherein the step of requesting the network slice from the network comprises requesting the network slice from the network adjusted to the expected bandwidth needed for the edge service instance, the expected execution time of the edge service instance, and the expected time for cloning the other instance of the edge service.

8. The computer program product of claim 1 , wherein the collaborative platform comprises a subscription-based platform separate from the network.

9. obtaining, by the one or more processors, one or more service-related parameters for a network slice invocation to support the edge service instance; requesting, by one or more processors, a network slice from a network based on the obtained one or more service-related parameters, wherein the requesting from the network is performed via a collaborative platform; receiving a network slice invocation code from the network based on the request for the network slice; and initiating activation of the edge service instance on the network slice of the network using the network slice invocation code. A computer-implemented method comprising:

10. The computer-implemented method of claim 9 , wherein obtaining one or more service-related parameters relates to service-related parameters of a previous instance of the edge service.

11. The computer-implemented method of claim 9 , wherein initiating activation of the edge service instance comprises cloning the edge service instance from another instance of the edge service.

12. 12. The computer-implemented method of claim 11, wherein initiating activation of the edge service instance occurs at an edge device, and cloning the edge service instance includes cloning the edge service instance from another instance of the edge service on another edge device.

13. 12. The computer-implemented method of claim 11, wherein the obtained one or more service-related parameters for a network slice invocation include an expected bandwidth required for the edge service instance and an expected execution time for the edge service instance.

14. The computer-implemented method of claim 13 , wherein the obtained one or more service-related parameters further comprise an expected time to clone the edge service instance from another instance of the edge service.

15. 15. The computer-implemented method of claim 14, wherein requesting the network slice from the network comprises requesting the network slice from the network adjusted to the expected bandwidth needed for the edge service instance, the expected execution time of the edge service instance, and the expected time to clone the other instance of the edge service.

16. 1. A computer system for facilitating processing within a computing environment, the computer system comprising: memory; and and at least one processor in communication with the memory, wherein the computer system is configured to execute a method, the method comprising: obtaining one or more service-related parameters for a network slice invocation to support the edge service instance; requesting a network slice from a network based on the obtained one or more service-related parameters, wherein the requesting from the network is performed via a collaborative platform; receiving a network slice invocation code from the network based on the request for the network slice; and initiating activation of the edge service instance on the network slice of the network using the network slice invocation code. A computer system comprising:

17. The computer system of claim 16 , wherein the obtaining one or more service-related parameters relates to service-related parameters of a previous instance of the edge service.

18. 17. The computer system of claim 16, wherein initiating activation of the edge service instance comprises cloning the edge service instance from another instance of the edge service.

19. 20. The computer system of claim 18, wherein initiating activation of the edge service instance occurs at an edge device, and cloning the edge service instance includes cloning the edge service instance from another instance of the edge service on another edge device.

20. 20. The computer system of claim 19, wherein the obtained one or more service-related parameters for a network slice invocation include an expected bandwidth required for the edge service instance and an expected execution time for the edge service instance.

Images