Resource Balancing

Abstract

An apparatus is disclosed. The apparatus includes components for performing the following operations: in response to determining that resources in a communication network are insufficient or about to be insufficient, determining whether an agreed-upon service level of one or more service requirements of one or more services will be affected; and when it is determined that the agreed-upon service level of the one or more service requirements of the one or more services will be affected, determining whether one or more customers can tolerate non-compliance with the agreed-upon service level.

Description

Technical Field

[0001] The present disclosure relates to communications, and more particularly to resource balancing in wireless communication systems. Background Art

[0002] A communication system may be viewed as a facility for enabling communication between two or more devices (such as user terminals, machine-type terminals, base stations and / or other nodes) by providing a communication channel for carrying information between the communication devices. For example, a communication system may be provided by means of a communication network and one or more compatible communication devices. Communications may include, for example, data communications for carrying data for voice, electronic mail (email), text messaging, multimedia and / or content data communications, etc. Non-limiting examples of the services provided include two-way or multi-way calls, data communications or multimedia services, and access to data network systems such as the Internet.

[0003] In a wireless system, at least part of the communication occurs over a wireless interface. Examples of wireless systems include public land mobile networks (PLMNs), satellite-based communication systems, and different wireless local area networks, such as wireless local area networks (WLANs). Local area network wireless network technology that allows devices to connect to data networks is called WiFi (or Wi-Fi). WiFi is often used synonymously with WLAN. Wireless systems can be divided into cells and are therefore often referred to as cellular systems. A base station provides at least one cell.

[0004] A user can access a communication system by means of an appropriate communication device or terminal capable of communicating with a base station. Therefore, nodes such as base stations are often referred to as access points. The communication device of a user is often referred to as a user equipment (UE). The communication device is provided with appropriate signal receiving and transmission means for achieving communication, for example, achieving communication with a base station and / or directly with other user equipment. The communication device can communicate on an appropriate channel, for example, a channel on which a listening station (e.g., a base station of a cell) transmits.

