Edge Cloud Application Backup

Abstract

In a methodology for in-band selective data snapshot using fifth generation (5G) radio link control (RLC) channels for edge-cloud application backup, a processor creates one or more RLC channels for forwarding network data packets in a telecommunications network using network slicing techniques. The processor assigns the one or more RLC channels to one or more applications in a user device for dedicated packet routing requirements. The processor maps the corresponding RLC channels and applications to respective corresponding identifiers. The processor monitors the one or more applications for backup. In response to receiving a backup request for the application, the processor creates a copy of a data store associated with the application based on changes monitored in the one or more applications.

Description

Technical Field

[0001] The present disclosure generally relates to the field of application backup, and more particularly, relates to in-band selective data snapshot using 5th Generation (5G) Radio Link Control (RLC) channels for edge-cloud application backup.

Background Art

[0002] In telecommunications, 5G is the fifth-generation technology standard for broadband cellular networks. A 5G network is a cellular network whose service area is divided into small geographic areas called cells. All 5G wireless devices within a cell are connected to the Internet and telephone networks via radio waves through local antennas within the cell. The main advantage of the new networks is that they will have wider bandwidth, faster download speeds, and will eventually reach up to 10 gigabits per second. Due to the increased bandwidth, 5G networks are increasingly likely to be used as general Internet service providers for laptop and desktop computers, and may enable new applications in the fields of the Internet of Things (IoT) and machine-to-machine communications.

[0003] Edge computing is achieved by computing servers located closer to the end user. Edge computing has the potential to reduce latency and data traffic congestion. One definition of edge computing is any type of computer program that delivers low latency closer to the demand. Edge computing can be defined as all out-of-cloud computing that takes place at the edge of the network, or more specifically, all computing in applications that require real-time processing of data. Cloud computing may operate on big data, while edge computing may operate on "instant data," which is real-time data generated by sensors or users. A data store can be a repository for persistently storing and managing a collection of data, including not only database-like repositories, but also simpler store types such as simple files and emails. [Overview of the project]

[0004] Aspects of the embodiments of this disclosure disclose an in-band selective data snapshot technique using fifth-generation (5G) radio link control (RLC) channels for edge cloud application backup, wherein a processor creates one or more RLC channels for forwarding network data packets within a telecommunications network using network slicing techniques. The processor assigns one or more RLC channels to one or more applications in a user device to suit specific packet routing requirements. The processor maps the corresponding RLC channels and applications to corresponding identifiers. The processor monitors one or more applications for backup. In response to receiving a backup request for an application, the processor creates a copy of the datastore associated with the application based on the monitored changes in the application. [Brief explanation of the drawing]

[0005] [Figure 1] This is a functional block diagram illustrating an edge cloud application backup environment according to one embodiment of the present disclosure. [Figure 2] This is a flowchart illustrating the operational steps of a virtual network function module in the computing device shown in Figure 1, according to one embodiment of the present disclosure. [Figure 3] This is an illustrative functional diagram of a virtual network function module within the computing device shown in Figure 1 of this disclosure. [Figure 4] This is an illustrative functional diagram of a user device according to one embodiment of the present disclosure. [Figure 5] This is an exemplary functional diagram of a data store according to one embodiment of the present disclosure. [Figure 6] This figure shows an exemplary service path of a virtual network function module in the computing device of Figure 1 according to one embodiment of the present disclosure. [Figure 7]This is an illustrative functional diagram of a virtual network function module in the computing device shown in Figure 1, according to one embodiment of the present disclosure. [Figure 8] This is a block diagram of the components of the user device and computing device shown in Figure 1, according to one embodiment of the present disclosure. [Figure 9] This figure shows one embodiment of the cloud computing environment described herein. [Figure 10] This figure shows one embodiment of the abstraction model layer of the cloud computing environment as disclosed herein. [Modes for carrying out the invention]

[0006] This disclosure pertains to a system and method for in-band selective data snapshots using fifth-generation (5G) radio link control (RLC) channels for edge cloud application backup.

[0007] Embodiments of this disclosure recognize the need to provide effective application snapshot management in 5G telecommunications networks. Snapshot technology may propose creating multiple copies of data that can be used to restore content if the most recent copy detects a failure or application-level inconsistency. Furthermore, snapshots may serve additional purposes, such as testing new versions of an application using dummy data captured in older snapshots. Embodiments of this disclosure disclose providing application data snapshots in a selective manner controllable by the application. Embodiments of this disclosure disclose that the application controls the selective elements that participate in remote snapshots based on defined policies. Embodiments of this disclosure disclose involving logical RLC channels to identify snapshot requirements in the internal 5G core cloud network. Embodiments of this disclosure disclose monitoring applications that require snapshots and, accordingly, managing to trigger, restore, and refine chain element actions using virtual network function calls. When a snapshot of any application is triggered, an empty datastore is created and all subsequent changes are tracked. When any new write packet arrives at the same application datastore, the old data grain is moved to a copy datastore, and the incoming packet data may be written to its original location.

[0008] Embodiments of this disclosure disclose a method and system that operates in conjunction with 5G radio link control channel management and payload processing in an end-user device and provides a method for selectively snapshotting an application based on a radio link control channel parameter handshake. Embodiments of this disclosure disclose a thin device driver layer implemented within an end-user system that has knowledge of the application and the RLC channel mapping to the application. Embodiments of this disclosure disclose creating multiple radio link control channels from an end-user device and assigning the multiple radio link control channels to an application to suit specific packet routing requirements. Embodiments of this disclosure disclose using the multiple radio link control channels to determine a snapshot on the data grain in a virtual network function of a 5G telecommunications network. Embodiments of this disclosure disclose a virtual network function of a 5G network that maintains an allow list of snapshot-enabled channels communicating from a radio interface and extending to a bearer (e.g., an S1 bearer). The S1 bearer may provide connectivity between a base station (e.g., an evolved node B or eNode B) and a home serving gateway. The eNodeB may be hardware connected to a cellular network that communicates wirelessly directly with cellular devices, such as a transceiver base station in the network. The virtual network function may maintain a map of all logical IDs from which application-level snapshots are activated, and accordingly trigger the initial (e.g., denoted as T0) data copy management of the core / edge cloud whenever any new write packet is received for each application. End-user level instances may manage all applications subscribed to selective space-saving snapshots (e.g., FlashCopy) of 5G applications, and manage the routing of incoming packets to the Service Data Adaptation Protocol (SDAP) layer.When an application packet reaches the SDAP layer on an end-user device, the application packet may first check the workload type, such as read or write. Since data read operations over the network do not affect the internal copy, the internal copy can be routed along its normal path. If the application is writing data to a remote datastore allocation, the instance in the end-user device queries the application's copy management requirements for the received grain pack. The application may maintain its own data structures using policies defined for specific data where the snapshot (e.g., FlashCopy) requirement is "yes" or "no". This information applies to application-level radio link control channels. For radio link control channel allocations on systems without a base operating system or installed applications (e.g., bare metal), packet data may be handed over to the SDAP along with additional system flags indicating the requirements for copy management actions in the internal cloud system.

