Method and apparatus for resource availability check

Abstract

Systems, methods, apparatuses, and computer program products for resource availability checking.

Description

Technical Field

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or Fifth Generation (5G) radio access technology or New Radio (NR) access technology, or may relate to other communication systems. For example, certain embodiments may relate to systems and / or methods for resource availability checking. Background Art

[0002] Examples of mobile or wireless telecommunication systems may include Universal Mobile Telecommunication System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), Advanced LTE (LTE-A), MulteFire, LTE-A Pro, and / or Fifth Generation (5G) radio access technology or New Radio (NR) access technology. 5G wireless systems refer to the Next Generation (NG) radio systems and network architectures. 5G is mainly built on New Radio (NR), but 5G (or NG) networks can also be built on E-UTRA radio. It is estimated that NR can provide bitrates in the order of 10 - 20 Gbit / s or higher, and can support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine type communication (mMTC). NR is expected to provide ultra-wideband and ultra-robust low-latency connections and large-scale networks to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communication become more and more common, the need for networks that can meet the requirements of low power consumption, low data rate, and long battery life will continue to grow. Note that in 5G, a node that can provide radio access functions to user equipment (i.e., similar to Node B in UTRAN or eNB in LTE) can be named gNB when built on NR radio, and can be named NG-eNB when built on E-UTRA radio. Brief Description of the Drawings

[0003] For a proper understanding of the example embodiments, reference should be made to the drawings, in which:

[0004] Figure 1 An example of a request-response process between a customer-side entity and a network-side entity according to some embodiments is shown;

[0005] Figure 2 An example of processing a request for availability information according to some embodiments is shown;

[0006] Figure 3 An example operation of a projection unit according to some embodiments is shown;

[0007] Figure 4 An example operation of a policy unit according to some embodiments is shown;

[0008] Figure 5 Shows an example flowchart of a method according to some embodiments;

[0009] Figure 6 Shows an example flowchart of a method according to some embodiments;

[0010] Figure 7 Shows an example flowchart of a method according to some embodiments;

[0011] Figure 8a Shows an example block diagram of an apparatus according to one embodiment; and

[0012] Figure 8b Shows an example block diagram of an apparatus according to another embodiment. Detailed Description

[0013] It will be readily understood that the components of certain example embodiments, generally described and illustrated in the figures herein, can be arranged and designed in a variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for resource availability checking is not intended to limit the scope of certain embodiments, but rather represents selected example embodiments.

[0014] The features, structures, or characteristics of the example embodiments described throughout this specification can be combined in any suitable manner in one or more example embodiments. For example, the use of the phrases "certain embodiments", "some embodiments", or other similar language throughout this specification refers to a particular feature, structure, or characteristic described in connection with one embodiment that can be included in at least one embodiment. Thus, the appearances of the phrases "in certain embodiments", "in some embodiments", "in other embodiments", or other similar language throughout this specification are not necessarily all referring to the same set of embodiments, and the described features, structures, or characteristics can be combined in any suitable manner in one or more example embodiments.

[0015] Furthermore, if desired, the different functions or processes discussed below can be performed in a different order and / or simultaneously with each other. Additionally, if desired, one or more of the described functions or processes can be optional or can be combined. Accordingly, the following description should be regarded as illustrative only of the principles and teachings of certain example embodiments and not as limiting thereof.

[0016] For a network service request, a service customer may only be able to request an immediate service instantiation or check the feasibility of such service instantiation at the actual time of the request. A potential problem with a standardized feasibility check solution is that a positive result of such a check may not guarantee a successful service instantiation, even if the service instantiation is requested immediately after receiving a positive (e.g., feasible) result. This may be because the resources available during the feasibility check are no longer available (e.g., the resources may have been allocated to another service or may have been consumed by concurrent requests).

[0017] Resource reservation (where resources immediately become occupied and are no longer available for allocation to other services or for use by other consumers) can address the previously described problem. However, such resource reservation may have various possible consequences. For example, resource reservation may have a negative impact on resource utilization and may result in resource utilization being below optimal (e.g., resources may be idle or unused and may not be available for allocation to other services). In a commercial interaction (e.g., when the resources belong to a commercial computing cloud), a consumer may pay for resources reserved in its name but never used. This may result in significant costs for the customer and may make business planning and the implementation of business strategies difficult. From the perspective of the service provider, without flexibility in resource allocation (e.g., at a specific date and / or time, to estimate the resource availability at a given future time, and / or etc.), the service provider may not be able to adequately plan the use of network resources.

[0018] Some embodiments described herein may provide resource availability checks. For example, some embodiments may allow a network entity to determine the probability of network resource availability at a future predefined time (e.g., a timed feasibility check) and / or evaluate the feasibility of providing a set of resources at that future predefined time. For example, a network entity may determine the feasibility of providing a network slice subnet instance (NSSI) at a specific future time. The network entity may determine the feasibility based on current or predicted load information, current or predicted resource usage information, etc. This can improve the operation of the network by increasing the resource utilization of network resources, which can reduce wasted or idle network resources. In addition, this can facilitate improved planning and / or deployment of network resources. In addition, this can save costs related to business operations by reducing or eliminating the reservation of resources that are not used at the reserved time.

[0019] Figure 1 An example of a request-response process between a customer-side entity and a network-side entity according to some embodiments is shown. Figure 1shows a user - side network entity 100 (e.g., a network service customer entity such as a user equipment (UE)) and a network - side entity 102 (e.g., a network service provider entity such as a function involved in network function virtualization management and orchestration (NFV MANO), communication service management function (CSMF), network slice management function (NSMF), network slice subnet management function (NSSMF), etc.). Although Figure 1 the user - side network entity 100 and the network - side entity 102 are shown, certain embodiments described herein are equally applicable to interactions between two or more user - side entities or two or more network - side entities. Additionally, while some embodiments relate to interactions between network service consumer (NSC) entities and network service provider / producer (NSP) entities, some embodiments are equally applicable to interactions between communication service consumer (CSC) entities and communication service provider / producer (CSP) entities or other types of entities.