[0005] Communication systems and related equipment typically operate according to a given standard or specification that specifies what the various entities associated with the system are allowed to do and how it should be implemented. Communication protocols and / or parameters that should be used for connections are also typically defined. Non-limiting examples of standardized radio access technologies include GSM (Global System for Mobile), EDGE (Enhanced Data for GSM Evolution) Radio Access Network (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and Evolved UTRAN (E-UTRAN). An example communication system architecture is the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology. LTE is standardized by the Third Generation Partnership Project (3GPP). LTE adopts Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access and its further development (sometimes referred to as Advanced LTE (LTE-A)).

[0006] Since the launch of fourth generation (4G) services, there has been a growing interest in the next generation or fifth generation (5G) standard. 5G can also be referred to as New Radio (NR) networks. The standardization of 5G or New Radio networks has been completed in 3GPP Release 15.

[0007] In some networks (such as 5G networks), the network may include one or more network slices. Summary of the invention

[0008] According to a first aspect, a device is provided, comprising components for: determining whether an agreed-upon service level for one or more service requirements of one or more services will be affected in response to determining that a resource shortage or an impending resource shortage is occurring in a communication network; and determining whether one or more customers can tolerate non-compliance with the agreed-upon service level when it is determined that the agreed-upon service level for one or more service requirements of the one or more services will be affected.

[0009] According to one example, the component is further configured to enforce allowing non-compliance with the agreed-upon service level for those customers who can tolerate non-compliance.

[0010] According to one example, the component is further configured to perform prevention of non-compliance with the agreed-upon service level for those customers who cannot tolerate non-compliance.

[0011] According to one example, the component is further configured to perform a lookup of a tolerance indicator of the one or more customers when determining whether the one or more customers can tolerate non-compliance with the agreed-upon service level.

[0012] According to an example, the tolerance indicator is associated with one or more of the one or more service requirements of the one or more services.

[0013] According to one example, the tolerance indicator indicates at least one or more of: a tolerance range for an agreed service level; a tolerance duration for non-compliance with the agreed service level; and compensation for accepting non-compliance with the agreed service level.

[0014] According to an example, the one or more service requirements include at least one or more of: data rate; packet loss; coverage; user mobility; service availability; reliability.

[0015] According to one example, a communication network includes at least one or more of the following: a network slice; a network slice subnet; a network service; a network function; a network function service.

[0016] According to one example, the apparatus comprises an entity of a network service provider.

[0017] According to one example, the component includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause execution of the apparatus.

[0018] According to a second aspect, a device is provided, comprising at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code being configured to, together with the at least one processor, cause the device to at least perform: in response to determining that there is a resource shortage or an impending resource shortage in a communication network, determining whether an agreed service level of one or more service requirements of one or more services will be affected; and when it is determined that the agreed service level of one or more service requirements of one or more services will be affected, determining whether one or more customers can tolerate non-compliance with the agreed service level.

[0019] According to an example, at least one memory and computer program code are configured to, with at least one processor, cause the apparatus to at least perform: allowing non-compliance with an agreed-upon service level for those customers who can tolerate non-compliance.

[0020] According to an example, at least one memory and computer program code are configured to, with at least one processor, cause the apparatus to at least perform: preventing non-compliance with an agreed-upon service level for those customers that cannot tolerate non-compliance.

[0021] According to one example, at least one memory and computer program code are configured to, with at least one processor, cause the apparatus to at least perform: when determining whether one or more customers can tolerate non-compliance with an agreed-upon service level, looking up tolerance indicators for one or more customers.

[0022] According to an example, the tolerance indicator is associated with one or more of the one or more service requirements of the one or more services.

[0023] According to one example, the tolerance indicator indicates at least one or more of: a tolerance range for an agreed service level; a tolerance duration for non-compliance with the agreed service level; and compensation for accepting non-compliance with the agreed service level.

[0024] According to an example, the one or more service requirements include one or more of: data rate; packet loss; coverage; user mobility; service availability; reliability.

[0025] According to one example, a communication network includes at least one or more of the following: a network slice; a network slice subnet; a network service; a network function; a network function service.

[0026] According to one example, the apparatus comprises an entity of a network service provider.

[0027] According to a third aspect, a device is provided, which includes: a determination circuit system for determining whether an agreed-upon service level of one or more service requirements of one or more services will be affected in response to determining that there is a resource shortage or an impending resource shortage in a communication network; and a determination circuit system for determining whether one or more customers can tolerate non-compliance with the agreed-upon service level when it is determined that the agreed-upon service level of one or more service requirements of the one or more services will be affected.

[0028] According to a fourth aspect, a method is provided, comprising: in response to determining that there is a resource shortage or an imminent resource shortage in a communication network, determining whether an agreed service level of one or more service requirements of one or more services will be affected; and when it is determined that the agreed service level of one or more service requirements of one or more services will be affected, determining whether one or more customers can tolerate non-compliance with the agreed service level.

[0029] According to one example, the method includes allowing non-compliance with an agreed-upon service level for those customers who can tolerate non-compliance.

[0030] According to one example, the method includes preventing non-compliance with an agreed-upon service level for those customers who cannot tolerate non-compliance.

[0031] According to one example, the method includes looking up a tolerance indicator for one or more customers when determining whether one or more customers can tolerate non-compliance with an agreed-upon service level.

[0032] According to an example, the tolerance indicator is associated with one or more of the one or more service requirements of the one or more services.

[0033] According to one example, the tolerance indicator indicates at least one or more of: a tolerance range for an agreed service level; a tolerance duration for non-compliance with the agreed service level; and compensation for accepting non-compliance with the agreed service level.

[0034] According to an example, the one or more service requirements include at least one or more of: data rate; packet loss; coverage; user mobility; service availability; reliability.

[0035] According to one example, a communication network includes at least one or more of the following: a network slice; a network slice subnet; a network service; a network function; a network function service.

[0036] According to an example, the method is performed by an entity of a network service provider.

[0037] According to a fifth aspect, a computer program is provided, comprising instructions for causing a device to perform at least the following operations: in response to determining that there is a resource shortage or an imminent resource shortage in a communication network, determining whether an agreed-upon service level of one or more service requirements of one or more services will be affected; and when it is determined that the agreed-upon service level of one or more service requirements of one or more services will be affected, determining whether one or more customers can tolerate non-compliance with the agreed-upon service level.

[0038] According to a sixth aspect, a computer program is provided, comprising instructions stored thereon, the instructions being used to perform at least the following operations: in response to determining that there is a resource shortage or an imminent resource shortage in a communication network, determining whether an agreed-upon service level for one or more service requirements of one or more services will be affected; and when it is determined that the agreed-upon service level for one or more service requirements of one or more services will be affected, determining whether one or more customers can tolerate non-compliance with the agreed-upon service level.

[0039] According to a seventh aspect, a non-transitory computer-readable medium is provided, which includes program instructions for causing a device to perform at least the following operations: in response to determining that there is a resource shortage or an imminent resource shortage in a communication network, determining whether an agreed-upon service level of one or more service requirements of one or more services will be affected; and when it is determined that the agreed-upon service level of one or more service requirements of one or more services will be affected, determining whether one or more customers can tolerate non-compliance with the agreed-upon service level.

[0040] According to an eighth aspect, a non-volatile computer-readable medium is provided, which includes program instructions stored thereon, and the program instructions are used to perform at least the following operations: in response to determining that there is a shortage of resources or an impending shortage of resources in a communication network, determine whether an agreed service level of one or more service requirements of one or more services will be affected; and when it is determined that the agreed service level of one or more service requirements of one or more services will be affected, determine whether one or more customers can tolerate non-compliance with the agreed service level.

[0041] According to a ninth aspect, a device is provided, comprising components for performing the following operations: receiving a network slice instance allocation or modification request from a consumer of the network slice instance; determining whether the allocation or modification is feasible; and sending information to the consumer, the information comprising a proposal for tolerance for the consumer's non-compliance with an agreed service level.

[0042] According to an example, the component is further configured to perform receiving an approval or disapproval of the proposed tolerance for non-compliance from the consumer.

[0043] According to one example, the component is also configured to perform allocation or update of network slice instances.

[0044] According to one example, the component includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause execution of the apparatus.

[0045] According to the tenth aspect, a device is provided, which includes at least one processor; and at least one memory including computer program code; 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 perform: receiving a network slice instance allocation or modification request from a consumer of the network slice instance; determining whether the allocation or modification is feasible; and sending information to the consumer, the information including a proposal for tolerance of the consumer's non-compliance with an agreed service level.

[0046] According to an example, at least one memory and computer program code are configured to, with at least one processor, cause the apparatus to at least perform: receiving from a consumer an approval or disapproval of a proposed tolerance for non-compliance.

[0047] According to one example, at least one memory and computer program code are configured to, together with at least one processor, cause the apparatus to at least perform: allocating or updating a network slice instance.

[0048] According to an eleventh aspect, a device is provided, comprising: a receiving circuit system for receiving a network slice instance allocation or modification request from a consumer of the network slice instance; a determining circuit system for determining whether the allocation or modification is feasible; and a sending circuit system for sending information to the consumer, the information comprising a proposal for tolerance of the consumer's non-compliance with an agreed service level.

[0049] According to a twelfth aspect, a method is provided, comprising: receiving a network slice instance allocation or modification request from a consumer of the network slice instance; determining whether the allocation or modification is feasible; and sending information to the consumer, the information comprising a proposal for tolerance for the consumer's non-compliance with an agreed service level.

[0050] According to one example, the method includes receiving, from a consumer, an approval or a disapproval of a proposed tolerance for non-compliance.

[0051] According to one example, the method includes allocating or updating a network slice instance.

[0052] According to a thirteenth aspect, a computer program is provided, comprising instructions for causing a device to perform at least the following operations: receiving a network slice instance allocation or modification request from a consumer of the network slice instance; determining whether the allocation or modification is feasible; and sending information to the consumer, the information comprising a proposal for tolerance for the consumer's non-compliance with an agreed service level.

[0053] According to a fourteenth aspect, a computer program is provided, comprising instructions stored thereon for performing at least the following operations: receiving a network slice instance allocation or modification request from a consumer of the network slice instance; determining whether the allocation or modification is feasible; and sending information to the consumer, the information comprising a proposal for tolerance for the consumer's non-compliance with an agreed service level.

[0054] According to a fifteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing an apparatus to perform at least the following operations: receive a network slice instance allocation or modification request from a consumer of the network slice instance; determine whether the allocation or modification is feasible; and send information to the consumer, the information comprising a proposal for tolerance of the consumer's non-compliance with an agreed-upon service level.

[0055] According to a sixteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions stored thereon, the program instructions being used to perform at least the following operations: receiving a network slice instance allocation or modification request from a consumer of the network slice instance; determining whether the allocation or modification is feasible; and sending information to the consumer, the information comprising a proposal for tolerance of the consumer's non-compliance with an agreed service level.

[0056] According to the seventeenth aspect, a device is provided, comprising components for performing the following operations: sending a network slice instance allocation or modification request to a provider of the network slice instance; receiving a proposal for tolerance of the device for non-compliance with an agreed service level; and sending an approval or disapproval of the proposed tolerance for non-compliance to the provider.

[0057] According to one example, the apparatus includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause execution of the apparatus.

[0058] According to the eighteenth aspect, a device is provided, which includes at least one processor; and at least one memory including computer program code; 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 perform: sending a network slice instance allocation or modification request to a provider of the network slice instance; receiving a proposal for tolerance of the device's non-compliance with an agreed service level; and sending an approval or disapproval of the proposed tolerance for non-compliance to the provider.

[0059] According to the nineteenth aspect, a device is provided, comprising: a sending circuit system for sending a network slice instance allocation or modification request to a provider of the network slice instance; a receiving circuit system for receiving a proposal for tolerance of the device's non-compliance with an agreed service level; and a sending circuit system for sending an approval or disapproval of the proposed tolerance for non-compliance to the provider.

[0060] According to the twentieth aspect, a method is provided, comprising: sending a network slice instance allocation or modification request to a provider of the network slice instance; receiving a proposal for tolerance of the device's non-compliance with an agreed service level; and sending an approval or disapproval of the proposed tolerance for non-compliance to the provider.

[0061] According to the twenty-first aspect, a computer program is provided, comprising instructions for causing a device to perform at least the following operations: sending a network slice instance allocation or modification request to a provider of the network slice instance; receiving a proposal for tolerance of the device's non-compliance with an agreed service level; and sending an approval or disapproval of the proposed tolerance for non-compliance to the provider.

[0062] According to the twenty-second aspect, a computer program is provided, comprising instructions stored thereon, for performing at least the following operations: sending a network slice instance allocation or modification request to a provider of the network slice instance; receiving a proposal for tolerance of the device's non-compliance with an agreed service level; and sending an approval or disapproval of the proposed tolerance for non-compliance to the provider.

[0063] According to the twenty-third aspect, a non-transitory computer-readable medium is provided, which includes program instructions for causing a device to perform at least the following operations: sending a network slice instance allocation or modification request to a provider of the network slice instance; receiving a proposal for tolerance of the device's non-compliance with an agreed service level; and sending an approval or disapproval of the proposed tolerance for non-compliance to the provider.

[0064] According to the twenty-fourth aspect, a non-transitory computer-readable medium is provided, comprising program instructions stored thereon, the program instructions being used to perform at least the following operations: sending a network slice instance allocation or modification request to a provider of the network slice instance; receiving a proposal for tolerance of the device's non-compliance with an agreed-upon service level; and sending an approval or disapproval of the proposed tolerance for non-compliance to the provider. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 The principle of network slicing is schematically shown;

[0066] Figure 2 is a flow chart of a method according to an example;

[0067] Figure 3 is a signaling diagram schematically illustrating an exemplary process for slice modification;

[0068] Figure 4 An example of a communication device is schematically shown;

[0069] Figure 5 An example of a control device is schematically shown;

[0070] Figure 6 is a flow chart schematically illustrating a method according to an example;

[0071] Figure 7 is a flow chart schematically illustrating a method according to an example;

[0072] Figure 8 is a flow chart schematically illustrating a method according to an example. DETAILED DESCRIPTION

[0073] The network can be divided into network "slices". For example, 3GPP Release 15 (Rel-15) describes network slicing for mobile 5G networks. Network slicing can be used for applications in the Internet Protocol (IP) Multimedia Subsystem (IMS).

[0074] Each network slice of the network can be considered as a virtualized independent logical network on the same physical network infrastructure of the network. Each network slice can include an isolated end-to-end network that is suitable for meeting the requirements requested by a specific application.

[0075] exist Figure 1 In the exemplary scenario shown, the network 105 may include three slices: slice a 103a; slice b 103b; and slice c 103c. It should be understood that in other examples, the network may include fewer or more network slices.

[0076] Figure 1 Each network slice 103a, 103b and 103c may be used for different applications. For example, slice a 103a may be used by user equipment (UE) 101a to comply with 3GPP eMBB (extended mobile broadband communication), slice b 103b may be used by UE 101b for Internet of Things (IoT) communication, and slice c 103c may be used by UE 101c to comply with 3GPP URLLC (ultra-reliable low latency communication). Another exemplary application in which network slicing may be used may be, for example, machine-to-machine communication. These applications are listed for example purposes only to help understand network slicing and are non-limiting.

[0077] In communication networks, contracts between service providers (e.g., mobile network operators (MNOs)) and service customers (i.e., customers of the MNOs, which may be, for example, end users) are described with the help of service level agreements (SLAs). Therefore, in some examples, a "customer" may be considered a "user" of a service. It will also be understood that the term "customer" may refer to a customer's device. For example, in a discussion of a customer's service level being affected, this may also be considered to mean that the service level of the device (e.g., UE, base station, etc.) is affected. A customer may also be referred to as a consumer. An important component of an SLA is the service level. The service level describes the agreed quality of service (QoS) and contains information about service characteristics or service requirements. Service requirements may include one or more of the following: latency; data rate; packet loss; coverage; user mobility; service availability; reliability; etc. "Service requirements" may also be referred to as "attributes" of a service.

[0078] Standardization bodies such as GSMA and 3GPP deal with SLA requirements to support network slicing.

[0079] 3GPP defines a network slice as a logical network that can span multiple parts of a wider network and provide specific network capabilities and network characteristics. Network slices must support agreed SLAs.

[0080] Currently, the Generic Network Slice Template (GST) defined by the GSMA is a set of attributes that can characterize a network slice. The GST is generic and has nothing to do with any specific network deployment. However, a GST filled with values, called a Network Slice Type (NEST), can be used to create a network slice instance.

[0081] The service profile of the network slice is also defined in the 3GPP Network Resource Model (NRM) of 3GPP TS 28.541. TS 28.541 represents the service requirements for the network slice instance. The service profile is mapped from NEST and is used to derive the resource requirements to support the service requirements of the network slice.

[0082] The service provider is responsible for controlling whether the service requirements on the relevant slices for a given customer are met.

[0083] In existing GST, NEST and service profiles, attributes (or service requirements) are defined to reflect the service requirements of the network slice. Figure 1 , the network slice management function (NSMF) 105 or the network slice subnet management function (NSSMF) 107 allocates resources to try to meet each service requirement equally.

[0084] However, in practice, there may be conflicts between two or more service requirements. Such conflicts may block network slice allocation / updates, or trigger unnecessary resource reconfiguration. This may lead to unexpected results for network slice consumers and violation of service level agreements (SLAs). This may also lead to instability in the operator's network. Therefore, under changing network conditions and limited network resources, it may be difficult to plan how many resources are required to complete all service agreements. Insufficient resources can lead to conflicts and deadlocks during system operation. From a business perspective, resource expansion is uneconomical and wasteful. In addition, data transmission may be affected by a variety of factors on the radio interface and in the transport network. For example, network equipment may drop data packets for several reasons. For example, link capacity may be congested, data in the wireless environment may be corrupted, latency may increase over time, or "jitter" (differences in packet arrival times) may become too high.

[0085] In situations where more resources are needed or requested than are available, it may be difficult or impossible to guarantee the promised quality of service to every customer.

[0086] It is determined in the present disclosure that in order to provide the best possible quality of service, it is necessary to know how to best handle service to a large number of customers when the network is affected by, for example, bottlenecks.

[0087] Therefore, the present disclosure introduces an indicator of individual service attributes. This indicator may be referred to as a tolerance indicator (TI). The TI of individual service attributes allows optimizing resource handling, especially in emergency network situations.

[0088] According to one example, the attributes (or service requirements) include SLA attributes (or service requirements). That is, the TI may indicate a tolerance for a level or standard of a particular attribute. In other words, the TI may provide an indication of the relative importance of the SLA attributes. That is, the TI may indicate which SLA attributes the customer is prepared to accept as not being met (i.e., not reaching the desired level) and which SLA attributes the customer requires to be met (i.e., must meet the desired level).

[0089] In the example, the TI is assigned to the service requirement related attributes in the service profile defined in 3GPP TS 28.541. This will be propagated to the service requirement related attributes in the slice profile defined in 3GPP TS 28.541, and the resulting related resource requirements.

[0090] The TI of a particular SLA attribute defines the customer's stated or specified tolerance for SLA violations. In other words, the TI defines the importance of adhering to a particular SLA attribute in an emergency network situation where network resources are limited. In some examples, the TI can define the duration of a tolerated violation.

[0091] In an example, TI helps improve resource allocation or reallocation in network emergency situations. TI can help avoid unnecessary network reconfiguration, which may have a higher risk of violating another SLA.

[0092] Knowing the importance of a particular SLA attribute may allow an exact or more accurate estimate of the consequences of a violation, and may therefore allow a less critical reconfiguration to be estimated, or allow a process to be moved in time to avoid a reconfiguration.

[0093] TI resolves network bottlenecks in situations where network failures lead to contract violations and resource allocation / reallocation.

[0094] Having TI associated with service attributes can avoid premature decisions and / or premature actions. Reconfiguration processes to address emergency situations can be costly, they are always speculative, and therefore they do not always bring the expected effect. Reconfiguration can also have the unintended consequence of violating other SLAs.

[0095] In congested situations where network conditions deteriorate, network service providers (NSPs) have greater decision flexibility in how to use TI to handle customer data. For example, data traffic can be increased for one service, while another service may be slowed down due to increased latency. TI thus moves NSP decisions from speculation to understanding.

[0096] Therefore, TI increases the freedom of NSPs to choose how to handle traffic data during congestion. TI provides NSPs with the possibility of greater decision flexibility and allows avoiding network reconfiguration processes that are inherently risky and subject to many uncertainties.

[0097] Understanding real customer needs may lead to optimized instantiation, configuration, reconfiguration, and scaling of slices.

[0098] In the example, TI may define any one or more of the following:

[0099] 1. The tolerance range of the attribute, i.e., the extent to which the attribute is allowed to deviate from the agreed service level (e.g., value)

[0100] 2. The tolerance duration for the attribute not to meet the SLA

[0101] 3. Conditions / compensation for tolerance. This could be compensation to the customer, for example.

[0102] In some examples, the negotiation of a TI for a particular SLA may be combined with a discount on the customer's service price, and penalties against the service provider may thus also be avoided.

[0103] In some examples, TI may be incorporated into the common attributes of the service requirement related attributes, as shown in Tables 1 and 2 below, where M=Mandatory; O=Optional, T=True, and F=False.

[0104]

[0105] Table 1

[0106] Table 1 shows the individual service attributes, i.e., SLA attributes, that are added to each service requirement attribute. Thus, as shown in Table 1, the following information is stored for each attribute: Category; Tag; Expose; AppliedNSSTypeList; ToleranceIndicator. In some practical examples (as shown in Table 1), all attributes are required, except for the optional TI (as shown in the Support Qualifier column "O" - Optional). In Table 1, "Writable" means that both the consumer and the provider can update the attribute. "Unchanged" means that the attribute value is set at object creation time and cannot be changed under specified conditions. "Notifiable" identifies whether a notification should be sent if the value changes.

[0107]

[0108] Table 2

[0109] Therefore, as shown in Table 2, when determining the customer's tolerance, the following aspects of the attributes may be considered: tolerance range (i.e., the range of permitted deviations from the agreed level); tolerance duration (how long a deviation from the agreed level can be tolerated); condition. Setting "writable" to true for all three attributes in Table 2 provides greater flexibility for both parties (providers and customers). However, in some examples, this may be changed. It should also be understood that the attribute values ​​provided in Table 2 are only examples and may be different in other examples. In some examples, the "condition" attribute defines what compensation may be provided to the network slice consumer if the consumer accepts a compromised service requirement within a specific range, time, and duration. For example, for a service requirement of "downlink throughput per slice", if 100MBps is agreed and this will not be delivered within a tolerable time of, for example, 5 minutes, the NSP will pay the NSC x$ for every 1MBps below 100MBps. Therefore, the condition may be set to "x$ for every 1MBps" (the amount of x may of course vary).

[0110] An example implementation of the Tolerance Index (TI) is now explained.

[0111] During the slice lifecycle, the NSP checks the SLA fulfillment of the customer's service. This check can be performed periodically or in response to an event (for example, receiving an indication of increased network traffic). If a service attribute has reached or is almost at a critical value (for example, close to non-compliance with the SLA), the NSP checks one or more customer tolerance indicators for that attribute. If the attribute is set to "tolerable", the NSP waits until the incident that caused the problem is over. The NSP can then take control of the situation. If the situation does not improve (for example, the situation reaches a tolerable limit), the NSP may take action to improve the situation.

[0112] If the situation does improve (e.g., the attribute is no longer close to a critical value), the NSP has avoided unnecessary work, cost, and risk.

[0113] The following describes in more detail Figure 2 In some examples, Figure 2 The process of the method is performed in a network device. In some examples, the process is performed by a management function (MF) that can be part of the network device. In some examples, the network device is located in a management system.

[0114] At S1, the MF forecasts an incoming network emergency (or determines that such an emergency exists). In other words, the MF determines that one or more service requirements (or attributes) of one or more services are resource deficient or are about to become resource deficient.

[0115] As shown in S2, the MF determines whether any service requirements are expected to be unsatisfied. For example, the MF determines whether the situation will cause the attribute to be at or close to a level that does not meet the SLA.

[0116] If the answer to S2 is "No", the process proceeds to S3, that is, nothing is done.

[0117] On the other hand, if the answer to S2 is "yes", the process proceeds to S4, where the criticality of the affected SLA attribute is determined.

[0118] In more detail, as shown in S5, determine whether (multiple) customers can tolerate non-compliance with the attribute. In other words, this involves determining whether one or more customers can tolerate non-compliance with the agreed service level. In some examples, this involves checking or looking up the TI of (multiple) corresponding customers. Therefore, it can be considered that the MF is configured to look up the tolerance indicator of one or more customers when determining whether one or more customers can tolerate non-compliance with the agreed service level. In some examples, the tolerance indicator can be considered to be associated with one or more service requirements (attributes). In some examples, there may be multiple TIs for multiple corresponding service requirements. In some examples, S5 involves determining the duration of non-compliance that can be tolerated.

[0119] If the determination at S5 is "yes" (i.e., non-compliance can be tolerated for a period of time), the flow proceeds to S6. At S6, the MF waits to see if the situation improves. Figure 2 In , the “event horizon” can be thought of as an upper tolerance limit. Therefore, one can consider configuring the MF to allow non-compliance with the agreed service level for those customers who can tolerate non-compliance.

[0120] The process then proceeds to S7 where it is determined whether the situation has improved.

[0121] If the determination of S7 is "YES", the flow proceeds to S3 (do nothing).

[0122] On the other hand, if the determination at S7 is "No", the flow proceeds to S8 where action is taken. For example, resource reconfiguration may be performed. Customers may also be notified. Thus, it may be considered that the MF is configured to prevent non-compliance with the agreed service level for those customers who cannot tolerate non-compliance.

[0123] Figure 3An exemplary process of a slice modification request initiated between a network slice consumer (NSC) 302 and a network slice provider (NSP) 304 is shown.

[0124] As shown in S1, the network slice provider (NSP) 304 receives a network slice instance (NSI) allocation / modification request from the network slice consumer (NSC) 302.

[0125] At S2, the NSP 304 invokes a feasibility check process based on the new network slice related requirements to check whether it is feasible to meet those requirements.

[0126] In some examples, the feasibility check is negative in some way, for example, it is determined that the NSI allocation / modification cannot be successful in some cases, or the NSP predicts that some emergency situation may occur after the allocation / modification.

[0127] After the feasibility check, at S3, the NSP 304 responds by proposing some tolerance indicator (TI) values ​​that facilitate satisfactory NSI allocation / modification.

[0128] NSC can choose whether to accept TI proposal.

[0129] exist Figure 3 In the example of FIG. 3 , the NSC accepts the proposed TI, as shown in S4. The NSC 302 accepts the TI value and invokes the management service of the NSP 304 to allocate / modify the NSI using the TI value.

[0130] At S5, the NSP 304 allocates / modifies slices with reference to the TI.

[0131] It is understood that tolerance indicators can contribute to one or more of the following:

[0132] Helps resolve network bottlenecks in the event of a network failure leading to contract breach and resource allocation / reallocation,

[0133] Allows slice optimization instantiation, configuration, reconfiguration, and scaling,

[0134] Avoid unnecessary network reconfiguration that could have a higher risk of violating another SLA,

[0135] Allows exact or accurate estimation of the consequences of SLA violations,

[0136] Allows for estimation of less critical reconfigurations or allows processes to be moved just in time and reconfigurations to be avoided,

[0137] · Has a favourable business aspect for NSPs in terms of avoiding fines,

[0138] · Has favorable business aspects for NSC: the agreed tolerance indicators for specific SLAs can be combined with service price discounts;

[0139] Increased flexibility in decision making about how to handle (multiple) customer data

[0140] Transform service provider (SP) decisions from speculative to known.

[0141] Now refer to Figure 4 describing in more detail possible wireless communication devices, Figure 4 A schematic partial cross-sectional view of a communication device 400 is shown. Such a communication device is generally referred to as a user equipment (UE) or terminal. Any device capable of sending and receiving radio signals can provide a suitable mobile communication device. Non-limiting examples include a mobile station (MS) or mobile device, such as a mobile phone or a so-called "smart phone", a computer provided with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA) or a tablet computer provided with wireless communication capabilities, or any combination of these, etc. For example, a mobile communication device can provide data communications for carrying communications such as voice, e-mail (email), text messages, multimedia, etc. Therefore, a variety of services can be supplied and provided to users through its communication device. Non-limiting examples of these services include two-way or multi-directional calls, data communications or multimedia services, or simply include access to data communication network systems such as the Internet. Broadcast or multicast data can also be provided to users. Non-limiting examples of content include downloads, television and radio programs, videos, advertisements, various alarms and other information.