[0009] Embodiments of this disclosure disclose RLC channel selection that may be performed by an application in an application-level packet transmission method based on whether an initiated write pack requires data retention. If the location of newly written data is not critical for tracking changes, RLC channel selection may select a designated untrackable RLC channel for the packet. The packet may be sent to the RLC layer with a defined RLC identifier that may have a setting to not track changes in an application-level snapshot in the cloud. On the other hand, if the application is writing sensitive information that must be tracked, the packet may be wrapped in a designated RLC header with a defined identifier for tracking enablement. In the case of a bare-metal channel allocation policy, when messages and packets are received at the SDAP, RLC channel selection may select an RLC instance based on the nature of the tracking requirements and old data retention policies sent to the SDAP by the application via the platform interface.

[0010] Embodiments of this disclosure disclose creating RLC channels. Embodiments of this disclosure disclose exchanging additional parameters for tracking state stored by each party participating in the communication. When an arbitrary write packet is received by the virtual network function, the write packet may extract the application identifier and the respective RLC channel identifier from the packet header. Once the channel identifiers are located, these identifiers may be mapped to a local virtual network function data structure for trace activation. If RLC identifiers for trace activation are found, the source data may be overwritten with new application data, and the original data may be stored in the target datastore. Source copies and target copies may be used by various applications for various purposes. In this case, since a particular RLC channel is designed to send data to the datastore, data tracking is calculated by the copy data management system in the virtual network function, and the FlashCopy of each grain is updated. Furthermore, application data chaining and tracking may be enabled. The virtual network function may understand the SADP header for RLC identifiers belonging to a list that needs to be tracked in dependency chaining. On the other hand, data that is not critical and does not require copy data management may be received on a separate set of RLC channels. In such cases, the data block may be discarded, and new data may be stored in the same grain location as before without calling the copy data management system. Since the data is not moved to another store, the data saves storage requirements for the data store, thereby providing a spatial advantage for remote storage for managing application data. Furthermore, embodiments of this disclosure disclose that the effectiveness of copy management capabilities of virtual network functions is improved by saving computational requirements for managing dependency chaining between data store objects during the addition / removal of intermediate objects and optimizing the overall workload using 5G RLC tunnels for application write packs.

[0011] Embodiments of this disclosure disclose that critical application data traffic exhaustion is eliminated because the correct data sets are moved to edge clouds with the correct snapshot requirements. Embodiments of this disclosure disclose that a user-friendly experience is provided that saves storage space in telecommunications networks. Embodiments of this disclosure disclose that a user-defined method is enabled for controlling application-beneficial edge computing. Embodiments of this disclosure disclose the enabling of cognitive systems for capturing additional information in the cloud and for user-based service propagation.

[0012] Embodiments of this disclosure disclose controlling selective elements that participate in remote snapshots based on defined policies. Embodiments of this disclosure disclose selective control over data to internal elements managed by virtual network functions that are not accessible over the radio. Embodiments of this disclosure disclose exchanging additional parameters for tracking state stored by each party participating in the communication. Embodiments of this disclosure disclose maintaining a map of all logical ids from which application-level snapshots are activated.

[0013] Next, the present disclosure will be described in detail with reference to the drawings. Figure 1 is a functional block diagram showing an edge cloud application backup environment, generally indicated as 100, according to one embodiment of the present disclosure.

[0014] In the illustrated embodiment, the edge cloud application backup environment 100 includes a computing device 102, a base station 104, a user device 110, a data store 106, and a network 108. In one or more embodiments of the Disclosure, the base station 104 may be a node in a telecommunications network. In one example, the telecommunications network may be a 5G network. In one example, the base station 104 may be called an evolved node B or eNodeB. The base station 104 is a critical part of the wireless network and may perform network control functions in addition to creating mobile network coverage. In the illustrated example, only one base station is shown. However, in other examples, there may be multiple base stations in the telecommunications network. In one example, an S1 bearer (not shown) may provide connectivity between the base station 104 and a serving gateway.

[0015] In one or more embodiments of the present disclosure, the datastore 106 may be a repository for storing and managing collections of data. For example, the datastore 106 may be a database or a repository for databases. For example, the datastore 106 may store data from user devices 110 and computing devices 102. In the illustrated embodiment, the datastore 106 is located externally and accessed through a communication network such as network 108. However, in other embodiments, the datastore 106 may be located on user devices 110 and computing devices 102. In one embodiment, the datastore 106 may store snapshot backups or other preferred backups (e.g., FlashCopy(R)). For example, the snapshot backup may be either a full copy snapshot or a space-efficient snapshot. The type of snapshot backup may depend on the storage environment. During a full copy snapshot, all blocks of data on the source volume may be copied to the target volume. During a space-efficient snapshot, only blocks of data written to the source volume after the snapshot was created may be copied to the target volume.

[0016] In various embodiments of this disclosure, the user device 110 may be a laptop computer, tablet computer, netbook computer, personal computer (PC), desktop computer, mobile phone, smartphone, smartwatch, wearable computing device, personal digital assistant (PDA), or server. In one embodiment, the user device 110 is a mobile device. Generally, the user device 110 may be any computing device or combination of devices having access to the network 108 and may communicate with the base station 104. The user device 110 may include internal and external hardware components, as will be illustrated and described in more detail with respect to Figure 8.

[0017] Furthermore, in the illustrated embodiment, the user device 110 includes an RLC channel management system 112 and an application 114. In the illustrated embodiment, the RLC channel management system 112 and the application 114 are located on the user device 110. However, in other embodiments, the RLC channel management system 112 and the application 114 may be located externally and accessed through a communication network such as network 108. In one or more embodiments, the RLC channel management system 112 is configured to manage in-band selective data snapshots using RLC channels for edge cloud application backup. The RLC channel management system 112 may provide a method for selective snapshots of applications based on an RLC channel parameter handshake. The RLC channel management system 112 may include a thin device driver layer implemented within the user device 110 that has knowledge of the application 114 and the RLC channel mapping to the application 114. RLC channel management 112 may provide services to RLC layer control in the form of logical channels. These logical channels are virtualized communication network interfaces used to transfer input / output commands (network data packets) and control instructions over the radio interface and network 108. Logical channels may be defined by the type of information they carry. For example, a logical channel may be a control channel used for transmitting control and configuration information. In another example, a logical channel may be a traffic channel used for user data. RLC channel management 112 may create multiple logical channels on a single radio bearer network using a network slicing model. RLC channel management 112 may use logical channels to carry specialized traffic from user devices 110 to network 108. RLC channel management 112 may create multiple channels from a single device (e.g., user device 110) to network 108.The RLC channel management 112 can realize channels with parallel packet transmission and can reduce exclusive locks on network resources, thereby providing performance advantages. The RLC channel management 112 may generate multiple RLC channels and assign multiple RLC channels to application 114 to suit dedicated packet routing requirements. The RLC channel management 112 may determine a snapshot of the data grain (e.g., FlashCopy(R)) in the virtual network function of network 108.