[0020] As shown at 104, the user - side entity 100 may provide and the network - side entity 102 may receive a request for availability information. For example, the availability information may be related to the availability of one or more resources of a network associated with the network - side entity 102. In some embodiments, the resources may include sub - nets, network functions, computing resources, memory resources, network resources (e.g., bandwidth), etc. The resources may include virtualized resources such as virtualized network functions, virtual computing resources, virtual memory resources, virtual network resources, etc. The resources may be associated with a particular network entity. For example, a resource may be provided by a particular network entity, and the availability information may identify the availability of the resource for that particular entity (e.g., the availability may be determined on a per - resource - per - entity basis).

[0021] In some embodiments, after receiving a request, the network-side entity 102 may determine the probability of the availability of one or more resources at a future time and / or during a certain time period. For example, the network-side entity 102 may determine this probability based on information related to the current or predicted load of one or more resources, the current or predicted resource usage of one or more resources, etc. In some embodiments, in order to perform a prediction on the availability of one or more resources, the network-side entity 102 may utilize the cross-correlation with other known, planned, or predicted events (e.g., at the time and / or location of a sports event or concert, the resource and / or network utilization increases), may make the prediction based on an approximation of the observed usage trends (including periodic patterns), may utilize statistical methods that report predicted values and / or confidence scores, and so on. For example, the prediction may be based on data related to a specific location, regional population, demographics, the number of visitors to a certain location at a specific time or during a certain time period, etc. Additionally or alternatively, for some resources, the prediction may be based on data related to context features, such as weather, the utilization of neighboring resources, etc. The use of one or more of these prediction techniques may improve the accuracy of the prediction, thereby improving resource allocation and / or utilization.

[0022] In some embodiments, the probability may be related to a geographical location or region (e.g., the probability of availability at a geographical location or region), a Network Function Virtualization Infrastructure Point of Presence (NFVIPoP) (e.g., a server or data center), etc. Additionally or alternatively, the probability may be associated with an entity for network management integration (e.g., for performance, fault, planning, and / or analysis operations).

[0023] In some embodiments, the network-side entity 102 may determine a preferred future time or a preferred future time period for the availability of one or more resources based on this probability. For example, the network-side entity 102 may determine that the time or time period with the highest relative probability of availability (e.g., the highest probability relative to other times or time periods) is the preferred time or the preferred time period. In some embodiments, the highest relative probability may be for a specific geographical location or region, for a specific NFVIPoP, etc. For example, based on the highest relative probability being associated with different times or time periods, different geographical locations or different NFVIPoPs may be associated with different preferred times or preferred time periods. In some embodiments, the highest relative probability may be for a specific customer-related entity, such as a customer, a network tenant, a communication service using the network, etc. The selection of the preferred future time or time period may improve resource allocation and / or utilization by directing requests for resources to the time or time period when the resources are likely to be available.

[0024] In some embodiments, the network - side entity 102 may determine whether the network infrastructure can provide resources of the requested type. For example, the network - side entity 102 may determine whether the network infrastructure is configured with the specific type of resources requested. Additionally or alternatively, the network - side entity 102 may determine whether the network infrastructure can provide one or more resources in the requested quantity. For example, the network - side entity 102 may determine whether the network infrastructure can provide one or more resources in the requested quantity by performing calculations and / or analyses on quantization information related to the quantity of resources provided by the network infrastructure. Additionally or alternatively, the network - side entity 102 may determine whether one or more resources can be provided with a specific quality (e.g., with a specific quality of service). Performing these types of checks saves the processing resources of the network - side entity 102 in performing predictions, determining preferred times or time periods, etc., because these operations may depend on the network infrastructure passing these checks.

[0025] In some embodiments, the network - side entity 102 may utilize availability information to determine and / or provide a confidence value associated with the result of determining whether the network infrastructure can provide the requested quantity of network resources (e.g., the confidence value may indicate the confidence in determining the capabilities of the network infrastructure). Additionally or alternatively, the network - side entity 102 may provide a risk value associated with the result of determining whether the network infrastructure can provide the requested quantity of network resources. For example, the risk value may indicate the risk that one or more resources will be unavailable during a future time or future time period.

[0026] As shown at 106, the network - side entity 102 may provide availability information, and the user - side entity 100 may receive the availability information. The availability information may identify the probability of availability during a future time or future time period, a preferred future time or preferred future time period (e.g., determined based on the highest relative probability), etc. In addition, the network - side entity 102 may provide an indication of whether the requested resources can be provided.

[0027] As described above, providing Figure 1 As an example. According to some embodiments, other examples are possible.

[0028] Figure 2 An example of processing a request for availability information according to some embodiments is shown. Figure 2 Shown is Figure 1 One or more example processing units of the network - side entity 102. For example, one or more processing units may include a request analysis unit 200, a projection unit 202, a policy unit 204, and a decision - making unit 206.

[0029] As shown in 208, the network-side entity 102 may receive a request for availability information at the request analysis unit 200 (e.g., from the user-side entity 100). For example, the NSC entity may request availability information related to a specific resource in a manner similar to that described elsewhere in this document. The network-side entity 102 may analyze the request and may identify one or more aspects and / or attributes of the request (e.g., may identify the amount of resources, the type of resources, etc.). For example, the request analysis unit 200 may analyze the request. In some embodiments, the request may be provided using an intent-based approach (e.g., an unstructured or partially structured approach for making the request), an application programming interface (API)-based approach, a template-based approach, etc. This may provide flexibility to the network-side entity 102 in terms of the way the request is provided.

[0030] As shown in 210, the request analysis unit 200 may provide information related to the request to the projection unit 202. The projection unit 202 may project the identified request onto the network and network elements to determine whether the request can be satisfied. The projection unit 202 may deliver a satisfactory response (e.g., to indicate that the request can be satisfied) or a response regarding the request not being satisfied (e.g., a resource issue has been identified). In the case where the request can be satisfied, as shown in 212-1, the projection unit 202 may provide the response to the decision-making unit 206, where the request may be further evaluated.