[0142] A wireless communication device may be, for example, a mobile device, i.e., a device that is not fixed to a particular location, or may be a fixed device. A wireless device may or may not require human interaction to communicate. In the present teachings, the term UE or "user" is used to refer to any type of wireless communication device.

[0143] The wireless device 400 may receive signals over the air or radio interface 407 via appropriate means for receiving, and may transmit signals via appropriate means for transmitting radio signals. Figure 4 In the wireless device, the transceiver arrangement is schematically designated by block 406. The transceiver arrangement 406 may be provided, for example, by means of a radio part and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the wireless device.

[0144] The wireless device is typically provided with at least one data processing entity 401, at least one memory 402 and possibly other components 403 for use in the software and hardware assisted execution of the tasks it is designed to perform, including controlling access to and communication with access systems and other communication devices. The data processing, storage and other related control means may be provided on appropriate circuit boards and / or in a chipset. This feature is indicated by reference numeral 404. The user may control the operation of the wireless device through a suitable user interface such as a keypad 405, voice commands, a touch sensitive screen or keyboard, a combination thereof, etc. A display 408, a speaker and a microphone may also be provided. In addition, the wireless communication device may include appropriate connectors (wired or wireless) to other devices and / or for connecting external accessories (e.g., a hands-free device) thereto.