[0018] In various embodiments of this disclosure, the computing device 102 may be a laptop computer, tablet computer, netbook computer, PC, desktop computer, mobile phone, smartphone, smartwatch, wearable computing device, PDA, or server. In another embodiment, the computing device 102 represents a computing system that utilizes clustered computers and components to act as a single pool of seamless resources. In yet another embodiment, the computing device 102 may represent a server computing system that utilizes multiple computers as a server system, such as in a cloud computing environment. Generally, the computing device 102 may be any computing device or combination of devices having access to the virtual network function module 120 and the network 108, and capable of processing program instructions and executing the virtual network function module 120 according to embodiments of this disclosure. The computing device 102 may include internal and external hardware components, as illustrated and described in more detail with respect to Figure 8.

[0019] Furthermore, in the illustrated embodiment, the computing device 102 includes a virtual network function module 120. In the illustrated embodiment, the virtual network function module 120 is located on the computing device 102. However, in other embodiments, the virtual network function module 120 may be located externally and accessed through a communication network such as network 108. The communication network may be, for example, a local area network (LAN), a wide area network (WAN) such as the Internet, or a combination of the two, and may include wired connections, wireless connections, fiber optic connections, or any other connections known in the art. Generally, the communication network may be any combination of connections and protocols that support communication between the computing device 102 and the virtual network function module 120 according to a desired embodiment of the present disclosure.

[0020] In one or more embodiments, the virtual network function module 120 is configured to create one or more RLC channels for forwarding network data packets within a network 108 using network slicing techniques. In one example, network slicing may be a network architecture that enables multiplexing of independent, virtualized logical networks over the same physical network infrastructure. Each network slice may be a separate end-to-end network tailored to meet the diverse requirements demanded by specific applications. In one example, an RLC channel is a logical channel of a virtualized communication network interface used to transfer input / output commands (network data packets) and control instructions via a radio interface and the network 108. A logical channel may be defined by the type of information that the logical channel carries. In one example, a logical channel may be used as a control channel for transmitting control and configuration information. In another example, a logical channel may be used as a traffic channel for user data. The virtual network function module 120 may create a plurality of logical channels over a single radio bearer network using a network slicing model. These channels are used to carry specialized traffic from the user device 110 to the network 108. Since multiple channels are created from a single device to the network 108, the channels achieve parallelism for packet transmission while reducing exclusive locking of network resources, thereby providing performance advantages.

[0021] The virtual network function module 120 may exchange additional parameters for tracking states saved by each party participating in the communication. The virtual network function module 120 may maintain an allow list of snapshot-enabled channels communicating from the radio interface and similarly extending to the S1 bearer. The virtual network function module 120 may maintain a map of all logical identifiers that activate application-level snapshots (e.g., FlashCopy(R)), and therefore, when any new write packet for each application is received, it may trigger data copy management in the core / edge cloud. The virtual network function module 120 may manage all applications registered for the selective space-saving FlashCopy(R) of application 114, and routing of incoming packets to the Service Data Adaptation Protocol (SDAP) layer. The SDAP layer may be responsible for mapping quality-of-service flows from the 5G core network to data radio bearers, as well as marking quality-of-service flow identifiers in uplink and downlink packets. In telecommunications, bearer services or data services are services that enable the transmission of informational signals between network interfaces. These services provide subscribers with the capacity necessary to transmit appropriate signals between specific access points, i.e., between user network interfaces.

[0022] The virtual network function module 120 may activate network data processing and control protocol data units. The virtual network function module 120 may activate respective lists of RLC channels for selective point-in-time data copying of application data. The virtual network function module 120 may create a data traffic channel. The virtual network function module 120 may open RLC channels from the user device 110 and issue application bindings associated with each of the RLC channels. The virtual network function module 120 may initiate a thin device driver layer in the user device 110 that has knowledge of the applications 114 and the RLC channel mapping for the applications 114.

[0023] In one or more embodiments, the virtual network function module 120 is configured to assign one or more RLC channels to an application 114 in a user device 110. The virtual network function module 120 may assign multiple RLC channels to the application 114 to suit specific packet routing requirements. The virtual network function module 120 may use multiple RLC channels to determine snapshots on the data grain in the virtual network function of network 108. The virtual network function module 120 may control selective elements within the application 114 that participate in remote snapshots based on defined policies. The virtual network function module 120 may identify snapshot requirements in network 108 (e.g., an internal 5G core cloud network). The virtual network function module 120 can eliminate depletion of critical application data traffic because the correct data sets are moved to edge clouds with the correct snapshot requirements. The virtual network function module 120 can provide a user experience that saves storage space in network 108 (e.g., a 5G core cloud network). The virtual network function module 120 may enable a user-defined method for controlling edge computing that is beneficial to application 114. The virtual network function module 120 may control selective elements that participate in remote snapshots based on defined policies. The virtual network function module 120 may selectively control data to internal elements managed by virtual network functions that are not accessible over the radio. The virtual network function module 120 may allocate multiple RLC channels to application 114 to suit specific packet routing requirements.The virtual network function module 120 may select an RLC channel to take a snapshot (e.g., FlashCopy(R)) of the data grain in the virtual network function of network 108 (e.g., a 5G telecommunications network). The virtual network function module 120 may maintain an allow list of snapshot-enabled channels that communicate from the radio interface and are extended to the S1 bearer.

[0024] In one or more embodiments, the virtual network function module 120 is configured to map corresponding RLC channels and applications 114 to corresponding identifiers. The virtual network function module 120 may maintain a map of all logical identifiers for which application-level snapshots are activated. When any write packet is received by the virtual network function, the write packet may extract the application identifier and the respective RLC channel identifier from the packet header. Once the channel identifiers are located, these identifiers may be mapped to a local virtual network function data structure for trace activation. When the RLC identifiers for trace activation are found, the source data may be overwritten with new application data, and the original data may be stored in the data store 106. Source copies and target copies may be used by various applications for various purposes. In this case, since a particular RLC channel is designed to send data to the data store 106, data tracking is calculated by the copy data management system in the virtual network function, and the FlashCopy for each grain is updated. Furthermore, the virtual network functionality can understand SADP headers relating to RLC identifiers belonging to a list that needs to be tracked in dependency chaining, thus enabling the chaining and tracking of application data. On the other hand, data that is not critical and does not require copy data management may be received on a separate set of RLC channels. In such cases, the initial data block (e.g., denoted as T0) may be discarded, and the new data may be stored in the same grain location as before without calling the copy data management system. Since the T0 data is not moved to another store, the T0 data saves storage requirements for datastore 106, thereby providing a spatial advantage for remote storage for managing application data.Furthermore, the virtual network function module 120 can save computational requirements for managing dependency chaining between datastore objects during the addition / removal of intermediate objects, and can improve the effectiveness of the virtual network function's copy management capabilities by optimizing the overall workload using the RLC channel of the application write pack.