[0031] In the case where the request cannot be satisfied based on the identification of insufficient resources, as shown in 212-2, the projection unit 202 may provide the response to the policy unit 204 so that the network-side entity 102 can apply one or more policies to reduce or eliminate the problem. This may provide a way for the network-side entity 102 to overcome problems that would otherwise prevent resource allocation and / or impede resource utilization. To this end, the policy unit 204 may evaluate, analyze, and / or assess a given event and / or hazard. The goal of the assessment may be to determine whether the request is likely to be satisfied and what the consequences of some assumptions and hazards may be. When the policy unit 204 has completed the assessment of possible assumed actions, possible solutions may be delivered to the decision-making unit 206, as shown in 214.

[0032] Based on the delivered solutions that may be marked with weights, the decision-making unit 206 may deliver a response that may take into account additional network knowledge. The decision-making unit 206 may include an expert system that works with a database to improve decision-making.

[0033] Some in the database can also be used by the other units described above. The database can include, for example, a knowledge database (e.g., which includes information related to facts about the network or general knowledge, such as network topology, network capabilities, or network capacity, and the information includes information related to spatio - temporal relationships (e.g., for events, such as fluctuating channel conditions at different locations and / or times), etc.). Additionally or alternatively, the database can include a network scenario memory database (e.g., including information related to network state patterns), an association database (e.g., having some proven facts, such as the network path from entity A through entity C to entity B always performs well, router X is error - prone, network failures may occur if there are more than X connections, etc.), an experience database (e.g., including information related to network experiences), a historical database (e.g., including information related to network history), etc.

[0034] In one embodiment, aspects of the projection unit 202 and / or the policy unit 204 can be implemented as a simulator based on the generated network model and the actual network topology and capabilities. Additionally, the simulator can be based on a neural network having learning capabilities (e.g., the ability to learn to predict resource availability based on data related to historical resource availability). This can improve predictions related to resource availability.

[0035] As described above, provide Figure 2 As an example. According to some embodiments, other examples are possible.

[0036] Figure 3 An example operation of the projection unit according to some embodiments is shown. Figure 3 The request analysis unit 200, the projection unit 202, the policy unit 204, and the decision - making unit 206 are shown.

[0037] As shown at 300, the request analyzer 200 may provide the result of analyzing the request for availability information to the projection unit 202, as described elsewhere herein. At 302, the projection unit 202 may perform request distribution to perform various analysis operations based on information requested from one or more network entities associated with the requested resource. For example, at 304, the projection unit 202 may perform a preliminary analysis, which may be a network-centric analysis (e.g., an overall analysis of various aspects of the network). Additionally or alternatively, and as another example, at 306, the projection unit 202 may perform an analysis of the requested effects without failures, which may be a network element-centric analysis (e.g., the availability of network elements (such as network nodes or network functions) under normal circumstances). Additionally or alternatively, at 308, the projection unit 202 may perform an analysis of the requested effects with failure rates, which may be a network element-centric analysis (e.g., analyzing the results of network elements if a failure occurs in a network element or another node associated with the network element, in which case, replacements, maintenance times, etc. of network nodes may have to be considered).

[0038] As shown at 310, the projection unit 202 may compile the results of various analysis operations and may perform an evaluation of whether the type and / or quantity of the requested resource can be provided by the network infrastructure, the probability of the availability of one or more resources at a future time or future time period, a preferred future time or preferred time period, whether the request can be satisfied, etc. As shown at 312, the projection unit 202 may determine whether there are sufficient resources available (e.g., whether the request can be satisfied, as described elsewhere herein). If resources are available (312 - Yes), then at 314, the projection unit 202 may provide a response indicating whether the resources are available to the decision-making unit 206. If resources are not available (312 - No), then at 316, the projection unit 202 may provide a response indicating that the resources are not available (e.g., a problem with the request for resources has been identified). The decision-making unit 206 and the policy unit 204 may perform operations similar to those described elsewhere herein.

[0039] As described above, provide Figure 3 as an example. According to some embodiments, other examples are possible.

[0040] Figure 4 An example operation of the policy unit according to some embodiments is shown. Figure 4 The request analysis unit 200, the policy unit 204, and the decision-making unit 206 are shown.

[0041] As shown at 400, the request analysis unit 400 may provide a response to the policy unit 204, as described elsewhere herein (e.g., to indicate that a problem with a request for a resource has been identified). As shown at 402, the policy unit 204 may perform event / hazard assumptions, as described elsewhere herein. As shown at 404, the policy unit 204 may perform an evaluation of the event / hazard assumptions. As shown at 406, the policy unit 406 may perform a sensitivity analysis of the evaluation (e.g., by adjusting the amount of the requested resource, the future time or future time period for providing the resource, etc.).

[0042] As shown at 408, the policy unit 204 may perform an evaluation of the sensitivity analysis. As shown at 410, the policy unit 204 may determine whether a problem (e.g., the resource request cannot be satisfied) has been resolved. If the problem has not been resolved (410 - No), then at 412, the policy unit 204 may determine whether to perform additional assumptions / hazards. If the policy unit 204 determines that no additional assumptions / hazards are to be performed, then at 414, the policy unit 204 may provide information indicating that the problem has not been resolved to the decision-making unit 206. If the policy unit 204 determines to perform additional assumptions / hazards (412 - Yes), then at 418, the policy unit 204 may return to operation 402. If the problem has been resolved (410 - Yes), then at 416, the policy unit 204 may provide information indicating that the request can be satisfied to the decision unit 206.

[0043] As described above, provided Figure 4 as an example. According to some embodiments, other examples are possible.