[0145] Figure 5 An example of a control device for a communication system is shown, for example, for coupling to and / or for controlling a station of an access system, such as a RAN node, such as a base station, a gNB, a central unit of a cloud architecture, or a node of a core network, such as an MME or S-GW, a scheduling entity (such as a spectrum management entity), or a server or host. The control device may be integrated with a node or module of the core network or RAN or external to it. In some embodiments, the base station includes a separate control device unit or module. In other embodiments, the control device may be other network elements such as a radio network controller or a spectrum controller. In some embodiments, each base station may have such a control device and a control device arranged in a radio network controller. The control device 500 may be arranged to provide control of communications in a service area of ​​the system. The control device 500 includes at least one memory 501, at least one data processing unit 502, 503 and an input / output interface 504. Through the interface, the control device may be coupled to a receiver and a transmitter of the base station. The receiver and / or the transmitter may be implemented as a radio front end or a remote radio head. For example, the control device 500 or the processor 501 may be configured to execute appropriate software code to provide control functions.

[0146] Figure 6 is a flow chart of a method according to an example. Figure 6 The process is from the perspective of a device. The device may be, for example, a network device. The device may, for example, include a management function (MF).

[0147] At S1 , the method comprises, in response to determining that a resource shortage or impending resource shortage is occurring in the communication network, determining whether an agreed-upon service level of one or more service requirements of one or more services will be affected.