[0025] In one or more embodiments, the virtual network function module 120 is configured to monitor applications 114 that require snapshots. The virtual network function module 120 may manage to trigger, restore, and refine chain element operations using virtual network function calls. When a snapshot of any application is triggered, an empty datastore is created and all subsequent changes are tracked. When any new write packet arrives at the same application datastore, the old data grain may be moved to a copy datastore, and the incoming packet data may be written to its original location. The virtual network function module 120 may maintain a map of all logical identifiers that activate application-level snapshots, and accordingly, when any new write packet is received for each application, it may trigger a first data copy management (e.g., denoted as T0) in the core / edge cloud. An end-user level instance may manage all applications 114 that are registered for selective space-saving snapshots of application 114 (e.g., FlashCopy), and the routing of incoming packets to the SDAP layer. When an application packet reaches the SDAP layer on user device 110, the virtual network function module 120 may first check the workload type, such as read or write. If the application is writing data to a remote datastore allocation, the instance within user device 110 queries the application's copy management requirements for the received grain pack. The virtual network function module 120 may maintain application-specific data structures with defined policies for certain data that have snapshot requirements. This information applies to application-level radio link control channels. The virtual network function module 120 may also apply application-specific data structures to application-level RLC channels.For systems without a basic operating system or installed applications (e.g., bare metal), the virtual network function module 120 may assign the RLC channel for packet data to the SDAP, along with additional system flags indicating the requirements for copy management actions in the internal cloud system.

[0026] In one or more embodiments, the virtual network function module 120 is configured to create a copy of the datastore associated with application 114 based on changes monitored in the application, in response to an application snapshot request. The virtual network function module 120 may perform RLC channel selection by application 114 based on whether the initiated pack write requires data preservation. For example, if the location of newly written data is not critical for tracking changes, the virtual network function module 120 may perform RLC channel selection using a specified untrackable RLC channel for the packet. The virtual network function module 120 may send the packet to the RLC layer with a defined RLC identifier that has a setting to not track changes to application-level snapshots in the cloud (e.g., FlashCopy). The virtual network function module 120 may determine whether application 114 is writing information that must be tracked. If the virtual network function module 120 determines that application 114 is writing information that must be tracked, the virtual network function module 120 may wrap the packet with a specified RLC header having a defined identifier for tracking enablement. Upon receiving an arbitrary write packet, the virtual network function module 120 may extract the application identifier and the respective RLC channel identifier from the packet header. The virtual network function module 120 may map the RLC channel identifier to a local data structure for tracking enablement. The virtual network function module 120 may determine whether the RLC channel identifier matches tracking enablement. If the virtual network function module 120 determines that the RLC channel identifier matches tracking enablement, the virtual network function module 120 may overwrite the source data with new application data in the data store 106. The virtual network function module 120 may save the original data to target data in the data store 106.The virtual network function module 120 may activate data tracking and update each grain. The virtual network function module 120 may perform copy-on-write. The virtual network function module 120 may deliver acknowledgments to the source datastore 106. In the case of a bare-metal channel allocation policy, when messages and packets are received at the SDAP layer, the virtual network function module 120 may select an RLC instance based on the nature of the tracking requirement sent to the SDAP layer via the platform interface and the aging data retention policy.

[0027] Furthermore, in the illustrated embodiment, the virtual network function module 120 includes an extraction module 122, a mapping module 124, and a data copy module 126. In the illustrated embodiment, the extraction module 122, the mapping module 124, and the data copy module 126 are located on the computing device 102 and the virtual network function module 120. However, in other embodiments, the extraction module 122, the mapping module 124, and the data copy module 126 may be located externally and accessed through a communication network such as network 108. In one or more embodiments, the extraction module 122 is configured to extract the application identifier and the respective RLC channel identifier from the packet header when the virtual network function module 120 receives any write packet. The extraction module 122 may locate the RLC channel identifier. The extraction module 122 may validate asynchronous event requests. The extraction module 122 may extract the read or write type of information from the received data packet. The extraction module 122 may detect the RLC channel identifier for trace enablement. Extraction module 122 may overwrite new application data or save the original data to the target data store. Source and target copies may be used by various applications for various purposes. Since specific RLC channels can send data to data store 106, extraction module 122 may calculate data tracking. Extraction module 122 may enable application data chaining and tracking. Extraction module 122 may recognize SDAP headers for RLC identifiers belonging to a list that needs to be tracked in dependency chaining. Meanwhile, data that is not critical and does not need to be copied may be assigned to a separate set of RLC channels.In such cases, the original data block (for example, labeled T0) may be discarded, and new data can be stored in the same grain location as before without calling the copy data management system. Since the T0 data is not moved to another store, the extraction module 122 can save on the storage requirements of the data store 106, which provides a spatial advantage for remote storage for managing application data.

[0028] In one or more embodiments, a mapping module 124 The mapping module is configured to map the corresponding RLC channel and application 114 to the corresponding identifier. 124 The application-level snapshot may maintain a map of all logical identifiers for which an application-level snapshot is activated. When an arbitrary write packet is received by the virtual network function, the write packet may extract the application identifier and the respective RLC channel identifier from the packet header. Once the channel identifier is located, it may be mapped to the local virtual network function data structure for trace activation. If the RLC identifier for trace activation is found, the source data may be overwritten with new application data, and the original data may be stored in datastore 106. Source copies and target copies may be used by various applications for various purposes. In this case, since a particular RLC channel is designed to send data to datastore 106, the copy data management system in the virtual network function calculates data traces and updates each grain. Furthermore, the mapping module 124 This may enable application data chaining and tracking. (Mapping module) 124 The mapping module may recognize the SDAP header for RLC identifiers belonging to a list that needs to track data in dependency chaining. 124A separate set of RLC channels may be allocated to application data that is not critical and does not need to be copied. In such a case, the t0 data block may be discarded, and new data may be stored in the same grain location as before without calling the copy data management system. Since the T0 data is not moved to another store, the T0 data saves storage requirements for datastore0_tx, thereby providing a spatial advantage for remote storage for managing application data. Furthermore, embodiments of this disclosure disclose that the effectiveness of the copy management function of the virtual network function is improved by saving computational requirements for managing dependency chaining between datastore objects during the addition / removal of intermediate objects and optimizing the overall workload using RLC channels for application write packs.

[0029] In one or more embodiments, a data copy module 126 The Data Copy Module is configured to respond to application snapshot requests by creating a copy of the datastore associated with the application based on the changes monitored within the application. 126 Application 114 may perform RLC channel selection based on whether the initiated pack write requires data preservation. For example, if the location of the newly written data is not critical for tracking changes, the data copy module may be used. 126 The RLC channel selection may be performed using an untrackable RLC channel specified for the packet. The virtual network function module 120 may send the packet to the RLC layer with a defined RLC identifier that has a setting to not track changes to application-level snapshots (e.g., FlashCopy) in the cloud. Data Copy Module 126 It may determine whether application 114 is writing information that needs to be tracked. Data copy module126 However, if it is determined that application 114 is writing information that must be tracked, the data copy module 126 The virtual network function module 120 may wrap the packet with a specified RLC header having a defined identifier for tracking activation. Upon receiving any write packet, the virtual network function module 120 may extract the application identifier and the respective RLC channel identifier from the packet header. The virtual network function module 120 may map the RLC channel identifier to a local data structure for tracking activation. Data copy module 126 This may determine whether the RLC channel identifier matches trace enablement. (Data Copy Module) 126 However, if the RLC channel identifier is determined to match trace enablement, the data copy module 126 The source data may be overwritten with new application data in datastore 106. (Data copy module) 126 The original data may be saved to the target data in datastore 106. (Data copy module) 126 The data copy module may activate data tracking and update each grain. 126 The data copy module may perform copy-on-write. 126 The data copy module may deliver an acknowledgment to the source data store 106. In the case of a bare metal channel allocation policy, when messages and packets are received at the SDAP layer, the data copy module 126 The RLC instance may be selected based on the nature of the tracking requirements and legacy data retention policies sent to SDAP by the application via the platform interface.