[0044] Figure 5 An example flow chart of a method according to some embodiments is shown. For example, Figure 5 an example operation of a network-side entity (e.g., a device 10 similar to or belonging to Figure 8a and / or a user-side entity (e.g., a device 20 similar to or belonging to Figure 8b is shown. Figure 5 Some of the operations shown in Figures 1 to 4 may be similar to Figures 1 to 4 some of the operations shown and described with respect to

[0045] In one embodiment, the method may include: at 500, providing at least one request for availability information related to the availability of at least one resource of at least one network. For example, a user-side entity may provide the at least one request to a network-side entity, as described elsewhere herein. In one embodiment, the method may include: at 502, receiving the availability information. For example, a user-side entity may receive the availability information from a network-side entity. The availability information may identify at least one of the following: at least one probability of the availability of at least one resource at at least one future time or during at least one future time period, and at least one preferred future time or at least one preferred future time period based on the at least one probability.

[0046] In some embodiments, the network entity may include at least one user-side entity. In some embodiments, the network entity may include at least one network-side entity. In some embodiments, at least one resource may be associated with at least one specific network entity. In some embodiments, at least one probability of availability may be associated with at least one of the following: at least one geographical location or region, or at least one network function virtualization infrastructure (NFVI) point of presence (PoP). In some embodiments, at least one probability of availability may be associated with at least one entity for network management integration.

[0047] In some embodiments, at least one preferred time or at least one preferred time period may be associated with the highest relative probability of the availability of at least one time or at least one time period. In some embodiments, at least one preferred time or at least one preferred time period is associated with the highest relative probability of the availability of at least one of the following: at least one geographical location or region, or at least one network function virtualization infrastructure (NFVI) point of presence (PoP). In some embodiments, at least one preferred time or at least one preferred time period may be associated with the highest relative probability of the availability of at least one customer-related entity. In some embodiments, at least one resource may include at least one virtual resource.

[0048] As described above, provide Figure 5 As an example. According to some embodiments, other examples are possible.

[0049] Figure 6 An example flowchart of a method according to some embodiments described herein is shown. For example, Figure 6 An example operation of a network-side entity (e.g., similar to or belonging to Figure 8a device 10) is shown. Figure 6 Some of the operations shown may be similar to Figures 1 to 4 those shown and regarding Figures 1 to 4 described some operations.

[0050] In one embodiment, the method may include: at 600, receiving at least one request for availability information related to the availability of at least one resource of at least one network. For example, a network-side entity may receive the at least one request from a user-side entity. In one embodiment, the method may include: at 602, determining at least one probability of the availability of at least one resource at at least one future time or during at least one future time period. For example, a network-side entity may determine the at least one probability.

[0051] In one embodiment, the method may include: at 604, determining at least one preferred future time or at least one preferred future time period of the availability of at least one resource based on at least one probability. For example, a network-side entity may determine at least one preferred future time or at least one preferred future time period. In one embodiment, the method may include: at 606, providing the availability information. For example, a network-side entity may provide the availability information to a user-side entity. The availability information may at least identify: at least one probability of the availability of at least one resource at at least one future time or during at least one future time period, and at least one preferred future time or at least one preferred future time period.

[0052] In some embodiments, at least one resource may be associated with at least one specific network entity. In some embodiments, at least one specific network entity may include at least one subnet, at least one network function, at least one computing resource, at least one memory resource, or at least one network resource. In some embodiments, at least one probability of availability may be associated with at least one of the following: at least one geographical location or region, or at least one network function virtualization infrastructure (NFVI) point of presence (PoP). In some embodiments, at least one probability of availability may be associated with at least one entity for network management integration.

[0053] In some embodiments, at least one preferred time or at least one preferred time period may be associated with the highest relative probability of availability of at least one time or at least one time period. In some embodiments, at least one preferred time or at least one preferred time period may be associated with the highest relative probability of availability of at least one of the following: at least one geographical location or region, or at least one network function virtualization infrastructure (NFVI) point of presence (PoP). In some embodiments, at least one preferred time or at least one preferred time period may be associated with the highest relative probability of availability of at least one customer-related entity. In some embodiments, at least one resource may include at least one virtual resource.

[0054] In some embodiments, the method may further include determining whether the network infrastructure can provide resources of one or more request types. In some embodiments, the method may further include performing at least one calculation or at least one analysis on whether the network infrastructure can provide resources of one or more requested amounts. In some embodiments, the method may further include providing at least one confidence value that identifies at least one result of performing at least one calculation or at least one analysis. In some embodiments, the method may further include determining at least one risk value of the availability of at least one resource. In some embodiments, the network entity may include at least one network-side entity.

[0055] As described above, provide Figure 6 As an example. According to some embodiments, other examples are possible.

[0056] Figure 7 An example flowchart of a method according to some embodiments described herein is shown. For example, Figure 7 An example operation of a network-side entity (e.g., similar to or belonging to Figure 8a device 10) is shown. Figure 7 Some of the operations shown may be similar to Figures 1 to 4 those shown and regarding Figures 1 to 4 described some operations.

[0057] In one embodiment, the method may include: at 700, receiving a request for availability information related to the availability of at least one resource of at least one network. For example, the network-side entity may receive a request for availability information from a user-side entity. In one embodiment, the method may include: at 702, causing to provide at least one response including the availability information. For example, the network-side entity may cause to provide at least one response including the availability information to the user-side entity. The availability information may identify at least one of the following: at least one probability of the availability of at least one resource at at least one future time or during at least one future time period, and at least one preferred future time or at least one preferred future time period.

[0058] As described above, provide Figure 7 As an example. According to some embodiments, other examples are possible.

[0059] Figure 8aShows an example of the device 10 according to one embodiment. In some embodiments, the device 10 may include a network side entity as described elsewhere herein. In some embodiments, the device 10 may include a node, host, or server in a communication network or serving such a network. For example, the device 10 may include a network node associated with a radio access network (such as an LTE network, 5G or NR), a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB), and / or a WLAN access point.

[0060] It should be understood that in some example embodiments, the device 10 may include an edge cloud server as a distributed computing system, where the server and the radio node may be independent devices communicating with each other via a wireless circuit path or via a wired connection, or they may be in the same entity communicating via a wired connection. For example, in some example embodiments where the device 10 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functions. In such an architecture, the CU may be a logical node including gNB functions (such as transmission of user data, mobility control, radio access network sharing, positioning, and / or session management, etc.). The CU may control the operation of the DU through a fronthaul interface. The DU may be a logical node including a subset of the gNB functions, depending on the function split option. It should be noted that those of ordinary skill in the art will understand that the device 10 may include Figure 8a components or features not shown.

[0061] As Figure 8a shown in the example of, the device 10 may include a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general or special purpose processor. In fact, for example, the processor 12 may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 8a a single processor 12 is shown, multiple processors may be used according to other embodiments. For example, it should be understood that in certain embodiments, the device 10 may include two or more processors, which may form a multi-processor system that can support multi-processing (for example, in this case, the processor 12 may represent a multi-processor). In certain embodiments, the multi-processor system may be tightly coupled or loosely coupled (for example, to form a computer cluster).

[0062] Processor 12 may perform functions associated with the operation of device 10, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of device 10, including processes related to management of communication resources.

[0063] Device 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12 and is for storing information and instructions executable by processor 12. Memory 14 may be one or more memories and of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology (such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory). For example, memory 14 may include random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic or optical disks, hard disk drive (HDD), or any other type of non-transitory memory or computer-readable medium. Instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable device 10 to perform the tasks described herein.

[0064] In one embodiment, device 10 may also include or be coupled to (internal or external) a drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, USB drive, flash drive, or any other storage medium. For example, the external computer-readable storage medium may store computer programs or software for execution by processor 12 and / or device 10.

[0065] In some embodiments, device 10 may also include or be coupled to one or more antennas 15 for transmitting signals and / or data to and receiving signals and / or data from device 10. Device 10 may also include or be coupled to a transceiver 18 configured to transmit and receive information. Transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to antenna 15. The radio interfaces may correspond to multiple radio access technologies, including one or more of the following: GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identification (RFID), ultra-wideband (UWB), MulteFire, etc. The radio interfaces may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, etc., to generate symbols for transmission via one or more downlinks and (e.g., via the uplink) receive symbols.

[0066] Accordingly, the transceiver 18 can be configured to modulate information onto a carrier waveform for transmission by the antenna 15 and demodulate information received via the antenna 15 for further processing by other elements of the device 10. In other embodiments, the transceiver 18 can be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, the device 10 can include input and / or output devices (I / O devices).

[0067] In one embodiment, the memory 14 can store software modules that provide functionality when executed by the processor 12. The module can include, for example, an operating system that provides operating system functionality for the device 10. The memory can also store one or more functional modules, such as applications or programs, to provide additional functionality for the device 10. The components of the device 10 can be implemented in hardware or as any suitable combination of hardware and software.

[0068] According to some embodiments, the processor 12 and the memory 14 can be included in or can form part of a processing circuitry or a control circuitry. Additionally, in some embodiments, the transceiver 18 can be included in or can form part of a transceiver circuitry.

[0069] As used herein, the term "circuitry" can refer to only hardware circuit implementations (e.g., analog and / or digital circuitry), combinations of hardware circuits and software, combinations of analog and / or digital hardware circuits and software / firmware, any portion of a hardware processor (including a digital signal processor) working with software to cause a device (e.g., the device 10) to perform various functions, and / or hardware circuits and / or processors or portions thereof that operate using software but for which the software may not be present when not needed for operation. As a further example, as used herein, the term "circuitry" can also cover implementations that include only a hardware circuit or a processor (or processors), or a portion of a hardware circuit or a processor, and its accompanying software and / or firmware. The term circuitry can also cover, for example, a baseband integrated circuit in a server, a cellular network node or device, or other computing or network device.

[0070] As described above, in certain embodiments, the device 10 can be a network node or a RAN node, such as a base station, an access point, a Node B, an eNB, a gNB, a WLAN access point, etc.

[0071] According to certain embodiments, the device 10 can be controlled by the memory 14 and the processor 12 to perform functions associated with any of the embodiments described herein, such as Figures 1 to 7 some operations.

[0072] For example, in one embodiment, the apparatus 10 may be controlled by the memory 14 and the processor 12 to receive at least one request for availability information related to the availability of at least one resource of at least one network. In one embodiment, the apparatus 10 may be controlled by the memory 14 and the processor 12 to determine at least one probability of the availability of at least one resource at at least one future time or during at least one future time period. In one embodiment, the device 10 may be controlled by the memory 14 and the processor 12 to determine at least one preferred future time or at least one preferred future time period for the availability of at least one resource based on at least one probability. In one embodiment, the apparatus 10 may be controlled by the memory 14 and the processor 12 to provide availability information, where the availability information at least identifies: at least one probability of the availability of at least one resource at at least one future time or during at least one future time period, and at least one preferred future time or at least one preferred future time period.

[0073] In another embodiment, the apparatus 10 may be controlled by the memory 14 and the processor 12 to provide at least one request for availability information related to the availability of at least one resource of at least one network. In one embodiment, the apparatus 10 may be controlled by the memory 14 and the processor 12 to receive availability information. The availability information may identify at least one of the following: at least one probability of the availability of at least one resource at at least one future time or during at least one future time period, and at least one preferred future time or at least one preferred future time period based on at least one probability.

[0074] In one embodiment, the apparatus 10 may be controlled by the memory 14 and the processor 12 to receive a request for availability information related to the availability of at least one resource of at least one network. In one embodiment, the apparatus 10 may be controlled by the memory 14 and the processor 12 to cause the provision of at least one response including availability information. The availability information may identify at least one of the following: at least one probability of the availability of at least one resource at at least one future time or during at least one future time period, and at least one preferred future time or at least one preferred future time period.

[0075] Figure 8bShows an example of the apparatus 20 according to another embodiment. In some embodiments, the apparatus 20 may include a user side entity as described elsewhere herein. In some embodiments, the apparatus 20 may include a node, host, or server in a communication network or a node, host, or server serving such a network, similar to the apparatus 10 described above. For example, the apparatus 20 may include a network node, satellite, base station, Node B, evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), and / or WLAN access point associated with a radio access network such as an LTE network, 5G, or NR. In some embodiments, the apparatus 20 may include a node or element in a communication network or a node or element associated with such a network, such as a UE, mobile device (ME), mobile station, mobile equipment, fixed device, IoT device, or other device. As described herein, a UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user equipment, subscriber station, wireless terminal, tablet, smartphone, IoT device, sensor, or NB-IoT device, etc. As an example, the apparatus 20 may be implemented in, for example, a wireless handheld device, a wireless plug-in accessory, etc.