[0148] At S2, when it is determined that the agreed service level of one or more service requirements of the one or more services will be affected, it is determined whether the one or more customers can tolerate non-compliance with the agreed service level.

[0149] Figure 7 is a flow chart of a method according to an example. Figure 7 The process is from the perspective of a device. The device may be, for example, a network device. The device may include, for example, an NSP device.

[0150] At S1, the method includes receiving a network slice instance allocation or modification request from a consumer of the network slice instance.

[0151] At S2, the method comprises determining whether the allocation or modification is feasible.

[0152] At S3, the method includes sending information to the consumer, the information including an offer of tolerance for the consumer's non-compliance with the agreed-upon service level.

[0153] Figure 8 is a flow chart of a method according to an example. Figure 8 The process is from the perspective of the device. The device may include, for example, a NSC device.

[0154] At S1, the method includes sending a network slice instance allocation or modification request to a provider of the network slice instance.

[0155] At S2 , the method includes receiving a proposal for a tolerance for non-compliance with an agreed-upon service level.

[0156] At S3 , the method includes sending an approval or disapproval of the proposed tolerance for non-compliance to the provider.

[0157] In general, various embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects of the invention may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, but the invention is not limited thereto. Although various aspects of the invention may be illustrated and described as block diagrams, flow charts, or using some other graphical representation, it is well understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general purpose hardware or controllers or other computing devices, or some combination thereof.