[0030] Figure 2 is a flowchart 200 showing the operation steps of a virtual network function module 120 according to one embodiment of the present disclosure.

[0031] The virtual network function module 120 operates to create one or more RLC channels for forwarding network data packets within the network 108 using network slicing technology. The virtual network function module 120 also operates to assign one or more RLC channels to applications 114 in the user device 110. The virtual network function module 120 operates to map the corresponding RLC channels and applications 114 to their respective identifiers. The virtual network function module 120 operates to monitor applications 114 that require snapshots. In response to an application snapshot request, the virtual network function module 120 operates to create a copy of the datastore associated with application 114 based on the changes monitored in the application.

[0032] In step 202, the virtual network function module 120 creates one or more RLC channels for forwarding network data packets within network 108 using network slicing technology. For example, network slicing may be a network architecture that enables multiplexing of virtualized independent logical networks on the same physical network infrastructure. Each network slice may be an isolated end-to-end network tailored to meet the diverse requirements demanded by a particular application. For example, an RLC channel is a logical channel of a virtualized communication network interface used to forward input / output commands (network data packets) and control instructions over the radio interface and network 108. A logical channel may be defined by the type of information it carries. For example, a logical channel may be used as a control channel for transmitting control and configuration information. For example, a logical channel may be used as a traffic channel for user data. The virtual network function module 120 may use the network slicing model to create multiple logical channels on a single radio bearer network. These channels are used to carry specialized traffic from user device 110 to network 108. Since multiple channels are created from a single device to network 108, the channels enable parallelism in packet transmission and reduce exclusive locking of network resources, resulting in performance advantages.

[0033] The virtual network function module 120 may exchange additional parameters for tracking states saved by each party participating in the communication. The virtual network function module 120 may maintain an allow list of snapshot-enabled channels communicating from the radio interface and similarly extending to the S1 bearer. The virtual network function module 120 may maintain a map of all logical identifiers that activate application-level snapshots (e.g., FlashCopy(R)), and therefore, when any new write packet for each application is received, it may trigger data copy management in the core / edge cloud. The virtual network function module 120 may manage all applications registered for selective space-saving FlashCopy(R) of application 114, and routing of incoming packets to the Service Data Adaptation Protocol (SDAP) layer. The SDAP layer may be responsible for mapping quality-of-service flows from the 5G core network to data radio bearers, as well as marking quality-of-service flow identifiers in uplink and downlink packets. In telecommunications, bearer services or data services may be services that enable the transmission of informational signals between network interfaces. These services provide subscribers with the capacity necessary to transmit appropriate signals between specific access points, i.e., between user network interfaces.

[0034] The virtual network function module 120 may activate the processing of network data and control protocol data units. The virtual network function module 120 may activate each list of RLC channels for selective point-in-time data copying of application data. The virtual network function module 120 may create data traffic channels. The virtual network function module 120 may open RLC channels from the user device 110 and issue application bindings associated with each RLC channel. The virtual network function module 120 may initiate a thin device driver layer in the user device 110 that has knowledge of application 114 and the RLC channel mapping to application 114.

[0035] In step 204, the virtual network function module 120 assigns one or more RLC channels to application 114 in user device 110. The virtual network function module 120 may assign multiple RLC channels to application 114 to suit specific packet routing requirements. The virtual network function module 120 may use multiple RLC channels to determine snapshots on the data grain in the virtual network function of network 108. The virtual network function module 120 may control selective elements within application 114 that participate in remote snapshots based on defined policies. The virtual network function module 120 may identify snapshot requirements in network 108 (e.g., internal 5G core cloud network). The virtual network function module 120 can eliminate depletion of critical application data traffic because the correct data sets are moved to edge clouds with the correct snapshot requirements. The virtual network function module 120 can provide a user experience that saves storage space in network 108 (e.g., 5G core cloud network). The virtual network function module 120 may enable a user-defined method for controlling edge computing that is beneficial to application 114. The virtual network function module 120 may control selective elements that participate in remote snapshots based on defined policies. The virtual network function module 120 may selectively control data to internal elements managed by virtual network functions that are not accessible over the radio. The virtual network function module 120 may allocate multiple RLC channels to application 114 to suit specific packet routing requirements.The virtual network function module 120 may select an RLC channel to take a snapshot (e.g., FlashCopy(R)) of the data grain in the virtual network function of network 108 (e.g., a 5G telecommunications network). The virtual network function module 120 may maintain an allow list of snapshot-enabled channels that communicate from the radio interface and are extended to the S1 bearer.

[0036] In step 206, the virtual network function module 120 maps the corresponding RLC channels and applications 114 to their respective identifiers. The virtual network function module 120 may maintain a map of all logical identifiers for which application-level snapshots are activated. When any write packet is received by the virtual network function, the write packet may extract the application identifier and the respective RLC channel identifier from the packet header. Once the channel identifiers are located, these identifiers may be mapped to the local virtual network function data structure for trace activation. If the RLC identifiers for trace activation are found, the source data may be overwritten with new application data, and the original data may be stored in the data store 106. Source copies and target copies may be used by various applications for various purposes. In this case, since a particular RLC channel is designed to send data to the data store 106, the copy data management system in the virtual network function calculates data tracking and updates the FlashCopy for each grain. Furthermore, the virtual network functionality can understand SADP headers relating to RLC identifiers belonging to a list that needs to be tracked in dependency chaining, thus enabling the chaining and tracking of application data. On the other hand, data that is not critical and does not require copy data management may be received on a separate set of RLC channels. In such cases, the initial data block (e.g., denoted as T0) may be discarded, and the new data may be stored in the same grain location as before without calling the copy data management system. Since the T0 data is not moved to another store, the T0 data saves storage requirements for datastore 106, thereby providing a spatial advantage for remote storage for managing application data.Furthermore, the virtual network function module 120 can save computational requirements for managing dependency chaining between datastore objects during the addition / removal of intermediate objects, and can improve the effectiveness of the virtual network function's copy management capabilities by optimizing the overall workload using the RLC channel of the application write pack.