[0076] In some example embodiments, the apparatus 20 may include one or more processors, one or more computer-readable storage media (e.g., memories, storage devices, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or a user interface. In some embodiments, the apparatus 20 may be configured to operate using one or more radio access technologies such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology. It should be noted that those of ordinary skill in the art will understand that the apparatus 20 may include Figure 8b components or features not shown therein.

[0077] As Figure 8b shown in the example of, the apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general-purpose or special-purpose processor. In fact, the processor 22 may include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 8bA single processor 22 is shown, but in accordance with other embodiments, multiple processors may be used. For example, it should be understood that in certain embodiments, the apparatus 20 may include two or more processors, which may form a multiprocessor system that can support multiprocessing (e.g., in such a case, the processor 22 may represent a multiprocessor). In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0078] The processor 22 may perform functions associated with the operation of the apparatus 20, and as some examples, include precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of the apparatus 20, including processes related to the management of communication resources.

[0079] The apparatus 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22, and the memory 24 is for storing information and instructions that may be executed by the processor 22. The memory 24 may be one or more memories and have any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology (such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory). For example, the memory 24 may include random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic disks or optical discs, hard disk drives (HDDs), or any other type of non-transitory memory or computer-readable medium. The instructions stored in the memory 24 may include program instructions or computer program code, which when executed by the processor 22 enable the apparatus 20 to perform the tasks described herein.