[0158] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation using only analog and / or digital circuitry), and (b) a combination of hardware circuitry and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware, and (ii) any portion of hardware processor(s) (including digital signal processor(s)), software, and memory(s) with software that work together to enable a device (such as a mobile phone or server) to perform various functions, (c) hardware circuitry and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s) that requires software (e.g., firmware) to operate, but that software may not be present when not required for operation. This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of hardware circuitry or processor(s) or portion(s) of a hardware circuitry or processor and its (or their) accompanying software and / or firmware. For example, the term circuitry would also cover, if applicable to a particular claim element, a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or networking equipment.

[0159] Embodiments of the present invention may be implemented by computer software that can be executed by a data processor of a mobile device, such as in a processor entity, or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products, including software routines, applets and / or macros) may be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform an embodiment when the program is run. One or more computer executable components may be at least one software code or a portion thereof.

[0160] Furthermore, it should be noted at this point that any block of the logic flow in the figure may represent a program process, or interconnected logic circuits, blocks and functions, or a combination of program processes and logic circuits, blocks and functions. The software may be stored on physical media such as memory chips or memory blocks implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants CDs. Physical media is a non-transient medium.

[0161] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0162] Embodiments of the present invention may be practiced in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0163] The foregoing description provides a complete and informative description of exemplary embodiments of the present invention by way of non-limiting examples. However, various modifications and adaptations may become apparent to those skilled in the relevant art in view of the foregoing description when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of the present invention will still fall within the scope of the present invention as defined in the appended claims. Indeed, there are other embodiments that may include a combination of one or more embodiments with any other embodiment discussed above.