[0037] In step 208, the virtual network function module 120 monitors the application 114 that requires a snapshot. The virtual network function module 120 may use virtual network function calls to trigger, restore, and refine chain element operations. When a snapshot of any application is triggered, an empty datastore is created and all subsequent changes are tracked. When any new write packet arrives at the same application datastore, the old data grain may be moved to a copy datastore, and the incoming packet data may be written to its original location. The virtual network function module 120 may maintain a map of all logical identifiers that activate application-level snapshots, and accordingly, when any new write packet is received for each application, it may trigger a first data copy management (e.g., denoted as T0) in the core / edge cloud. End-user level instances may manage all applications 114 that are enrolled in a selective space-saving snapshot of application 114 (e.g., FlashCopy), and the routing of incoming packets to the SDAP layer. When an application packet reaches the SDAP layer on user device 110, the virtual network function module 120 may first check the workload type, such as read or write. If the application is writing data to a remote datastore allocation, the instance within user device 110 queries the application's copy management requirements for the received grain pack. The virtual network function module 120 may maintain application-specific data structures with defined policies for certain data that have snapshot requirements. This information applies to application-level radio link control channels. The virtual network function module 120 may also apply application-specific data structures to application-level RLC channels.For systems without a basic operating system or installed applications (e.g., bare metal), the virtual network function module 120 may assign the RLC channel for packet data to the SDAP, along with additional system flags indicating the requirements for copy management actions in the internal cloud system.

[0038] In step 210, the virtual network function module 120, in response to the application's snapshot request, creates a copy of the datastore associated with application 114 based on the changes monitored by the application. The virtual network function module 120 may perform RLC channel selection by application 114 based on whether the initiated pack write requires data preservation. For example, if the location of newly written data is not critical for tracking changes, the virtual network function module 120 may perform RLC channel selection using a specified untrackable RLC channel for the packet. The virtual network function module 120 may send the packet to the RLC layer with a defined RLC identifier that has a setting to not track changes to application-level snapshots in the cloud (e.g., FlashCopy). The virtual network function module 120 may determine whether application 114 is writing information that must be tracked. If the virtual network function module 120 determines that application 114 is writing information that must be tracked, the virtual network function module 120 may wrap the packet with a specified RLC header that has a defined identifier for tracking enablement. Upon receiving an arbitrary write packet, the virtual network function module 120 may extract the application identifier and the respective RLC channel identifier from the packet header. The virtual network function module 120 may map the RLC channel identifier to a local data structure for tracking enablement. The virtual network function module 120 may determine whether the RLC channel identifier matches tracking enablement. If the virtual network function module 120 determines that the RLC channel identifier matches tracking enablement, the virtual network function module 120 may overwrite the source data with new application data in the data store 106. The virtual network function module 120 may save the original data to target data in the data store 106.The virtual network function module 120 may activate data tracking and update each grain. The virtual network function module 120 may perform copy-on-write. The virtual network function module 120 may deliver acknowledgments to the source datastore 106. In the case of a bare-metal channel allocation policy, when messages and packets are received at the SDAP layer, the virtual network function module 120 may select an RLC instance based on the nature of the tracking requirements and aging data retention policy sent to the SDAP layer via the platform interface.

[0039] Figure 3 shows an exemplary functional diagram of the virtual network function module 120 according to this disclosure.

[0040] In the example in Figure 3, the virtual network function module 120 may communicate with the base station 104 (labeled E-Node B), the edge cloud 302, and the core cloud 304. The virtual machine (VM) 306 may run programs, store data, and connect to the edge cloud 302 and the core cloud 304. Data 314 may be transmitted between the edge cloud 302 and the core cloud 304. Data 314 may be stored in the datastore 106, for example, a solid-state drive (SSD) 308, a hard disk drive (HDD) 310, and nearline storage 312.

[0041] Figure 4 shows an exemplary functional diagram of a user device 110 according to one embodiment of the present disclosure.

[0042] In the example in Figure 4, user device 110 may be a mobile device used by user 402. User device 110 may include SDAP layer 404, Packet Data Convergence Protocol (PDCP) layer 406, RLC layer 408, and Media Access Control (MAC) layer 410. SDAP layer 404 may include RLC locator and multiplexing logic 412, requirements collection and mapping 414, application tunnel assignment 416, user-initiated consent manager 418, snapshot requirements manager 420, copy data manager 422, asynchronous event request / response 424, and RLC decoder 426.

[0043] Figure 5 shows an exemplary functional diagram of a data store 106 according to one embodiment of the present disclosure.

[0044] In the example shown in Figure 5, user device 110 may have a datastore access path to datastore 106. In one example, datastore 106 (e.g., integrated storage pool 520) may be shown to include datastore0-master 502, datastore0-aux_t1 504, datastore0-aux_t2 506, datastore0-aux_t3 508, datastore0-aux_t4 510, datastore0-aux_t5 512, and so on.

[0045] Figure 6 shows an exemplary service path of a virtual network function module 120 according to one embodiment of the present disclosure. Figure 6 shows the access path from the user device 110 to the base station 104, and from the base station 104 to the service gateway (S-GW) 602. Figure 6 also shows the service path 604 from the S-GW 602 to the virtual network function module 120, and then to the endpoint 606.

[0046] Figure 7 shows an exemplary functional diagram of a virtual network function module 120 according to one embodiment of the present disclosure.

[0047] In the example in Figure 7, in block 702, the virtual network function module 120 may allocate an RLC channel when a packet is received. The virtual network function module 120 may perform header decoding logic. In block 704, the virtual network function module 120 may verify asynchronous event responses. The virtual network function module 120 may extract the packet header. The virtual network function module 120 may extract the packet read / write type information. In block 706, the virtual network function module 120 may extract the RLC identifier and perform policy mapping. The virtual network function module 120 may perform remote data management. The virtual network function module 120 may perform RLC tunnel and datastore policy mapping. The virtual network function module 120 may perform data copy management based on application datastore timelines and dependency chaining. In block 708, the virtual network function module 120 may perform delta tracking. The virtual network function module 120 may perform bitmap management. The virtual network function module 120 may perform a packed write update. The virtual network function module 120 may perform a copy-on-write. In block 710, user data may include a propagation range. Logical addresses and information may be stored in the grain header.

[0048] Figure 8 shows a block diagram 400 of the components of computing device 102 and user device 110 according to exemplary embodiments of the present disclosure. It should be understood that Figure 8 provides only an example of one implementation and does not imply any limitation to the environment in which different embodiments may be implemented. Many modifications may be made to the illustrated environment.

[0049] The computing device 102 and user device 110 may include a communication fabric 802 that provides communication between a cache 816, memory 806, persistent storage 808, a communication unit 810, and an input / output (I / O) interface 812. The communication fabric 802 can be implemented using any architecture designed to pass data or control information, or both, between a processor (such as a microprocessor, communication and network processor), system memory, peripheral devices, and any other hardware components in the system. For example, the communication fabric 802 can be implemented using one or more buses or crossbar switches.

[0050] Memory 806 and persistent storage 808 are computer-readable storage media. In this embodiment, memory 806 includes random-access memory (RAM). Generally, memory 806 can include any suitable volatile or non-volatile computer-readable storage media. Cache 816 is a high-speed memory that improves the performance of the computer processor 804 by holding recently accessed data from memory 806 and data close to the accessed data.