[0080] In one embodiment, the apparatus 20 may also include or be coupled to (internal or external) a drive or port configured to accept and read an external computer-readable storage medium, such as an optical disc, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store computer programs or software for execution by the processor 22 and / or the apparatus 20.

[0081] In some embodiments, device 20 may further include or be coupled to one or more antennas 25 for receiving downlink signals and for transmitting from device 20 via the uplink. Device 20 may also include a transceiver 28 configured to transmit and receive information. Transceiver 28 may also include a radio interface (e.g., a modem) coupled to antenna 25. The radio interface may correspond to a variety of radio access technologies, including GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc. to process symbols carried by the downlink or uplink, such as OFDMA symbols.

[0082] For example, transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by antenna 25 and to demodulate information received via antenna 25 for further processing by other elements of device 20. In other embodiments, transceiver 28 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, device 20 may include input and / or output devices (I / O devices). In certain embodiments, device 20 may further include a user interface, such as a graphical user interface or a touch screen.

[0083] In one embodiment, memory 24 stores software modules that provide functionality when executed by processor 22. The module may include, for example, an operating system that provides operating system functionality for device 20. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality for device 20. The components of device 20 may be implemented in hardware or as any suitable combination of hardware and software. According to an example embodiment, device 20 may optionally be configured to communicate with device 10 via a wireless or wired communication link 70 according to any radio access technology such as NR.

[0084] According to some embodiments, processor 22 and memory 24 may be included in or may form part of a processing circuitry or a control circuitry. Additionally, in some embodiments, transceiver 28 may be included in or may form part of a transceiver circuitry.

[0085] As described above, according to some embodiments, for example, the apparatus 20 may include a network node, a satellite, a base station, a Node B, an eNB, a 5G Node B or an access point, an NG-NB or a gNB, a LAN access point, a UE, a mobile device, a mobile station, an ME, an IoT device, and / or an NB-IoT device. According to certain embodiments, the apparatus 20 may be controlled by the memory 24 and the processor 22 to perform functions associated with the example embodiments described herein. For example, in some embodiments, the apparatus 20 may be configured to perform one or more of the processes depicted or described in any of Figures 1 to 7 therein.

[0086] For example, in one embodiment, the apparatus 20 may be controlled by the memory 24 and the processor 22 to provide at least one request for availability information related to the availability of at least one resource of at least one network. In one embodiment, the apparatus 20 may be controlled by the memory 24 and the processor 22 to receive availability information, where the availability information identifies at least one of the following: at least one probability of the availability of at least one resource at at least one future time or during at least one future time period, and at least one preferred future time or at least one preferred future time period based on at least one probability.

[0087] Thus, certain example embodiments provide several technical improvements, enhancements, and / or advantages over prior art processes. For example, one benefit of some example embodiments is the reduction of reserved but unused resources provided by the network. Additionally, another example benefit is the improvement in resource utilization optimization. Therefore, the use of some example embodiments improves the functionality of communication networks and their nodes, and thus constitutes at least an improvement in the technical fields such as network resource allocation, utilization, and / or optimization.

[0088] In some example embodiments, the functionality of any method, process, signaling diagram, algorithm, or flowchart described herein may be implemented by software and / or computer program code or code portions stored in a memory or other computer-readable or tangible medium and executed by a processor.

[0089] In some example embodiments, a device may be included in or associated with at least one software application, module, unit, or entity configured for arithmetic operations, or configured as a program or a portion thereof (including added or updated software routines) to be executed by at least one operating processor. The program (also referred to as a program product or a computer program, including software routines, applets, and macros) may be stored in any device-readable data storage medium and may include program instructions for performing specific tasks.

[0090] A computer program product may include one or more computer-executable components that, when the program runs, are configured to perform some example embodiments. The one or more computer-executable components may be at least one software code or code portion. Modifications and configurations required to implement the functions of the example embodiments may be performed as routines, which may be implemented as added or updated software routines. In one example, the software routines may be downloaded to the device.

[0091] As an example, the software or computer program code or code portion may be in source code form, object code form, or some intermediate form, and it may be stored in some carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. For example, such a carrier may include a recording medium, computer memory, read-only memory, electro-optical and / or electrical carrier signals, telecommunication signals, and / or software distribution packages. Depending on the required processing power, the computer program may be executed in a single electronic digital computer or distributed among multiple computers. The computer-readable medium or computer-readable storage medium may be a non-transitory medium.