Claims

1. An apparatus comprising components for performing the following operations: receiving a network slice instance allocation or modification request from a consumer of the network slice instance; determining whether the assignment or modification is feasible; and Information is sent to the consumer, the information including an offer of tolerance for the consumer's non-compliance with an agreed-upon service level. 2 . The apparatus of claim 1 , wherein the component is further configured to perform receiving an approval or disapproval of the proposed tolerance for non-compliance from the consumer.

3. An apparatus according to claim 1 or claim 2, wherein the component is further configured to perform allocation or update of the network slice instance.

4. An apparatus according to claim 1 or claim 2, wherein the component comprises at least one processor; and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to cause execution of the apparatus together with the at least one processor.

5. An apparatus comprising means for performing the following operations: Send a network slice instance allocation or modification request to the provider of the network slice instance; receiving an offer of tolerance for non-compliance of the device with an agreed-upon service level; and An approval or disapproval of the proposed tolerance for non-compliance is sent to the provider.

6. The apparatus of claim 5, wherein the component comprises at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to cause execution of the apparatus together with the at least one processor.

7. A method comprising: receiving a network slice instance allocation or modification request from a consumer of the network slice instance; determining whether the assignment or modification is feasible; as well as Information is sent to the consumer, the information including an offer of tolerance for the consumer's non-compliance with an agreed-upon service level.

8. The method of claim 7, comprising receiving from the consumer an approval or disapproval of the proposed tolerance for non-compliance.

9. The method according to claim 7 or claim 8 includes allocating or updating the network slice instance.

10. A method comprising: Send a network slice instance allocation or modification request to the provider of the network slice instance; receiving proposals for tolerance of non-compliance with agreed service levels; as well as An approval or disapproval of the proposed tolerance for non-compliance is sent to the provider.

11. A computer program comprising instructions for causing an apparatus to at least: receiving a network slice instance allocation or modification request from a consumer of the network slice instance; determining whether the assignment or modification is feasible; and Information is sent to the consumer, the information including an offer of tolerance for the consumer's non-compliance with an agreed-upon service level.

12. A computer program comprising instructions for causing an apparatus to at least: Send a network slice instance allocation or modification request to the provider of the network slice instance; receiving an offer of tolerance for non-compliance of the device with an agreed-upon service level; and An approval or disapproval of the proposed tolerance for non-compliance is sent to the provider.

Images