[0051] The virtual network function module 120 may be stored in persistent storage 808 and memory 806 so that it can be executed by one or more of the respective computer processors 804 via cache 816. In one embodiment, persistent storage 808 includes a magnetic hard disk drive. As an alternative to or in addition to the magnetic hard disk drive, persistent storage 808 may include a solid-state hard drive, a semiconductor storage device, read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, or any other computer-readable storage medium capable of storing program instructions or digital information.

[0052] The media used by persistent storage 808 may be removable. For example, a removable hard drive may be used for persistent storage 808. Other examples include optical and magnetic disks, thumb drives, and smart cards that are inserted into the drive for transfer to another computer-readable storage medium, which is also part of persistent storage 808.

[0053] In these examples, the communication unit 810 provides communication with other data processing systems or devices. In these examples, the communication unit 810 includes one or more network interface cards. The communication unit 810 may provide communication by using either or both physical communication links and wireless communication links. The virtual network function module 120 may be downloaded to persistent storage 808 through the communication unit 810.

[0054] The input / output interface 812 enables data input and output to and from other devices that may be connected to the computing device 102 and the user device 110. For example, the input / output interface 812 may provide a connection to an external device 818 such as a keyboard, keypad, touchscreen, or any other suitable input device or combination thereof. The external device 818 may also include portable computer-readable storage media such as a thumb drive, portable optical or magnetic disk, and memory card. Software and data used to practice embodiments of the present invention, such as the virtual network function module 120, can be stored on such portable computer-readable storage media and can be loaded into persistent storage 808 via the input / output interface 812. The input / output interface 812 also connects to the display 820.

[0055] The display 820 provides a mechanism for displaying data to the user and may be, for example, a computer monitor.

[0056] The programs described herein are identified based on the application in which they are intended to be implemented in particular embodiments of the present invention. However, it should be understood that any particular program naming convention used herein is merely for convenience and therefore the present invention should not be limited to use only in the specific application identified, implied, or both by such naming convention.

[0057] The present invention may be an integrated system, method, or computer program product or combination thereof at any possible level of technical detail. The computer program product may include a computer-readable storage medium (or a plurality of computer-readable storage media) having computer-readable program instructions for causing a processor to carry out aspects of the present invention.

[0058] A computer-readable storage medium can be a tangible device capable of holding and storing instructions for use by an instruction execution device. A computer-readable storage medium can be, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any preferred combination thereof. A non-exhaustive list of more specific examples of computer-readable storage media includes portable computer 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), portable compact disk read-only memory (CD-ROM), digital versatile disks (DVDs), memory sticks, floppy disks, mechanically encoded devices such as punch cards or grooved raised structures on which instructions are recorded, and any preferred combination thereof. The computer-readable storage media used herein should not be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through optical fiber cables), or electrical signals transmitted through wires.

[0059] The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to each computing / processing device, or to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, or a wireless network, or a combination thereof. The network may include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, or edge servers, or a combination thereof. A network adapter card or network interface in each computing / processing device receives computer-readable program instructions from the network and transfers those computer-readable program instructions for storage in a computer-readable storage medium within the respective computing / processing device.

[0060] The computer-readable program instructions for performing the operation of the present invention may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, configuration data for integrated circuits, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python(R) and C++, and procedural programming languages ​​such as the C programming language or similar programming languages. The computer-readable program instructions may be executed as a standalone software package entirely on the user's computer, partially on the user's computer, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or a server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it may be connected to an external computer (for example, via the Internet using an Internet service provider). In some embodiments, to carry out aspects of the present invention, an electronic circuit including, for example, a programmable logic circuit, a field-programmable gate array (FPGA), or a programmable logic array (PLA) may execute a computer-readable program instruction by personalizing the electronic circuit using state information of the computer-readable program instruction.

[0061] This specification describes aspects of the present invention with reference to flowcharts or block diagrams, or both, of methods, apparatus (systems), and computer program products according to embodiments of the present invention. It will be understood that each block in the flowcharts or block diagrams, or both, and combinations of blocks in the flowcharts or block diagrams, or both, can be implemented by computer-readable program instructions.

[0062] These computer-readable program instructions may be provided to a computer processor or other programmable data processing device so as to create a machine, by creating means for instructions executed via the processor of a computer or other programmable data processing device to perform functions / operations specified in one or more blocks of a flowchart or block diagram, or both. These computer-readable program instructions may also be stored on a computer-readable storage medium so as to contain a product containing instructions that perform modes of functions / operations specified in one or more blocks of a flowchart or block diagram, or both, and can instruct a computer, programmable data processing device, or other device or combination thereof to function in a particular manner.

[0063] Computer-readable program instructions may also be loaded into a computer, other programmable data processing device, or other device to create a computer execution process in which instructions executed on a computer, other programmable device, or other device perform a function / action specified in one or more blocks of a flowchart or block diagram, or both, causing the computer, other programmable device, or other device to execute a series of operational steps.

[0064] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of instructions containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions described in a block may be performed in an order different from the order shown in the figure. For example, two blocks shown consecutively may actually be achieved as a single step, or executed simultaneously, substantially simultaneously, partially or entirely, in a temporally overlapping manner, or in some cases, those blocks may be executed in reverse order, depending on the functionality involved. It should also be noted that each block in a block diagram or flowchart, or both, and combinations of blocks in a block diagram or flowchart, or both, may be implemented by a dedicated hardware-based system that performs a specified function or operation, or performs a combination of dedicated hardware and computer instructions.

[0065] The descriptions of various embodiments of the present invention are presented for illustrative purposes only and are not intended to be exhaustive or limitful to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope of the invention. The terminology used herein has been selected to best describe the principles of the embodiments, practical applications, or technical improvements beyond the technology available on the market, or to enable those skilled in the art to understand the embodiments disclosed herein.

[0066] While this disclosure includes a detailed description of cloud computing, it should be understood that implementations of the teachings described herein are not limited to cloud computing environments. Rather, embodiments of the present invention can be implemented in conjunction with any other type of computing environment currently known or to be developed in the future.

[0067] Cloud computing is a service delivery model that enables convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services), allowing these computing resources to be provisioned and released quickly with minimal administrative effort or interaction with service providers. This cloud model may include at least five features, at least three service models, and at least four deployment models.

[0068] The features are as follows:

[0069] On-demand self-service: Cloud consumers can unilaterally provision computing functions such as server time and network storage automatically as needed, without requiring human interaction with the service provider.

[0070] Extensive network access: The functionality is available over the network and accessed through standard mechanisms that facilitate use by heterogeneous thin-client platforms or thick-client platforms (e.g., mobile phones, laptops, and PDAs).

[0071] Resource pooling: A provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically allocated and reallocated as needed. Consumers generally have no control or knowledge of the exact location of the resources provided, but can identify their location at a higher level of abstraction (e.g., country, state, or data center), thus demonstrating location independence.

[0072] Rapid Flexibility: Features can be provisioned quickly and flexibly, sometimes automatically, to rapidly scale out, and rapidly release and scale in. To consumers, the features available for provisioning often appear unlimited and can be purchased in any quantity at any time.