[0092] In other example embodiments, the functions may be performed by hardware or circuitry included in a device (e.g., device 10 or device 20), such as by using an application-specific integrated circuit (ASIC), programmable gate array (PGA), field-programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functions may be implemented as a signal, such as an intangible device carried by an electromagnetic signal downloaded from the Internet or other network.

[0093] According to example embodiments, devices such as nodes, devices, or corresponding components may be configured as circuitry, a computer, or a microprocessor, such as a single-chip computer element, or may be configured as a chipset, which may include at least a memory for providing storage capacity for arithmetic operations and / or an arithmetic processor for performing arithmetic operations.

[0094] The example embodiments described herein apply equally to singular and plural implementations, regardless of whether singular or plural language is used in describing certain embodiments. For example, an embodiment describing the operation of a single network entity applies equally to an embodiment including multiple instances of the network entity, and vice versa.

[0095] Those of ordinary skill in the art will readily understand that the example embodiments discussed above may be practiced with processes in a different order and / or with hardware elements configured differently than those disclosed. Accordingly, while some embodiments have been described based on these example embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative configurations will be apparent while still remaining within the scope of the example embodiments.

[0096] According to a first embodiment, a method may include receiving at least one request for availability information related to the availability of at least one resource of at least one network. The method may include determining at least one probability of the availability of the at least one resource at at least one future time or during at least one future time period. The method may include determining at least one preferred future time or at least one preferred future time period of the availability of the at least one resource based on the at least one probability. The method may include providing the availability information. The availability information at least identifies: at least one probability of the availability of the at least one resource at at least one future time or during at least one future time period, and at least one preferred future time or at least one preferred future time period.

[0097] In a variation, the at least one resource may be associated with at least one specific network entity. In a variation, the at least one specific network entity may include at least one subnet, at least one network function, at least one computing resource, at least one memory resource, or at least one network resource. In a variation, the at least one probability of availability may be associated with at least one of the following: at least one geographical location or region, or at least one network function virtualization infrastructure (NFVI) point of presence (PoP).

[0098] In a variation, the at least one probability of availability may be associated with at least one entity for network management integration. In a variation, the at least one preferred time or at least one preferred time period may be associated with the highest relative probability of availability of at least one time or at least one time period. In a variation, the at least one preferred time or at least one preferred time period may be associated with the highest relative probability of availability of at least one of the following: at least one geographical location or region, or at least one network function virtualization infrastructure (NFVI) point of presence (PoP).

[0099] In a variant, at least one preferred time or at least one preferred time period may be associated with the highest relative probability of the availability of at least one customer-related entity. In a variant, at least one resource may include at least one virtual resource. In a variant, the method may include determining whether the network infrastructure is capable of providing resources of one or more request types. In a variant, the method may include performing at least one calculation or at least one analysis on whether the network infrastructure is capable of providing resources of one or more requested amounts. In a variant, the method may include providing at least one confidence value that identifies at least one result of performing at least one calculation or at least one analysis. In a variant, the method may include determining at least one risk value of the availability of at least one resource. In a variant, the network entity includes at least one network-side entity.

[0100] According to a second embodiment, a method may include providing at least one request for availability information related to the availability of at least one resource of at least one network. The method may include receiving the availability information by a network entity. The availability information identifies at least one of the following: at least one probability of the availability of at least one resource during at least one future time or at least one future time period, and at least one preferred future time or at least one preferred future time period based on at least one probability. In a variant, the network entity may include at least one user-side entity. In a variant, the network entity includes at least one network-side entity.

[0101] According to a third embodiment, a method may include receiving a request for availability information related to the availability of at least one resource of at least one network. The method may include causing the provision of at least one response including the availability information. The availability information may identify at least one of the following: at least one probability of the availability of at least one resource during at least one future time or at least one future time period, and at least one preferred future time or at least one preferred future time period.

[0102] A fourth embodiment may be directed to an apparatus that includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, together with the at least one processor, cause the apparatus to at least perform the methods according to the first embodiment, the second embodiment, or the third embodiment, or any variant, discussed above.

[0103] A fifth embodiment may be directed to an apparatus that may include circuitry configured to perform the methods according to the first embodiment, the second embodiment, or the third embodiment, or any variant, discussed above.

[0104] The sixth embodiment may be directed to an apparatus that may include components for performing the method according to the first embodiment, the second embodiment, or the third embodiment discussed above, or any variations thereof.

[0105] The seventh embodiment may be directed to a computer-readable medium having program instructions stored thereon for at least performing the method according to the first embodiment, the second embodiment, or the third embodiment discussed above, or any variations thereof.

[0106] The eighth embodiment may be directed to a computer program product encoding instructions for at least performing the method according to the first embodiment, the second embodiment, or the third embodiment discussed above, or any variations thereof.

Claims

1. A method for communication, the method comprises: receiving (600), by a network entity, at least one request for availability information related to the availability of at least one resource of at least one network; determining (602), by the network entity, at least one probability of the availability of the at least one resource at at least one future time or during at least one future time period; determining (604), by the network entity, based on the at least one probability, at least one first future time or at least one second future time period of the availability of the at least one resource, wherein the at least one first future time is at least one time with the highest probability of availability relative to other times, and the at least one second future time period is at least one time period with the highest probability of availability relative to other time periods; and providing (606), by the network entity, the availability information, wherein the availability information at least identifies the at least one first future time or the at least one second future time period, wherein the at least one resource comprises at least one of the following: a subnet, a network function, a computing resource, a memory resource, and a virtual resource.

2. The method according to claim 1, wherein the at least one resource is associated with at least one specific network entity.

3. The method according to any one of claims 1 to 2, wherein the at least one probability of the availability is associated with at least one of the following: at least one geographical location or region, or at least one network function virtualization infrastructure (NFVI) point of presence (PoP).

4. The method according to claim 1 or 2, wherein the at least one probability of the availability is associated with at least one entity for network management integration.

