COMMUNICATION SYSTEM AND METHOD FOR PROVIDING SERVICES WITH MOBILE RESOURCES - Patent application
The communication system optimally utilizes dynamic hardware resources by determining availability and deploying network functions on vehicles, addressing inefficiencies in service provision by leveraging time and location-dependent resource availability.
Patent Information
- Application Number
- JP2024506617
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-10-26
- Filing Date
- 2023-10-23
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2043-10-23
AI Technical Summary
Existing communication systems fail to efficiently utilize dynamic hardware resources, such as those in vehicles, which are underutilized when not in use, leading to inefficiencies in providing services due to their availability being time and location-dependent.
A communication system that includes a resource management component to determine available hardware resources based on location and time, using a resource information provisioning component to provide availability information, and a service delivery component to meet service requirements by deploying network functions on these resources.
Enables efficient utilization of dynamic resources by dynamically matching service requirements with available hardware resources, enhancing resource reusability and flexibility in service provision.
Smart Images

Figure 2024543763000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a communication system and method for providing services using movable (and therefore dynamic) resources. [Background technology]
[0002] Concepts such as network function virtualization make the provision of (e.g., communication) services increasingly flexible with respect to the hardware resources used to provide the services. At the same time, powerful hardware resources are becoming widely deployed, e.g., in vehicles, to provide driver assistance functions (or autonomous driving). Since these hardware resources are often unused (when the vehicle is not used for driving, e.g., for long periods such as at night), approaches to use these resources to provide services when they are available are desirable. Summary of the Invention
[0003] According to one embodiment, a communication system is provided, comprising: a resource information providing component configured to provide resource availability information comprising information about one or more locations where a hardware resource is temporarily available and information about one or more time periods when the hardware resource is available at the locations; a service provision component for providing a service (e.g. a communication service, but also a data processing service such as any kind of software application) configured to indicate requirements for one or more network functions for providing the service, the requirements comprising the locations where the one or more network functions should be provided and the time period when the one or more network functions should be provided; and a resource management component configured to determine hardware resources from among the hardware resources for providing the one or more network functions and to start providing the one or more network functions using the determined hardware resources, such that the indicated requirements for the one or more network functions can be met by providing the one or more network functions using the determined hardware resources. [Brief description of the drawings]
[0004] In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, with emphasis generally being placed upon illustrating the principles of the invention. In the following description, various aspects are described with reference to the following drawings: [Figure 1] SUMMARY OF THE DISCLOSURE A framework for managing a communications system and, in particular, communications resources of the communications system is presented. [Diagram 2] It shows the use of a rental car company's vehicles as a cloud of resources through a management and orchestration system (MANO). [Diagram 3] It illustrates the use of individual owner's vehicles 301 as a cloud of resources by MANO. [Figure 4] 1 illustrates time-varying resource management according to one embodiment. [Diagram 5] 1 illustrates a communication system according to one embodiment. [Figure 6] 1 shows a flow diagram illustrating a method for providing a service. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0005] The following detailed description refers to the accompanying drawings, which show by way of example specific details and aspects of the present disclosure in which the present invention may be practiced. Other aspects may be utilized, and structural, logical, and electrical changes may be made, without departing from the scope of the present invention. Various aspects of the present disclosure are not necessarily mutually exclusive, as some aspects of the present disclosure may be combined with one or more other aspects of the present disclosure to form new aspects.
[0006] Various examples corresponding to aspects of the present disclosure are described below.
[0007] The first embodiment is a communication system described below with reference to FIG.
[0008] Example 2 is the communication system of example 1, in which the one or more network functions include at least one of a core network function, an edge network function, and a wireless network function.
[0009] Example 3 is the communication system of example 1 or 2, wherein the resource management component is configured to at least partially forward the resource availability information to the service provision component, and the service provision component is configured to determine requirements such that they can be met by providing one or more network functions using the hardware resources.
[0010] Example 4 is the communication system of example 3, in which the resource management component is configured to remove the confidential information from the resource availability information and forward the remainder of the resource availability information to the service providing component.
[0011] Example 5 is the communication system of example 3 or 4, wherein the resource management component is configured to at least partially abstract the resource availability information and forward the abstracted resource availability information to the service provision component.
[0012] Example 6 is the communication system of example 5, in which abstracting the resource availability information includes reducing the accuracy of the information about the location.
[0013] Example 7 is the communication system of any one of Examples 3 to 6, wherein the resource management component is configured to receive from the service provision component an indication as to whether sensitive information should be transferred and / or an indication of details of the information to be transferred, and is configured to transfer the resource availability information at least in part in accordance with the indication.
[0014] Example 8 is the communication system of any one of Examples 1 to 7, wherein the resource management component is configured to determine hardware resources taking into account one or more requirements and / or characteristics of one or more network functions other than the location and the time period in addition to the location and the time period.
[0015] Example 9 is the communication system of any one of Examples 1 to 8, wherein the resource management component is configured to determine the hardware resource taking into account one or more requirements by the service provision component regarding that the determined hardware resource should allow transfer of sensitive information about the determined hardware resource and / or regarding details of information about the determined hardware resource that the determined hardware resource should allow transfer of.
[0016] Example 10 is the communication system of example 9, wherein the resource management component is configured to determine the hardware resources taking into account whether one or more network functions are stateful or stateless.
[0017] Example 11 is the communication system of any one of Examples 1 to 10, in which the hardware resources include at least one of a computation resource, a network resource, and a storage resource.
[0018] Example 12 is the communication system of any one of Examples 1 to 11, in which the hardware resource is a resource of a movable device.
[0019] Example 13 is the communication system of Example 12, wherein the movable device is a vehicle, and the hardware resources are configured to be switchable between providing functionality for driving the vehicle and providing network functions.
[0020] Example 14 is the communication system of example 12 or 13, wherein the resource information providing component is configured to receive resource availability information from the mobile device.
[0021] Example 15 is the communication system of any one of Examples 1 to 14, wherein the service is at least one of hotspot wireless access, a data streaming service, a user data plane gateway service, and a data caching service.
[0022] Example 16 is a communication system of any one of Examples 1 to 15, wherein the resource availability information includes, for at least some of the hardware resources, a guarantee that the hardware resources will be available at the indicated location or locations for the indicated time period or periods, and the resource management component is configured to determine the hardware resources for providing one or more network functions, taking into account whether the resource availability information includes a guarantee for the hardware resources.
[0023] Example 17 is a method for providing a service as described below with reference to FIG.
[0024] It should be noted that one or more of the features of any of the above embodiments may be combined with any of the other embodiments. In particular, the embodiments described in relation to a device are equally valid for a method.
[0025] According to a further embodiment, there is provided a computer program and a computer readable medium comprising instructions which, when executed by a computer, cause the computer to perform the method of any one of the above examples.
[0026] Various examples are described in more detail below.
[0027] FIG. 1 illustrates a communication system 100, and in particular a management framework for communication resources of the communication system.
[0028] The communication system 100 comprises communication system resources 101, 102, 103 that are managed by an infrastructure manager or resource manager 104. The hardware resources of the communication system include computational, storage, and / or network resources, for example in the form of compute servers, dedicated accelerators for specific tasks (e.g., provided in the cloud), specialized hardware such as programmable metasurfaces, etc.
[0029] The resources 101, 102, 103 are used (or "consumed") by resource consumers. In the example of FIG. 1, the service orchestrators (particularly acting as service provision components) 105, 106, e.g., tenants (i.e., communication providers) providing communication services, can be considered as resource consumers. Each service orchestrator is provided with (communication system) functionality (particularly, network functionality) by a respective resource orchestrator (particularly acting as resource management component) 107, which provides the functionality using the communication system resources allocated to the resource consumer. It should be noted that the tenants 105, 106 together with their resource orchestrators 107 (i.e., the resource orchestrators 107 that provide the functionality to it) can also be considered as resource consumers. Furthermore, alternatively, the resource orchestrator 107 may also be considered as a resource consumer (in the sense of using resources to provide the functionality, or in other words, allocating resources for the functionality provision).
[0030] So, for example, one or more resource orchestrators 107 manage resources 101, 102, 103 located, for example, in the same region or zone, where a resource orchestrator is responsible for a particular scope management, e.g., a domain, a certain application, a tenant, etc., and each resource 101, 102, 103 is associated (or may be unassigned) at a given point in time with one of the resource orchestrators 107 and tenants 105, 106.
[0031] According to various embodiments, the resources 101, 102, 103 include hardware resources provided by mobile (i.e. non-stationary) devices, in particular vehicles (although other mobile devices such as satellites may also be applicable).
[0032] Thus, various embodiments provide, among other things, reusability and resource sharing of commoditized vehicles with computing capabilities, e.g., vehicles-as-a-cloud service implementation that applies cloudification to the network edge. To that end, various embodiments provide a resource orchestrator (e.g., a Management and Orchestration (MANO)) that manages the network and the network. A cloud computing system (CIS) or its administrators (e.g., a telecommunications system operator) can leverage resources on a temporarily parked vehicle as if it were a cloud-enabled resource. The vehicle may be a personal vehicle or may belong to, for example, a rental car company's fleet.
[0033] FIG. 2 illustrates the use of a rental car company's vehicles 201 as a cloud of resources by MANO 202.
[0034] The vehicle is used by MANO 202, for example, when parked in a garage overnight and connected to access point 203.
[0035] FIG. 3 illustrates the use of individual owner's vehicles 301 as a cloud of resources by MANO 302 .
[0036] The vehicle can be used by MANO 302 wherever it is located by connecting it to base station 303.
[0037] Thus, according to various embodiments, it is assumed that there are a large number of vehicles capable of high performance computing, for example to achieve autonomous driving, and therefore have computational, storage, and / or communication (i.e., network) hardware resources that can be leveraged as resources (e.g., to build a cloud) when the vehicles are parked at a particular location (i.e., within a particular geographic area 204, 304) or moving in a flock (within a particular geographic area) under certain conditions.
[0038] Here, the concept of geographical regions may be flexible, such that rather than determining regions and zones in advance, computing clusters may be configured over time and (potentially) everywhere, i.e., the geographical grouping may be flexibly determined (e.g., by the respective resource orchestrator 107).
[0039] Of course, resources may dynamically join (i.e., become available) or leave (i.e., become unavailable). Thus, the resource orchestrator 107, when providing resources for a service, may have to take into account the requirements (e.g., amount of resources needed) and / or characteristics (e.g., stateless or stateful) of the application (e.g., network functionality) and determine in advance that some resources will be unavailable at a later point in time. For example, in the case of stateful applications, it is not feasible to deploy stateful applications, especially those resources that may become unavailable during the life of the deployed application.
[0040] Stateful means that a network function (or application) holds and has state information that is used to perform its functionality, e.g., an application that has in its database certain information that is used to route / forward packets, i.e., the routing / forwarding is determined by information that the application has, and not based solely on information received with the individual packets being forwarded. Thus, a "stateful" application means that the application has some kind of state and therefore cannot be easily moved to another resource. Thus, if an application is stateful and a communication service depends on it, the loss of the resource used to deploy the application will affect the availability of the application and, therefore, the availability of the communication service that the application is providing. Therefore, whether an application can be deployed on such a resource must also take into account the availability of the resource.
[0041] The resource orchestrator 107 may take into account placement constraints for the network function to meet the requirements of the service. For example, the resource orchestrator 107 may not deploy a network function using one or more vehicles when the network function needs to be provided (for a particular service) for a longer period of time than the resources of one or more vehicles might be expected to be available as resources at a particular location for the resource orchestrator 107 (which may be a larger area such as a block, a parking lot, etc.).
[0042] Since the resources are not owned by the administrator of the MANO 202, 302 in the above scenario, metadata and identifiers can be exchanged between the resource owner (i.e., the vehicle 201, 301) and the (administrator of) the MANO to realize negotiation of the use of the resources.
[0043] It should be noted that the service orchestrators 105, 106 and the resource orchestrator 107 may not have knowledge of certain information that should be sensitive, such as the exact location of the private vehicle 301 to ensure privacy.
[0044] For example, there is a mechanism to input geographic information about resources into a resource orchestrator (e.g., MANO), which may embed the resources as virtual resources according to, for example, NFVI (Network Functions Virtualization Infrastructure).
[0045] FIG. 4 illustrates time-varying resource management according to one embodiment.
[0046] The vehicle 401 provides one or more hardware resources. From an NFV (Network Function Virtualization) perspective, being provided by the vehicle 201 means that the resources may move, which means that the information used for application (including network function) placement may change over time.
[0047] To support the functionality of providing time-varying resource information and metadata, an entity 402, denoted as a time-varying resource information manager (which acts, among other things, as a resource information providing component), is provided for managing time-varying resource information.
[0048] A time-varying resource information manager 402 receives information about the resources provided by the vehicle 401, for example, via a database 403 or a message queue 408. This information is about the vehicle and its resources, such as availability (e.g., how long it will be parked in a particular location), its location, etc.
[0049] The time-varying resource information manager 402 provides this information to a resource orchestrator 404 (e.g., corresponding to the resource orchestrator 107 and / or MANO 202, 302), which may maintain a resource database 405 that holds information about available resources including metadata (e.g., identification information assigned to the vehicle 401).
[0050] The resources may be used to provide network functionality 406 to enable a service orchestrator 407 (eg, corresponding to one of the service orchestrators 105, 106) to provide communication services.
[0051] For example, the resource orchestrator 404 may provide a hotspot using the wireless communication capabilities of the vehicle 201 (i.e., the communication service is here a hotspot service). Another example is the use of the vehicle to cache or stream data, for example to provide users with faster access to data in the vicinity of the vehicle (i.e., the service may be the provision of a particular data). The resources provided by the vehicle may also be used for offloading for any kind of service to reduce the burden on other resources. Thus, the resources are used in particular to provide wireless or edge network functions whose proximity (and thus the placement of the network functions) to one or more other users is important to provide the respective communication service with a particular quality. The resources may also be used to provide core network functions (e.g., user plane functions for forwarding traffic from the wireless network at a particular location) whose placement may also benefit one or more other users due to proximity, coverage, or required bandwidth capabilities.
[0052] The resource orchestrator 404 uses information about resources to match requirements with the time-varying characteristics of the resources that are (to be) provided. The service orchestrator 407 sends application (particularly network function) requirements to the resource orchestrator 404, and the resource orchestrator 150 performs the matching and placement, i.e., finds resources that match the requirements and uses the matched resources to deploy the requested application (particularly network function). The time-varying resource information manager 402 provides the (time-varying) information needed for this to the resource orchestrator 404.
[0053] The (time-varying) information may for example include one or more of the following information elements: An indicator as to the level of information, e.g. whether the information can include GPS information about the vehicle's position every minute An indicator as to whether to commit (i.e., whether the vehicle (or its owner) commits to having the resource used, for example, for a certain indicated time). · (If committed) determined time-varying information (e.g. when the vehicle is moving away, e.g. when the vehicle passes a particular point, i.e. when it leaves a particular area).
[0054] Time-varying information related to the resources provided by the vehicle may be transmitted from the vehicle. As mentioned above, it is transmitted to the service orchestrator 407 (e.g., a tenant) via the resource orchestrator 404 (e.g., MANO or MANO administrator). However, its content may differ depending on the interface (i.e., whether it is transmitted via a service orchestrator-resource orchestrator interface or a vehicle-resource orchestrator interface). It should be noted that the information may also be transmitted to the resource orchestrator 404 via a device associated with the vehicle (such as the owner's mobile terminal), i.e., it does not necessarily have to be transmitted by the vehicle itself. The resource orchestrator 404 may take into account how much detailed information the vehicle owner can provide. For example, some service orchestrators may want to know detailed information about the movement of infrastructure components (i.e., vehicles) so that they can change the service operation depending on the location of the infrastructure elements. To do this, the resource orchestrator needs to select appropriate infrastructure elements (i.e., hardware resources) that allow the vehicle owner (of the selected infrastructure element) to allow the resource orchestrator 404 to reveal, for example, detailed information about the vehicle's movements or location, i.e., the determined hardware resources to transfer confidential information and / or information about them to the resource orchestrator 404 at a certain level of detail.
[0055] Table 1 shows examples of different levels of information that may be transferred. [Table 1]
[0056] Here, detailed information is, for example, the exact location of the vehicle (e.g., address), and abstract information is a higher level location. Sensitive information could be information such as license plate number, owner's name, etc.
[0057] Thus, information elements containing time-varying information, including current information (e.g., availability, location, with the level of detail depending on whether the information is abstracted or not), are transmitted over the interface. If the vehicle (or its owner) has not committed to the vehicle's resources being used, the information may include predictions for the near future (e.g., how long the vehicle is expected to be in a particular location), but there is no guarantee.
[0058] The resource orchestrator 404 performs masking of the information (ie, removing sensitive information) and abstracts the information (eg, converting an address into a larger region).
[0059] In summary, in accordance with various embodiments, a communication system is provided as shown in FIG.
[0060] FIG. 5 illustrates a communication system 500 according to one embodiment.
[0061] The communication system 500 comprises a resource information providing component 501 configured to provide resource availability information including information about one or more locations where a hardware resource is temporarily available and information about one or more time periods when the hardware resource is available at the locations.
[0062] The communication system 500 further comprises a service provision component 502 for providing a service (e.g., a communication service, but could also be a data processing service such as any kind of software application) configured to indicate requirements for one or more network functions for providing the service, the requirements including locations at which the one or more network functions should be provided and time periods at which the one or more network functions should be provided.
[0063] Furthermore, the communication system 500 comprises a resource management component 503 configured to determine hardware resources for providing the one or more network functions from among the hardware resources, and to start providing the one or more network functions using the determined hardware resources, such that the indicated requirements for the one or more network functions can be met by providing the one or more network functions using the determined hardware resources.
[0064] According to various embodiments, in other words, information about the temporal availability of hardware resources is taken into account for the service provision. This information may be considered as time-varying information or information about time-varying availability in the sense that a hardware resource may be available at a certain time and in a certain location, but may subsequently become unavailable or may be available in a different location (e.g. because the vehicle is moved to a different parking lot).
[0065] Thus, the approach of FIG. 5 considers data processing hardware resources whose availability at a particular location may change through time (because they are moving) and thus allows the data processing system to exploit data processing hardware resources (computational resources, network resources, storage resources) available from mobile infrastructure elements such as vehicles or other moving objects (e.g., satellites or wearable devices) having data processing hardware resources. Data processing resource hardware can dynamically join and leave a cloud-like data processing system (e.g., a communication system). The geographical area in which the data processing resources are used can be flexibly defined. For example, a location may be a parking lot, a square, another street, etc., depending on where the service provision component (or its operator) wants to provide a particular service. The resource management component determines (i.e., selects) a hardware resource (e.g., a vehicle) that can provide the service at that location for the required time.
[0066] Thus, according to various embodiments, the telecommunications operator orchestration mechanism is enhanced with methods, mechanisms, and interfaces that can enable data processing system resources on the vehicle (provided for functionality for operating the vehicle, e.g., driver assistance functions) to be leveraged as if they were part of a cloud service for, for example, a distributed data center.
[0067] The communication system 500 may, for example, implement a method such as that shown in FIG.
[0068] FIG. 6 shows a flow diagram 600 illustrating a method for providing a service.
[0069] At 601, resource availability information is received that includes information about one or more locations where a hardware resource is temporarily available and information about one or more time periods during which the hardware resource is available at the locations.
[0070] At 602, requirements for one or more network functions to provide a service are received, where the requirements include locations at which the one or more network functions are to be provided and time periods at which the one or more network functions are to be provided.
[0071] At 603, hardware resources for providing the one or more network functions are determined from among the hardware resources, such that the indicated requirements for the one or more network functions can be satisfied by providing the one or more network functions using the determined hardware resources, and providing of the one or more network functions is started using the determined hardware resources.
[0072] It should be noted that the above (especially 602, 603) do not have to be performed strictly in the order shown, but may be performed at least partially alternately, in parallel, or in the opposite order.
[0073] The components of the communication system may be implemented, for example, by one or more circuits. A "circuit" may be understood as any kind of logic implementation entity, which may be a dedicated circuit or a processor that executes software, firmware, or any combination thereof stored in a memory. Thus, a "circuit" may be a hardwired logic circuit or a programmable processor, e.g., a programmable logic circuit such as a microprocessor. A "circuit" may also be a processor that executes software, e.g., any kind of computer program. Any other kind of implementation of the respective functions described above may also be understood as a "circuit".
[0074] While particular embodiments have been described, it will be understood by those skilled in the art that various changes in form and details can be made therein without departing from the spirit and scope of the embodiments of the present disclosure as defined by the appended claims. The scope is therefore indicated by the appended claims, and all changes that come within the meaning and range of equivalents of the claims are therefore intended to be embraced.
Claims
1. 1. A communication system comprising: The present invention comprises a resource information providing component, a service providing component for providing a service, and a resource management component; the resource information providing component is configured to provide to the resource management component resource availability information including information about one or more locations where hardware resources of a movable device are temporarily available, the hardware resources being configured to be able to switch between providing functionality for controlling the movement of the movable device and providing network functionality, information about one or more time periods during which the hardware resources are available at the locations, and information about whether the movable devices permit use of the hardware resources they provide; the service provision component is configured to indicate requirements for one or more network functions for providing the service to the resource management component, the requirements including a location where the one or more network functions should be provided and a time period during which the one or more network functions should be provided; the resource management component is configured to determine, taking into account the provided resource availability information, hardware resources for providing the one or more network functions that can satisfy the indicated requirements for the one or more network functions by providing the one or more network functions using the determined hardware resources by matching the indicated requirements for the one or more network functions with characteristics of the hardware resources, and to start providing the one or more network functions using the determined hardware resources. Communication systems.
2. 10. The communication system of claim 1, wherein the one or more network functions include at least one of a core network function, an edge network function, and a radio network function.
3. 3. The communication system of claim 1 or 2, wherein the resource management component is configured to at least partially forward the resource availability information to the service provision component, and the service provision component is configured to determine requirements as the requirements that can be met by providing the one or more network functions using the hardware resources.
4. The communication system of claim 3 , wherein the resource management component is configured to remove sensitive information from the resource availability information and forward the remainder of the resource availability information to the service provision component.
5. The communication system of claim 3 , wherein the resource management component is configured to at least partially abstract the resource availability information and forward the abstracted resource availability information to the service provision component.
6. The communication system of claim 5 , wherein abstracting the resource availability information comprises reducing the precision of the information about the location.
7. The communication system of claim 3 , wherein the resource management component is configured to receive instructions from the service provision component regarding details of information to be transferred, and configured to transfer the resource availability information at least in part in accordance with the instructions.
8. 2. The communication system of claim 1, wherein the resource management component is configured to determine the hardware resource taking into account one or more requirements by the service provision component regarding which the determined hardware resource should allow transfer of sensitive information about the determined hardware resource and / or regarding details of the information about the determined hardware resource that the determined hardware resource should allow transfer of.
9. The communication system of claim 8 , wherein the resource management component is configured to determine the hardware resources taking into account whether the one or more network functions are stateful or stateless.
10. The communication system of claim 1 , wherein the hardware resources include at least one of a computational resource, a network resource, and a storage resource.
11. 2. The communication system of claim 1, wherein the resource availability information includes, for at least some of the hardware resources, a guarantee that the hardware resources will be available at the indicated one or more locations for the indicated one or more time periods, and the resource management component is configured to determine hardware resources for providing the one or more network functions taking into account whether the resource availability information includes a guarantee for a hardware resource.
12. 1. A method for providing a service, comprising: receiving resource availability information including information about one or more locations where hardware resources of a movable device are temporarily available, the hardware resources being configured to be able to switch between providing functionality for controlling movement of the movable device and providing network functionality, information about one or more time periods during which the hardware resources are available at the locations, and information about whether the movable devices permit use of the hardware resources they provide; receiving requirements for one or more network functions for providing said service, said requirements including a location at which said one or more network functions should be provided and a time period at which said one or more network functions should be provided; determining among the hardware resources for providing the one or more network functions, the hardware resources being capable of satisfying the indicated requirements for the one or more network functions by matching the indicated requirements for the one or more network functions with characteristics of the hardware resources, taking into account the provided resource availability information, by providing the one or more network functions using determined hardware resources; beginning to provide the one or more network functions using the determined hardware resources; The method includes:
Citation Information
Patent Citations
Methods, apparatus and articles of manufacture for workload placement in edge environment
JP2022054417A
A method of network service descriptor management in a network functions virtualisation
KR1020180123430A
Text line normalization systems and methods
US11062164B2
Vehicular cloud slicing
US20200313959A1
Method for customized, situation-aware orchestration of decentralized network resources
US20220029930A1