[0073] Service Measurement: Cloud systems automatically control and optimize resource usage by leveraging metric capabilities at a certain level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency to both service providers and consumers.

[0074] The service model is as follows:

[0075] Software as a Service (SaaS): This refers to the ability provided to consumers to use applications from a provider that run on cloud infrastructure. These applications are accessible from various client devices via thin-client interfaces, such as web browsers (e.g., web-based email). With the expected exception of limited user-specific application configuration settings, consumers do not manage or control the underlying cloud infrastructure, including the network, servers, operating system, storage, or individual application functionalities.

[0076] Platform as a Service (PaaS): A feature provided to consumers to deploy applications they have created or acquired, written using programming languages ​​and tools supported by the provider, onto cloud infrastructure. Consumers do not manage or control the underlying cloud infrastructure such as networks, servers, operating systems, or storage, but they do control the deployed applications and, in some cases, the applications that host the environment configuration.

[0077] Infrastructure as a Service (IaaS) is a feature provided to consumers to provision processing, storage, networking, and other basic computing resources, enabling them to deploy and run any software, including operating systems and applications. Consumers do not manage or control the underlying cloud infrastructure, but they do control the operating system, storage, and deployed applications, and in some cases, have limited control over selected network components (e.g., host firewalls).

[0078] The deployment model is as follows:

[0079] Private Cloud: A cloud infrastructure is operated exclusively for a specific organization. This cloud infrastructure may be managed by the organization or a third party and may reside on-premises or off-premises.

[0080] Community Cloud: Cloud infrastructure is shared by multiple organizations to support a specific community that shares common interests (e.g., missions, security requirements, policies, and compliance considerations). This cloud infrastructure may be managed by an organization or a third party and may reside on-premises or off-premises.

[0081] Public Cloud: Cloud infrastructure is available to the general public or large industry groups and is owned by organizations that sell cloud services.

[0082] Hybrid Cloud: Cloud infrastructure is a combination of two or more clouds (private, community, or public) that remain independent entities but are bound together by standardized or proprietary technologies that enable data and application portability (e.g., cloud bursting for load balancing across clouds).

[0083] Cloud computing environments are service-oriented, emphasizing statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is the infrastructure, including a network of interconnected nodes.

[0084] Referring now to Figure 9, an exemplary cloud computing environment 50 is shown. As shown, the cloud computing environment 50 includes one or more cloud computing nodes 10 that can communicate with local computing devices used by cloud consumers, such as personal digital assistants (PDAs) or mobile phones 54A, desktop computers 54B, laptop computers 54C, or automotive computer systems 54N or a combination thereof. The nodes 10 may communicate with each other. They may be physically or virtually grouped within one or more networks, such as private clouds, community clouds, public clouds, or hybrid clouds or a combination thereof, as described herein (not shown). This enables the cloud computing environment 10 to provide infrastructure, platforms, or software, or a combination thereof, as a service that does not require cloud consumers to maintain resources on their local computing devices. It should be understood that the types of computing devices 54A to 54N shown in Figure 9 are for illustrative purposes only, and that the computing node 10 and the cloud computing environment 50 can communicate with any type of computerized device via any type of network or network addressable connection or both (for example, using a web browser).

[0085] Referring now to Figure 10, a set of functional abstraction layers provided by the cloud computing environment 50 (Figure 9) is shown. It should be understood that the components, layers, and functions shown in Figure 10 are for illustrative purposes only, and embodiments of the present invention are not limited thereto. As shown, the following layers and corresponding functions are provided:

[0086] The hardware and software layer 60 includes hardware and software components. Examples of hardware components include a mainframe 61, RISC (Reduced Instruction Set Computer) architecture-based servers 62, 63, blade servers 64, storage devices 65, and network and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.

[0087] The virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: a virtual server 71, virtual storage 72, a virtual network 73 including a virtual private network, a virtual application and operating system 74, and a virtual client 75.

[0088] For example, the management layer 80 may provide the following functions: Resource provisioning 81 provides dynamic procurement of computing and other resources used to perform tasks within the cloud computing environment. Metering and pricing 82 provides cost tracking as resources are used within the cloud computing environment and billing or invoices for the consumption of these resources. For example, these resources may include application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides consumers and system administrators with access to the cloud computing environment. Service level management 84 provides allocation and management of cloud computing resources so that the required service levels are met. Service level agreement (SLA) planning and execution 85 provides pre-positioning and procurement of cloud computing resources that are expected to be required in the future in accordance with the SLA.

[0089] The workload layer 90 provides examples of functions that can be utilized in a cloud computing environment. Examples of workloads and functions that can be provided from this layer include mapping and navigation 91, software development and lifecycle management 92, virtual classroom education delivery 93, data analytics processing 94, transaction processing 95, and module 96, which includes, for example, the virtual network function module 120 described above with respect to an edge cloud application backup environment 100.

[0090] While specific embodiments of the present invention have been described, those skilled in the art will understand that other embodiments equivalent to those described exist. Therefore, it should be understood that the present invention is not limited by the specific embodiments shown, but only by the appended claims.

Claims

1. A method implemented in a computer, One or more processors create one or more radio link control (RLC) channels for forwarding network data packets within a telecommunications network using network slicing technology, One or more processors assign the one or more RLC channels to one or more applications within a user device in accordance with dedicated packet routing requirements, One or more processors map the application and the RLC channels for the application to corresponding identifiers, One or more processors monitor the one or more applications for backup, In response to receiving an application backup request, one or more processors create a copy of the datastore associated with the application based on changes monitored in the one or more applications. Methods that include...

2. The method according to claim 1, wherein the one or more RLC channels are logical channels of a virtualized communication network interface used to transfer input / output commands and control instructions, and the logical channels carry traffic in parallel from the user device to the telecommunications network.

3. The method according to claim 1, wherein mapping the application and the RLC channel to the application includes maintaining a map of all corresponding identifiers from which an application-level snapshot is activated.

4. Monitoring one or more of the aforementioned applications Maintain an allow list of snapshot-enabled channels from the RLC channel communicating from the wireless interface and bearer, Based on defined policies, control the selective elements within one or more applications that participate in the snapshot. The method according to claim 1, including the method described in claim 1.

5. The method according to claim 1, further comprising using one or more processors to perform RLC channel selection based on whether a data packet requires data storage.

6. In response to receiving a write data packet, one or more processors extract the application identifier and the respective RLC channel identifier from the packet header, One or more processors determine that the RLC channel identifier matches the application identifier for enabling tracking, One or more processors overwrite the source data with new application data in the data store. The method according to claim 1, further comprising:

7. One or more processors perform copy-on-write on the source data, One or more processors deliver an acknowledgment to the data store containing the source data. The method according to claim 6, further comprising:

8. A computer program for causing a computer to perform each of the steps of the method according to any one of claims 1 to 7.

9. A computer system, One or more computer processors, One or more computer-readable storage media, The program stored in the one or more computer-readable storage media and The program includes, and the program is one of the one or more computer processors. At the very least, to perform each step of the method according to any one of claims 1 to 7. It is a program. Computer system.

Images