5. The method according to claim 1 or 2, wherein the at least one first future time is associated with the highest relative probability of the availability for the at least one time, or the at least one second future time period is associated with the highest relative probability of the availability for the at least one time period.

6. The method according to claim 1 or 2, wherein the at least one first future time or the at least one second future time period is associated with the highest relative probability of the availability for at least one of the following: at least one geographical location or region, or at least one network function virtualization infrastructure (NFVI) point of presence (PoP).

7. The method according to claim 1 or 2, wherein the at least one first future time or the at least one second future time period is associated with the highest relative probability of the availability for at least one customer-related entity.

8. The method according to claim 1 or 2, further comprises: determining whether the network infrastructure can provide one or more resources of the requested type; and performing at least one calculation or at least one analysis on whether the network infrastructure can provide one or more amounts of resources.

9. The method according to claim 8, further comprises: Provide at least one confidence value, where the at least one confidence value identifies at least one result of performing the at least one calculation or the at least one analysis.

10. The method according to claim 1 or 2, further comprising: Determine at least one risk value of the availability of the at least one resource.

11. The method according to claim 1 or 2, wherein the network entity comprises at least one network-side entity.

12. The method according to claim 1 or 2, further comprising: The network entity provides (606) the availability information, where the availability information at least identifies at least one probability of the availability of the at least one resource during the at least one future time or during the at least one future time period.

13. A method for communication, the method comprising: The network entity provides (500) at least one request for availability information related to the availability of at least one resource of at least one network; and The network entity receives (502) the availability information, where the availability information at least identifies: Based on at least one probability of the availability of the at least one resource during at least one future time or during at least one future time period, at least one first future time or at least one second future time period, where The at least one resource comprises at least one of the following: subnet, network function, computing resource, memory resource, and virtual resource; The at least one first future time is at least one time when the probability of availability is the highest relative to other times; and The at least one second future time period is at least one time period when the probability of availability is the highest relative to other time periods.

14. The method according to claim 13, wherein the network entity comprises at least one user-side entity.

15. The method according to claim 13, wherein the network entity comprises at least one network-side entity.

16. A device for communication, the device comprising: At least one processor (12); and At least one memory (14), including computer program code, where the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to at least: Receive (600) at least one request for availability information related to the availability of at least one resource of at least one network; Determine (602) at least one probability of the availability of the at least one resource during at least one future time or during at least one future time period; and Based on the at least one probability, determine (604) at least one first future time or at least one second future time period of the availability of the at least one resource, and provide (606) the availability information, where the availability information at least identifies the at least one first future time or the at least one second future time period, where The at least one resource comprises at least one of the following: subnet, network function, computing resource, memory resource, and virtual resource; The at least one first future time is at least one time at which the probability of availability is highest relative to other times; and The at least one second future time period is at least one time period at which the probability of availability is highest relative to other time periods.

17. A device for communication, the device comprising: means for receiving at least one request for availability information related to the availability of at least one resource of at least one network; means for determining at least one probability of the availability of the at least one resource during at least one future time or during at least one future time period; means for determining, based on the probability, at least one first future time or at least one second future time period of the availability of the at least one resource, wherein the at least one first future time is at least one time at which the probability of availability is highest relative to other times, and the at least one second future time period is at least one time period at which the probability of availability is highest relative to other time periods; and means for providing the availability information, wherein the availability information at least identifies the at least one first future time or the at least one second future time period, wherein the at least one resource includes at least one of the following: a subnet, a network function, a computing resource, a memory resource, and a virtual resource.

18. A non-transitory computer-readable medium comprising program instructions for causing a device to at least perform the following operations: Receive (600) at least one request for availability information related to the availability of at least one resource of at least one network; Determine (602) at least one probability of the availability of the at least one resource during at least one future time or during at least one future time period; Determine (604), based on the at least one probability, at least one first future time or at least one second future time period of the availability of the at least one resource; and Provide the availability information, wherein the availability information at least identifies the at least one first future time or the at least one second future time period, wherein the at least one resource includes at least one of the following: a subnet, a network function, a computing resource, a memory resource, and a virtual resource; the at least one first future time is at least one time at which the probability of availability is highest relative to other times; and the at least one second future time period is at least one time period at which the probability of availability is highest relative to other time periods.

19. A device for communication, the device comprising: at least one processor (22); and at least one memory (24), including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to at least: Provide (500) at least one request for availability information related to the availability of at least one resource of at least one network; and Receive (502) the availability information, wherein the availability information identifies: At least one first future time or at least one second future time period based on the at least one probability of the availability of the at least one resource at at least one future time or during at least one future time period, wherein The at least one resource includes at least one of the following: a subnet, a network function, a computing resource, a memory resource, and a virtual resource; The at least one first future time is at least one time when the probability of availability is highest relative to other times; And The at least one second future time period is at least one time period when the probability of availability is highest relative to other time periods.

20. A device for communication, the device Comprises: Components for providing at least one request for availability information related to the availability of at least one resource of at least one network; And Components for receiving the availability information, wherein the availability information identifies At least one first future time or at least one second future time period based on the at least one probability of the availability of the at least one resource at at least one future time or during at least one future time period, wherein The at least one resource includes at least one of the following: a subnet, a network function, a computing resource, a memory resource, and a virtual resource; The at least one first future time is at least one time when the probability of availability is highest relative to other times; And The at least one second future time period is at least one time period when the probability of availability is highest relative to other time periods.

21. A non-transitory computer-readable medium, comprising program instructions for causing a device to at least perform the following operations: Provide (500) at least one request for availability information related to the availability of at least one resource of at least one network; and Receive (502) the availability information, wherein the availability information identifies At least one first future time or at least one second future time period based on the at least one probability of the availability of the at least one resource at at least one future time or during at least one future time period, wherein The at least one resource includes at least one of the following: a subnet, a network function, a computing resource, a memory resource, and a virtual resource; The at least one first future time is at least one time when the probability of availability is highest relative to other times; and The at least one second future time period is at least one time period when the probability of availability is highest relative to other time periods.

Images