Radio communication network with multi threshold based SLA monitoring for radio resource management

A radio communication network includes: a network orchestration entity, configured to orchestrate a plurality of network resources to set up at least one logical network of a plurality of logical networks based on a logical network-specific service level agreement (SLA); a radio scheduler, configured to schedule radio resources of the at least one logical network based on a scheduling strategy; a monitoring entity, configured to monitor performance information from the at least one logical network; and a controller, configured to: determine an SLA metric for the at least one logical network based on the monitored performance information from the at least one logical network; detect a threshold violation of the SLA metric with respect to a set of thresholds associated with the at least one logical network; and adjust the scheduling strategy based on the detected threshold violation.

CROSS-REFERENCE TO RELATED APPLICATIONS

Priority is claimed to European Patent Application No. EP 16200886.6, filed on Nov. 28, 2016, the entire disclosure of which is hereby incorporated by reference herein.

TECHNICAL FIELD

The present disclosure relates to a radio communication network, in particular a 5G radio network, with multi threshold based SLA (Service Level Agreement) monitoring for radio resource management (RRM).

BACKGROUND

Constructing logical networks also referred to as network slicing is a key concept for next generation mobile communications networks such as 5G networks. Each network slice can be considered as a logical network with well-defined Service Level Agreements (SLAs), i.e. official commitments prevailing between a service provider and the customer about network services, quality, availability and responsibilities, based on a corresponding orchestration of required network resources. For the service provider it is essential to comply with the committed SLA not only to avoid possible penalties but to maintain scheduling of network resources and hence to keep the whole communication network stable. An unplanned re-orchestration of a network slice will be seen as the worst case situation by the network operator and should be avoided by all possible means.

SUMMARY

In an exemplary embodiment, the present invention provides a radio communication network. The radio communication network includes: a network orchestration entity, configured to orchestrate a plurality of network resources to set up at least one logical network of a plurality of logical networks based on a logical network-specific service level agreement (SLA); a radio scheduler, configured to schedule radio resources of the at least one logical network based on a scheduling strategy; a monitoring entity, configured to monitor performance information from the at least one logical network; and a controller, configured to: determine an SLA metric for the at least one logical network based on the monitored performance information from the at least one logical network; detect a threshold violation of the SLA metric with respect to a set of thresholds associated with the at least one logical network; and adjust the scheduling strategy based on the detected threshold violation.

DETAILED DESCRIPTION

Exemplary embodiments of the invention provide for efficient and stable operation of a radio communication network, in particular in a next generation mobile network such as a 5G network, complying with the admitted SLAs as described above.

Exemplary embodiments of the invention utilize a logical entity monitoring a defined SLA metric and giving information to the Radio Resource Management (RRM) functions of the system, e.g. Admission Control (AC), Allocation and Retention Priority (ARP) and radio resource scheduler. Exemplary embodiments of the invention derive a scheduling strategy, e.g. by applying dynamic weights, based on the status of defined SLA metrics of multiple network slices. Therefore, multiple correlated thresholds per slice and across slices can be defined based on the slice specific SLA metric. Based on the differences between the intermediate SLA status and the thresholds, the scheduling strategy (or the dynamic weights, respectively) can be dynamically adapted to prioritize data flows when radio resources are allocated in order to optimize radio resource scheduling decision.

In order to describe the invention in detail, the following terms, abbreviations and notations will be used:

5G: fifth generation mobile network

LTE: Long Term Evolution

BS, eNodeB: Base Station or radio cell

MCS: Modulation and Coding Scheme

UE: User Equipment

FSS: frequency selective scheduling

SLA: service level agreement

TPB: Transmission Point Blanking

JT: Joint Transmission

HARQ: Hybrid automatic repeat request

MAC: Media Access Control layer

PHY: Physical layer

VNF: Virtual Network Function

DSP: Digital Signal Processor

KPI: Key Performance Indicator

RRM: Radio Resource Management

AC: Admission Control

ARP: Allocation and Retention Priority

QCI: Quality Channel Indicator

TFT Traffic Flow Template

GBR: Guaranteed Bit Rate

TTI: Transmission Time Interval

The communication systems, devices and methods described in the following may be based on service-level agreements (SLA) and SLA metrics. An SLA is defined as an official commitment that prevails between a service provider and the customer. Particular aspects of the service, such as quality, availability and responsibilities are agreed between the service provider and the service user. Services should be provided to the customer as agreed upon in the contract. Service providers and network operators will commonly include service level agreements within the terms of their contracts with customers to define the level(s) of service. The SLA may use technical definitions in terms of mean time between failures (MTBF), mean time to repair or mean time to recovery (MTTR); identifying which party is responsible for reporting faults or paying fees; responsibility for various data rates; throughput; jitter; or similar measurable details.

SLAs can include various service performance metrics or SLA metrics with corresponding service level objectives. Metrics commonly agreed to in these cases may include, for example, MIB (Management Information Base) variables of the IETF Structure of Management Information (SMI) such as system uptime, number of invocations, outage period or technical network performance metrics such as loss, utilization, delay, etc. which are collected via management directives such as management protocol messages, management interfaces, URIs, etc. Composite metrics use a specific function to average one or more metrics over a specific amount of time, for example average availability, or breaking them down according to certain criteria, for example minimum throughput, maximum response time, top 10%, etc.

According to a first aspect, the invention relates to a radio communication network, comprising: a network orchestration entity, configured to orchestrate a plurality of network resources to set up at least one logical network of a plurality of logical networks based on a logical network specific service level agreement (SLA); a radio scheduler configured to schedule radio resources of the at least one logical network based on a scheduling strategy; a monitoring entity, configured to monitor performance information from the at least one logical network; and a controller, configured: to determine an SLA metric for the at least one logical network based on the monitored performance information from the at least one logical network, to detect a threshold violation of the SLA metric with respect to a set of thresholds associated with the at least one logical network, and to adjust the scheduling strategy based on the detected threshold violation.

Such a radio communication network provides efficient and stable operation. The multi threshold based detection of threshold violations gives indications of possible performance and/or QoS bottlenecks in the radio communication network. An automatic escalation strategy can be implemented by the controller in order to increase availability of radio resources and to increase efficiency and stability of the network. Hence, an unplanned re-orchestration of a logical network or a network slice can be avoided.

In an implementation form of the radio communication network the scheduling strategy is based on applying a set of weights to the radio resources of the at least one logical network, and the controller is configured to adjust the scheduling strategy by adjusting the set of weights.

This provides the advantage that radio resources can be efficiently added if required by simply increasing the weights assigned to the radio resources.

In an implementation form of the radio communication network the controller is configured to increase the set of weights applied to the radio resources of the at least one logical network based on a first detected threshold violation.

This provides the advantage that a first detected threshold violation results in an increase of the weights, i.e. a provision of more radio resources for the logical network in order to relax a possible lack of resources that has caused the SLA metric reduction and thus the first detected threshold violation.

In an implementation form of the radio communication network the controller is configured to further increase the set of weights applied to the radio resources of the at least one logical network based on a second detected threshold violation.

This provides the advantage that an escalation strategy can be provided. When the second threshold violation is detected, a further increase of the weights results in a still higher availability of radio resources for the logical network in order to resolve the problem detected by the SLA metric.

In an implementation form of the radio communication network contexts of the thresholds of the set of thresholds associated with the at least one logical network are prioritized. A context of a threshold may relate to a radio resource allocation, i.e. an action of allocating (additional) radio resources to combat the threshold violation.

This provides the advantage that a violation of the second threshold which may have a higher priority than a first threshold will result in a much higher allocation of radio resources for the logical network than a violation of the first threshold. A violation of the first threshold may occur more often than a violation of the second threshold. Hence priorization of the contexts of thresholds results in a higher efficiency of the radio communication network and a more stable performance.

A context for allocation of radio resources may be considered in this disclosure based on the three aspects: (ultra-)high throughput, (ultra-)low latency and (ultra-)high reliability. I.e. a violation of a threshold may result in an allocation of a higher amount of radio resources to increase throughput and/or in an earlier allocation of radio resources to reduce latency and/or in an allocation of more robust and reliable radio resources, e.g. by using redundant radio resources or by using more robust modulation and coding schemes to improve reliability.

In an implementation form of the radio communication network the controller is configured to indicate the radio scheduler switching a scheduling strategy for scheduling the radio resources based on detecting a specific number of threshold violations or based on detecting a threshold violation of a specific threshold of the set of thresholds.

This provides the advantage that a further escalation can be to switch the scheduling strategy in order to acquire stable performance.

In an implementation form of the radio communication network the radio scheduler is configured to switch the scheduling strategy for scheduling the radio resources responsive to the indication received from the controller.

This provides the advantage that the radio scheduler can automatically switch the scheduling strategy based on an indication from the controller.

In an implementation form of the radio communication network the controller is configured to indicate a detection of a specific number of threshold violations or a detection of a threshold violation of a specific threshold of the set of thresholds to the network orchestration entity.

This provides the advantage that the escalation strategy when detecting threshold violations can be flexibly defined and adapted.

In an implementation form of the radio communication network the network orchestration entity is configured to re-orchestrate the plurality of network resources responsive to the indication received from the controller.

This provides the advantage that a re-orchestration of one logical network or of the whole radio communication network can be initiated by the network orchestration entity upon indication from the controller. This may be the last escalation stage.

In an implementation form of the radio communication network the controller is configured to adjust the scheduling strategy according to a prioritization of data flows transported by the at least one logical network.

This provides the advantage that depending on a specific type or priority assigned to a data flow, this data flow may obtain more or less radio resources. A data flow marked with high priority may obtain a larger amount of radio resources while a data flow marked with low priority may obtain a lesser amount of radio resources.

In an implementation form of the radio communication network the controller is configured to adjust the scheduling strategy based on adjusting a QCI class of the data flows and/or based on a deviation of a monitored Key Performance Indicator (KPI) from a KPI determined by the SLA of the at least one logical network.

This provides the advantage that the scheduling strategy can be flexibly changed according to the requirements of the network. KPIs can be flexibly defined for a logical network of the whole radio communication network.

In an implementation form of the radio communication network distances between the thresholds of the set of thresholds associated with the at least one logical network are correlated.

This provides that advantage that a pre-known escalation strategy can be provided, i.e. an escalation strategy in which a distance between a first threshold violation, a second threshold violation, etc. is known and reproducible to the operator.

In an implementation form of the radio communication network the controller is configured to normalize a first SLA metric determined for a first logical network of the plurality of logical networks with respect to a second SLA metric determined for a second logical network of the plurality of logical networks according to a common evaluation strategy.

This provides the advantage that a threshold violation for a first logical network has the same meaning as a threshold violation for a second logical network. Both threshold violations are comparable and similar amount of resources can be provided to resolve the bottleneck.

In an implementation form of the radio communication network the controller is configured to adjust the scheduling strategy in the same manner when a threshold violation of a threshold associated with the first logical network and a corresponding threshold of different level associated with the second logical network is detected.

This provides the advantage that a common or a slice-specific escalation strategy for all logical networks of the radio communication network can be implemented, i.e. an escalation strategy which has the same meaning for a first logical network as for a second logical network. In particular the same amount of resources can be allocated for the first logical network as for the second logical network when a threshold of the first logical network is violated and a corresponding threshold of the second logical network is violated. Note that these corresponding thresholds do not have to be set at the same values. For example a threshold violation of a threshold set at a first level, e.g. 0.9 in a first logical network may correspond to a threshold violation of a threshold set at a second level, e.g. 0.7 in a second logical network. The same escalation strategy may be applied and the same amount of radio resources may be allocated to combat the threshold violation. In the above example, the SLA metric associated with the threshold set at 0.9 may have a higher fluctuation range than the SLA metric associated with the threshold set at 0.7. Note that the setting of thresholds as described in this disclosure also includes the setting of fluctuation ranges for the SLA metrics.

In an implementation form of the radio communication network the radio communication network comprises a network according to a fifth generation (5G) or according to a further generation, and the at least one logical network is a network slice of the 5G network communicating with a physical layer of the 5G network.

The 5G network increases the efficiency of communication and provides in particular a higher data throughput, lower latency, particularly high reliability, a much higher connection density and a larger mobility area. The 5G network increases the operational flexibility and provides tailored features and functions while saving network resources. This increased performance is accompanied by the ability to control highly heterogeneous environments and the ability to secure trust, identity and privacy of users.

According to a second aspect, the invention relates to a method for operating a radio communication network, the method comprising: orchestrating, by a network orchestration entity, a plurality of network resources to set up at least one logical network of a plurality of logical networks based on a logical network specific service level agreement (SLA); scheduling, by a radio scheduler, radio resources of the at least one logical network based on a scheduling strategy; monitoring, by a monitoring entity, performance information from the at least one logical network; and determining, by a controller, an SLA metric for the at least one logical network based on the monitored performance information from the at least one logical network, to detect a threshold violation of the SLA metric with respect to a set of thresholds associated with the at least one logical network, and to adjust, by the controller, the scheduling strategy based on the detected threshold violation.

Such a method provides efficient and stable operation of a radio communication network. The multi threshold based detection of threshold violations gives indications of possible performance and/or QoS bottlenecks in the radio communication network. An automatic escalation strategy can be implemented by the controller in order to increase availability of radio resources and to increase efficiency and stability of the network. Hence, an unplanned re-orchestration of a logical network or a network slice can be avoided.

In the following detailed description, reference is made to the accompanying drawings, which form a part thereof, and in which is shown by way of illustration specific aspects in which the disclosure may be practiced. It is understood that other aspects may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

It is understood that comments made in connection with a described method may also hold true for a corresponding device or system configured to perform the method and vice versa. For example, if a specific method step is described, a corresponding device may include a unit to perform the described method step, even if such unit is not explicitly described or illustrated in the figures. Further, it is understood that the features of the various exemplary aspects described herein may be combined with each other, unless specifically noted otherwise.

The radio communication network as described hereinafter may include a plurality of different network entities. A network entity may be a computer host, a computer server or some network node. A network entity may be a hardware unit, e.g. a computer server, a network node or device, a PC, a tablet, a smartphone, a router, a gateway or a whole computer network. A network entity may be a software unit, e.g. an application program or software module on a PC, tablet, smartphone or any other hardware device.

The radio communication network or radio communication system or wireless communication network may be implemented by various technologies, in particular as a communication network based on mobile communication standards such as LTE, in particular LTE-A and/or OFDM and successor standards such as 5G. The components and network nodes of such a communication network described below may be implemented as electronic devices or electronic network entities. The described devices and network entities may include integrated circuits and/or passives and may be manufactured according to various technologies. For example, the circuits may be designed as logic integrated circuits, analog integrated circuits, mixed signal integrated circuits, optical circuits, memory circuits and/or integrated passives.

The described network components, in particular the radio cells and user equipments may be configured to transmit and/or receive radio signals and performing associated signal processing. Radio signals may be or may include radio frequency signals radiated by a radio transmitting device (or radio transmitter or sender) with a radio frequency lying in a range of about 3 kHz to 300 GHz. The frequency range may correspond to frequencies of alternating current electrical signals used to produce and detect radio waves.

The communication networks described herein after may be designed in accordance to mobile communication standards such as e.g. the Long Term Evolution (LTE) standard or the advanced version LTE-A thereof. LTE (Long Term Evolution), marketed as 4G LTE and 5G NR (new radio), is a standard for wireless communication of high-speed data for mobile phones and data terminals. 5G NR is a 3GPP terminology.

FIG. 1shows a schematic diagram illustrating a radio communication network100according to the disclosure. The radio communication network100includes a network orchestration entity130, a radio scheduler140, a monitoring entity120and a controller110.

The network orchestration entity130orchestrates139a plurality of network resources134,135,136,137to set up at least one logical network131of a plurality of logical networks131,132,133based on a logical network specific service level agreement SLA138. The radio scheduler140schedules141radio resources of the at least one logical network131based on a scheduling strategy142. The monitoring entity120monitors122performance information121from the at least one logical network131. The controller110is configured: to determine an SLA metric111for the at least one logical network131based on the monitored performance information121from the at least one logical network131, to detect a threshold violation112of the SLA metric111with respect to a set of thresholds113associated with the at least one logical network131, and to adjust114the scheduling strategy142based on the detected threshold violation112.

The radio scheduler140can be implemented as an entity arranged external to the logical network131as shown inFIG. 1. Alternatively, the radio scheduler140can be arranged inside the logical network131, for example collocated with or arranged nearby to one of the network resources134,135,136,137of the logical network131, e.g. as described below with respect toFIG. 2.

The network orchestration entity130may orchestrate139network resources134,135,136,137and radio resources to set up the logical network131. Radio resources may be for example time-frequency resources for transmission over an air interface. There may be different Radio Access Technologies (RATs) within one logical network131. Network resources may be Servers, Routers, Gateways and other network infrastructure, e.g. as described below with respect toFIGS. 5 and 6.

The scheduling strategy142may be based on applying a set of weights to the radio resources of the at least one logical network131. The controller110may adjust the scheduling strategy142by adjusting114the set of weights. The controller110may increase the set of weights applied to the radio resources of the at least one logical network131based on a first detected threshold violation303, e.g. an event when the SLA metric302(Slice2) falls below the first threshold312(Slice2) for the first time as exemplary depicted for Slice2inFIG. 3. The controller110may further increase the set of weights applied to the radio resources of the at least one logical network131based on a second detected threshold violation304, e.g. an event when the SLA metric302(Slice2) falls below the second threshold322(Slice2) for the first time as exemplary depicted for Slice2inFIG. 3. When increasing the weights, a higher amount of radio resources can be allocated resulting in a better service quality and thus a higher value for the SLA metric315as can be seen fromFIG. 3described below.

The scheduling strategy142may be implemented in the radio scheduler140, e.g. as a table or as an algorithm. Alternatively, the scheduling strategy may be implemented in a database to which the radio scheduler140has direct access or indirect access via the controller110and/or the network orchestration entity130. For example, the scheduling strategy142may be implemented together with the SLA138within a database207of the network operator, e.g. as described below with respect toFIG. 2.

The contexts of thresholds311,321,331of the set of thresholds113associated with the at least one logical network131may be prioritized. I.e. when the SLA metric302(Slice2) falls below the second threshold322(Slice2) a priorization to allocate radio resources can be higher than a priorization when the SLA metric302(Slice2) falls below the first threshold312(Slice2), as the first situation is less critical for the service level agreement than the second situation. When a violation316is detected as shown inFIG. 3, the priority to allocate radio resources may be the highest.

The controller110may indicate the radio scheduler140switching a scheduling strategy142for scheduling the radio resources based on detecting a specific number of threshold violations303,304,305or based on detecting a threshold violation of a specific threshold of the set of thresholds113. A priorization of a context (e.g. radio resource allocation with respect to throughput, delay, and robustness) of the specific threshold may be set higher than a priorization of a context of the other thresholds.

The radio scheduler140may switch the scheduling strategy142for scheduling the radio resources responsive to the indication received from the controller110. The controller110may indicate a detection of a specific number of threshold violations303,304,305or a detection of a threshold violation of a specific threshold of the set of thresholds113to the network orchestration entity130. The network orchestration entity130may re-orchestrate139the plurality of network resources134,135,136,137responsive to the indication received from the controller110. A multi-escalation strategy may be applied by the network orchestration entity130for re-orchestrating139the network resources134,135,136,137, e.g. as described below with respect toFIG. 4.

The controller110may adjust114the scheduling strategy142according to a prioritization of data flows transported by the at least one logical network131. For example, the controller110may check the header of IP data traffic to read the data type or other useful information about the data traffic. Depending on this data type the data flow may obtain more radio resources, e.g. if the data flow is assigned to a high priority or the data flow may obtain a less amount of radio resources, e.g. if the data flow is assigned to a low priority. The controller110may for example adjust the scheduling strategy142based on adjusting a QCI class of the data flows and/or based on a deviation of a monitored Key Performance Indicator (KPI) from a KPI determined by the SLA138of the at least one logical network131. Such KPI may be monitored by the monitoring entity120.

Distances between the thresholds311,321,331of the set of thresholds associated with the at least one logical network131may be correlated. I.e. the correlation is related to all thresholds or at least a subset of the thresholds within one logical network. For example, the thresholds may have the same distance with respect to each other, or the distance between thresholds may increase or decrease from threshold to threshold. The controller110may normalize a first SLA metric determined for a first logical network131of the plurality of logical networks with respect to a second SLA metric determined for a second logical network132of the plurality of logical networks according to a common evaluation strategy. This means that a threshold for a first logical network131has the same effect or quality than a threshold for a second logical network132, i.e. both logical networks are comparable based on the common evaluation strategy.

Alternatively or additionally, distances between thresholds311,321,331associated with the first logical network131and corresponding thresholds312,322,332associated with the second logical network132may be correlated. I.e. the correlation is between thresholds or at least a subset of thresholds belonging to different logical networks. For example, the thresholds of one logical network and another logical network may have the same distance with respect to each other, or the distance may increase or decrease from threshold to threshold.

The thresholds may be set-up by the network orchestration entity130, e.g. at set-up of a logical network131or when the logical network131is re-orchestrated. For example at start-up the network operator knows the logical networks and the associated thresholds to be set up by the network orchestration entity130. During operation of these logical networks, there may be demand for set up of an additional logical network with associated thresholds. Then, the network orchestration entity130can set up the additional logical network and provide the respective thresholds to the controller110. The thresholds provided by the network orchestration entity130may be usually raw thresholds which are not normalized with thresholds of other logical networks as during the operation of the system different demands for adding or removing slices (logical networks) with associated thresholds may occur. A comparison or normalization of these thresholds can then be performed (at run-time) by the controller110or optionally by the network orchestration entity130. Note, that a normalization of the SLA metrics can be performed or alternatively a normalization of the thresholds.

The radio communication network100may include a network500,600according to a fifth generation (5G) or according to a further generation, e.g. as described below with respect toFIGS. 5 and 6. The at least one logical network131may be a network slice610b,611b,612bof the 5G network500,600communicating with a physical layer505of the 5G network500,600, e.g. as described below with respect toFIGS. 5 and 6.

With respect to the radio communication network100described above, a method for operating the radio communication network100can include the following blocks: orchestrating, by a network orchestration entity130, a plurality of network resources to set up at least one logical network131of a plurality of logical networks based on a logical network specific service level agreement (SLA)138; scheduling, by a radio scheduler140, radio resources of the at least one logical network131based on a scheduling strategy; monitoring, by a monitoring entity120, performance information from the at least one logical network131; and determining, by a controller110, an SLA metric111for the at least one logical network131based on the monitored performance information from the at least one logical network131, to detect a threshold violation112of the SLA metric111with respect to a set of thresholds113associated with the at least one logical network131, and to adjust, by the controller110, the scheduling strategy based on the detected threshold violation112.

FIG. 2shows a schematic diagram illustrating a radio communication network200according to the disclosure. The radio communication network200is a specific implementation of the radio communication network100described above with respect toFIG. 1.

The network orchestration entity, also referred to as Orchestrator205orchestrates139a plurality of network resources as exemplary shown within in the depicted orchestrated radio access network210to set up one or more logical networks based on a logical network specific service level agreement SLA. For example a first logical network may include components211,220,214,221,215,222,216. A second logical network may include components225,219. A third logical network may include components212,223,217,224,218. A fourth logical network may include components213,226,227,228, etc. The radio scheduler, e.g.211,219,212,213schedules radio resources of the respective logical network based on a scheduling strategy or scheduling scheme208. The monitoring entity, also referred to as SLA/QoS monitor203monitors performance information from the respective logical network. The controller, also referred to as software controller201is configured: to determine an SLA metric for the respective logical network based on the monitored performance information of the corresponding logical network, to detect a threshold violation of the SLA metric with respect to a set of thresholds associated with the corresponding logical network, e.g. as described below with respect toFIG. 3, and to adjust the scheduling strategy based on the detected threshold violation.

As shown inFIG. 2, the scheduling strategy142described above with respect toFIG. 1, may be implemented in a database207with all kinds of scheduling schemes208which can be flexibly combined or exchanged at the base station when necessary based on SDN and NFV principles.

During some situations in the network200it makes sense to create temporarily, e.g. a BS cluster where a proportional fair (PF) based, QoS aware, joint transmission coordinated multi point (JT CoMP) flavored scheduler is applied (right cluster within the radio access network210with elements213,226,227,228). Such a cluster can be set up by the Orchestrator205as a first logical network or a first slice, e.g. a first logical network131as described above with respect toFIG. 1. While for another area in the network210a smaller cluster is created where a PF and QoS flavored scheduler is applied at each BS of the cluster. Such a cluster can be set up by the Orchestrator205as a second logical network or a second slice, e.g. a second logical network132as described above with respect toFIG. 1. In addition a centralized entity212which performs CoMP Transmission point blanking (TPB) may be formed (middle cluster within the network210ofFIG. 2including elements212,217,218,223,224) satisfying the QoS of each specific user. Such a cluster can be set up by the Orchestrator205as a third logical network or a third slice, e.g. a third logical network133as described above with respect toFIG. 1. Another base station225(with collocated radio scheduler218) schedules radio resources for its own based on a combination of a PF, SLA and QoS aware with carrier aggregation based ICIC scheme. Such a cluster can be set up by the Orchestrator205as a fourth logical network or a fourth slice, e.g. a further logical network as described above with respect toFIG. 1. The system gains from the flexibility to react on locally dynamic changes in the network (e.g. a lot of cell edge UEs got active and centralized scheduling should be applied to improve cell edge performance without decreasing the spectral efficiency of the system).

A logical network or slice may also be set up as a combination of different clusters with the applied radio resource management (RRM) methods. Multiple logical networks or slices may share one (or more) cluster, for example, a first cluster may include base stations BS1and BS2while a second cluster may include base station BS3. Then BS1may be used for slice1, BS3may be used for slice2and BS2may be used for both, slice1and slice2.

To adapt the scheduling scheme in a dynamic way as described above, a centralized software controller201as well as a live monitoring entity203is provided which observes the current performance at each individual BS or radio cell. The monitor203provides frequently the status and the controller201derives a critical situation (e.g. SLA of a network slice or QoS of a specific flow cannot be fulfilled or thresholds violated as described above with respect toFIG. 1or below with respect toFIG. 3), as an alternative. Then, the controlling entity201takes a decision what kind of scheduling algorithms and metrics should be used at the problematic area within the network210. For instance, a lot of cell edge users are active and the cell edge performance of a certain BS cluster needs to be increased, then it may make sense to load temporarily a centralized scheduler which interacts with the BS local proportional fair and QoS aware flavored scheduler. The controller201loads an individualized scheduler for that specific issue to improve the performance of that part of the network210. The controller201can access the database207via the orchestrator205or in alternative implementation (not shown inFIG. 2), the controller201can directly access the database207without the orchestrator205.

The radio communication network200shown inFIG. 2includes a plurality of radio cells221,222,223,224,225,226,227,228, for example base stations or WiFi Hotspots or other small cells, a plurality of radio schedulers214,215,216,217,219,224and other network schedulers211,212,213, a monitor203, e.g. for monitoring service level agreements and/or QoS and a controller201, e.g. a software controller. The plurality of radio cells221,222,223,224,225,226,227,228, the plurality of radio schedulers214,215,216,217,219,224and other network schedulers211,212,213are arranged in an orchestrated radio access network210that may be controlled by the software controller201and monitored by the SLA/QoS monitor203. The radio communication network200further includes an orchestrator205for setting-up or initializing the radio access network210. The radio communication network200further includes a database207for storing basis scheduling schemes208and a database209for storing ICIC schemes, e.g. as virtual network functions.

The radio cells221,222,223,224,225,226,227,228may transmit data flows to corresponding user equipments (not shown inFIG. 2) by using radio resources, e.g. time-frequency resources scheduled to the radio cells by radio schedulers214,215,216,217,224,213for transmission of the data flows, e.g. as described above with respect toFIG. 1.

The radio schedulers214,215,216,217,219,224may be collocated to the corresponding radio cells221,222,223,224,225,226,227,228and may schedule radio resources, e.g. time-frequency space resources to the corresponding radio cells according to a respective scheduling strategy142, e.g. as described above with respect toFIG. 1.

The SLA/QoS monitor203monitors performance information from the radio cells221,222,223,224,225,226,227,228of the radio access network210and the controller201adjusts/adapts the respective scheduling strategy142of the corresponding radio scheduler214,215,216,217,219,224based on the monitored performance information as described above with respect toFIG. 1.

The radio cells221,222,223,224,225,226,227,228and radio schedulers214,215,216,217,219,224of the radio access network210may be grouped in different clusters as shown inFIG. 2. For example, a first cluster (or first logical network) may include a coordinated beamforming network entity211coordinating an eICIC QoS round-robin (RR) radio scheduler214collocated with a small radio cell220, an eICIC QoS proportional fair (PF) radio scheduler215collocated with a base station221and an eICIC QoS round robin radio scheduler216collocated with a small radio cell222.

A second cluster (or second logical network) may include a coordinated multipoint (CoMP) TPS network entity212coordinating a QoS PF radio scheduler217collocated with a base station223and a QoS PF radio scheduler218collocated with a base station224.

A third cluster (or third logical network) may include a service level agreement (SLA) QoS PF radio scheduler219collocated with a base station225.

A fourth cluster (or fourth logical network) may include a stand-alone CoMP joint transmission (JT) QoS PF radio scheduler213scheduling three base stations226,227,228.

The orchestrator205may load scheduling metrics from the plurality of scheduling metrics208stored in the database207, e.g. based on a request for setting up a network slice, e.g. a network slice510b,511b,512bas described below with respect toFIGS. 5 and 6. The physical infrastructure may form the radio access network210to bear one or more logical networks (slices) which may include one or more clusters as described above. Each or some cluster may be divided between different logical networks such that resources of the cluster are allocated to these logical networks.

The orchestrator205may assign different radio schedulers214,215,216,217,219,224to different groups of radio cells220,221,222,223,224,225,226,227,228according to their specific scheduling strategy requirements. The orchestrator205may for example configure the scheduling metrics208based on a service function chain template which defines multiple combinations of metrics and ICIC schemes206.

The software controller201may select one or a combination of the basic scheduling schemes208and/or one or a combination of the ICIC schemes206via the orchestrator205from the database207,209for adjusting a respective radio scheduler schedulers214,215,216,217,219,224. The basic scheduling schemes208may include for example the schemes round robin, max/min, proportional fair, equal data rate, etc. The ICIC schemes206may for example include the schemes enhanced inter-cell interference coordination (eICIC), carrier aggregation (CA) based ICIC, coordinated multi-point (CoMP) transmission point blanking (TPB), CoMP joint transmission (JT), coordinated beamforming, centralized scheduling, etc. The scheduling may be based on a quality-of-service (QoS) class and/or a service level agreement (SLA). The SLA/QoS monitor203may for example monitor performance information from the radio cells220,221,222,223,224,225,226,227,228, such as: QoS, SLA for a logical network210, a traffic demand for a UE and channel conditions of radio links to the UEs.

The software controller201may adjust the scheduling strategies of the radio schedulers214,215,216,217,219,224per radio cell or per radio cell cluster. The software controller201may activate or deactivate combinations of scheduling metrics (208). A radio scheduler (or the radio schedulers) of a specific logical network (e.g. network210) may apply a first scheduling strategy to a cluster of radio cells220,221,222located in a first area of the radio communication network200, and a second scheduling strategy to a cluster of base stations223,224located in a second area of the radio communication network200. The scheduling strategy may be based on a scheduling metric.

The radio communication network200may include a network500,600according to a fifth generation (5G) or according to a further generation, e.g. as described below with respect toFIGS. 5 and 6. A part of the radio schedulers214,215,216,217,219,224or all of them may be implemented as a virtual network function622of an activation layer504of the 5G network500,600communicating with a physical layer505of the 5G network500,600, e.g. as described below with respect toFIGS. 5 and 6.

The radio schedulers may schedule radio resources of a first network slice610bof the 5G network500,600and radio resources of a second network slice611bof the 5G network500,600according to a common scheduling metric which may be designed according to an optimization criterion to best fit requirements of the first network slice610band the second network slice611bconcurrently.

FIG. 3shows a schematic diagram illustrating multi threshold based SLA monitoring300according to the disclosure. The described SLA monitoring300can be implemented by the radio communication network100described above with respect toFIG. 1or the radio communication network200described above with respect toFIG. 2.

FIG. 3shows an SLA metric315obtained by SLA monitoring of a monitoring entity, e.g. a monitoring entity120as described above with respect toFIG. 1or an SLA/QoS monitor203as described above with respect toFIG. 2. The SLA metric312includes an SLA metric301of a first slice, e.g. a first logical network131as described above with respect toFIG. 1, and an SLA metric302of a second slice132, e.g. a second logical network132as described above with respect toFIG. 1. A plurality of thresholds is shown relating to the first slice131and the second slice132. A first threshold for slice1is denoted as311, a second threshold for slice1is denoted as321and an Nth threshold for slice1is denoted as331. A first threshold for slice2is denoted as312, a second threshold for slice2is denoted as322and an Nth threshold for slice2is denoted as332. A threshold indicating an overall violation is denoted as316.

Based on the SLA status dynamic weights can be derived317which can be used for the scheduling decision340. The scheduling decision340may depend on frequency-time resources341of air interface variants (AIV) for the first slice131and the second slice132. The scheduling decision340may further depend on an available bandwidth342for the first slice131and the second slice132. Quality Class Indicator Key Performance Indicators (QCI KPIs) may be determined based on which the SLA metrics may be updated318.

In the following, one exemplary implementation of multi threshold based SLA monitoring300is described. In this implementation, referred to as Example 1, two slices are running on the same physical infrastructure. An SLA metric301,302for each slice131,132is calculated and must be normalized to compare slice specific SLAs. Multiple thresholds311,312,321,322,331,332are defined which are intra and inter slice correlated to derive weights for scheduling decisions in a more precise way (higher granularity/resolution). Each threshold defines a region of the normalized SLA metric.FIG. 3shows the principle approach having multiple thresholds. On the y-axis the normalized SLA value is defined while on x-axis the time is shown. Dependent on the slice specific SLA the thresholds311,312,321,322,331,332are set to define more or less critical regions until the SLA is violated316. For instance slice one131has a very relaxed situation regarding a possible SLA violation316. In the first time period the SLA metric301exceeds the first defined threshold311. When the first threshold311is exceeded a slightly higher prioritization to allocate radio resources for slice1is derived. Therefore a dynamic weight is set to ease the situation again. For slice one it was possible to influence the scheduling metric positive by slightly higher prioritization in all 3 cases where the first threshold311was exceeded. The behavior of the SLA metric302regarding slice2behaves a bit different and might be dependent on the scheduling decision taken for slice1. A slightly increasing prioritization in the first step didn't have a positive influence and could not prevent the SLA metric302exceeding the second threshold322, as well. After further increasing the priority more aggressively the situation relaxes slightly until the metric302falls sharply below the Nth threshold332. The prioritization is then heavily increased to prevent an SLA violation316by all means. It can be observed, during the time period the SLA metric302of slice2is in the critical region of the Nth threshold332, the SLA metric301of slice1slightly decreased because of interdependencies of the scheduling decision. As indicated on the right side ofFIG. 3slice2allocates more and more of the system bandwidth due to higher prioritization. After aggressively prioritizing the traffic of slice2for a while, a positive influence can be observed, while the metric302recovers until the second threshold322is reached. Then the prioritization of slice2is decreased again. Even with the decreased prioritization ongoing recovery is observed when the metric302rises in the direction of the first threshold312again. It is worth mentioning that the derived weights to prioritize the slices based on the individual metric is dependent on the status of the other slices which are operated within the system and share physical radio resources.

In the following, another exemplary implementation of multi threshold based SLA monitoring300is described. In this implementation, referred to as Example 2, Slice1is orchestrated for ultra-reliable communication services and Slice2is orchestrated for broadband everywhere. In this implementation, the following SLAs are defined:

For Slice1: 99.999% of all data flows need to be successfully transmitted; and a single data flow needs to have a maximum packet delay of 10 ms within 95% of the cases.

For Slice2: Guaranteed bit rate of 50 Mbps everywhere in 97.5% of the cases; and a single data flow has a maximum packet delay of 50 ms within 90% of the cases.

One data flow per slice is currently active and is routed based on e.g. IPv6 to the same mobile access entity (e.g. eNodeB). Each data flow has a certain Quality channel indicator (QCI) class marked within the IPv6 header extension field (In general 8 byte available): Data flow A (of slice1) has non-GBR with max delay of 10 ms; Data flow B (of slice2) has GBR with max delay of 50 ms.

SLA monitoring entity adds, e.g., two additional information to the IPv6 header: 1) SLA indicator to let the access node know which SLA has to be fulfilled; 2) SLA status indicators to let the access node know if SLA might be violated.

The SLA status indicators can be deltas to the defined thresholds, which indicate the degree of freedom of how to handle the data flow due to the SLA and its current instantaneous status. The smaller the delta of the SLA status indicator, the higher will be the weighting factor of the considered data flow.

Based on the additional information about the SLA (status) the access nodes' (eNodeB) radio scheduler can adapt dynamically the weighting factors to prioritize the transmission of each data flow. Influencing factors are: 1) The QCI classes of the data flow; 2) e.g. the delta of the instantaneous status of the KPIs of the SLAs of the network slices compared to the SLA.

Requirements to the scheduler of data flow A are for Alternative1: Transmission would use a lower Modulation and Coding Scheme (MCS) to make sure to be successful in transmission and avoid retransmission which result in higher latency, this results in a lower spectral efficiency so more radio resources are used “unefficent” but robust. Requirements are for Alternative2: In case of dual or multi connectivity redundant transmission over more than one access node. Requirements to the scheduler of data flow B are: Transmission needs a lot of resources because 50 Mbps everywhere is guaranteed (especially at cell edge where only low MCS might be useful).

In the following reference is made to an LTE like radio frame where the radio scheduler can allocate radio resources on TTI (1 ms) level. Usually the scheduler would serve data flow B at first because of the GBR QCI class. Due to the unpredictable upcoming traffic situation GBR needs to be fulfilled as fast as possible. However Data Flow A needs to be transmitted successful with a probability of 99.999%. Based on this very challenging SLA requirement the radio scheduler needs to change the priority which data to map on the physical resources to transmit.

The following can be summarized: QCI of data flow B results in higher weight for data flow B than for data flow A. But slice specific SLA status gives extra information which will result in a contradicting weight in the end. Worst case: Data flow B is discarded or not immediately scheduled (may be slice status gives information that in 99% of the cases it was successful and can be discarded) due to data flow A (flow of the uMTC slice A) which cannot be discarded at all (99.999%). In critical cases in front of an SLA violation the SLA can already be influenced by Admission Control (AC) and Allocation and Retention Priority (ARP). After scheduling decision is taken and applied the radio scheduler feeds back what happened based on QCI KPIs (data rate, BER, latency). Then the SLA metric are updated by mapping QCI specific KPIs the SLA metric.

FIG. 4shows a message sequence diagram400illustrating messaging between the entities of a radio communication network according to the disclosure, e.g. a radio communication network100or200as described above with respect toFIGS. 1 and 2. A possible function split between an orchestrator401that may correspond to the orchestrator205depicted inFIG. 2or the network orchestration entity130depicted inFIG. 1, a QoS/SLA monitoring entity402that may correspond to the SLA/QoS monitor203depicted inFIG. 2or to the monitoring entity120depicted inFIG. 1, a software controller403that may correspond to the software controller201depicted inFIG. 2or to the controller110depicted inFIG. 1, a lower MAC scheduler404that may correspond to a respective radio scheduler214,215,216,217,218,219depicted inFIG. 2or to the radio scheduler140depicted inFIG. 1and a UE405, e.g. a mobile device communicating in the radio communication networks100or200ofFIGS. 1 and 2is shown inFIG. 4. The radio scheduling functions may be implemented at a lower MAC layer which gets information from PHY layer.

The messages as described in the following are examples, other implementations are possible as well. In the example ofFIG. 4, the orchestrator401transmits a “Service (QoS/SLA) policies of NS” message410to QoS/SLA monitoring entity402that answers with an “Ack or Nack” message411. Then, the orchestrator401transmits a “Service (QoS/SLA) policies of NS” message412to software controller403that answers with an “Ack or Nack” message413. Then, the orchestrator401transmits a “vNF to node mapping table” message414to software controller403that answers with an “Ack or Nack” message415. This “vNF to node mapping table” message414may indicate a virtual node function mapping as determined by the Orchestrator401to the software controller403.

The software controller403transmits a “Radio resource scheduling decision” message416to the lower MAC scheduler404to indicate a scheduling of radio resources to lower MAC scheduler404that answers with an “Ack or Nack” message417. Then, the lower MAC scheduler404transmits a “scheduling grant” message418to the UE405to grant the UE405the scheduling of radio resources. The UE405answers with an “HARQ Ack or Nack” message419. Then, the lower MAC scheduler404transmits an “Ack/Nack” message420to the software controller403and transmits a “Flow based QoS information” message421to the QoS/SLA monitoring entity402to indicate monitored quality of service information and/or monitored SLA to the QoS/SLA monitoring entity402upon which message421the QoS/SLA monitoring entity402answers with a “QoS/SLA status indicator” message422to indicate the status of QoS/SLA monitoring to the software controller403. This status may indicate for example a threshold violation316as depicted inFIG. 3or an event that the SLA metrics301,302for first slice131and second slice132and other slices fall below one of the thresholds311,312,321,322,331,332as described above with respect toFIG. 3. Based on the received information, e.g. the status information and/or the data measured by the monitoring entity402, the software controller403detects440a first QoS/SLA threshold violation (1.), e.g. a threshold violation316as depicted inFIG. 3; the software controller403sets dynamic weights (2.) or more general speaking, adjusts the scheduling strategy142as described above with respect toFIG. 1; and determines a radio resource scheduling decision (3.). Based on this decision, a “radio resource scheduling decision” message423is sent to the lower MAC scheduler404to inform the lower MAC scheduler404about this decision. The lower MAC scheduler404forwards a “Scheduling grant” message424to the UE405to grant the new scheduling decision to the UE. The UE405answers with a “HARQ Ack/Nack” message425.

The lower MAC scheduler404transmits a “Flow based QoS information” message426to the QoS/SLA monitoring entity402to indicate monitored quality of service information and/or monitored SLA to the QoS/SLA monitoring entity402upon which message426the QoS/SLA monitoring entity402answers to the software controller403with a “QoS/SLA status indicator” message427to indicate the status of QoS/SLA monitoring to the software controller403as described above.

Based on the received information, e.g. the status information and/or the data measured by the monitoring entity402, the software controller403detects441a further, e.g. an nth QoS/SLA threshold violation (1.), e.g. a threshold violation316as depicted inFIG. 3; the software controller403switches the scheduling strategy (2.), e.g. at eNB and/or cluster as described above with respect toFIG. 2, based on service chain templates and determines a radio resource scheduling decision. Based on this decision, a “radio resource scheduling decision” message428is sent to the lower MAC scheduler404which forwards a “Scheduling grant” message429to the UE405. The UE405answers with a “HARQ Ack/Nack” message430, as described above.

The lower MAC scheduler404transmits a “Flow based QoS information” message431to the QoS/SLA monitoring entity402to indicate monitored quality of service information and/or monitored SLA to the QoS/SLA monitoring entity402upon which message431the QoS/SLA monitoring entity402answers to the software controller403with a “QoS/SLA status indicator” message432to indicate the status of QoS/SLA monitoring to the software controller403as described above.

Based on the received information, e.g. the status information and/or the data measured by the monitoring entity402, the software controller403detects442a further, e.g. an mth QoS/SLA threshold violation (1.), e.g. a threshold violation316as depicted inFIG. 3. In this example after the mth QoS/SLA threshold violation, an escalation of the threshold violation is indicated to the Orchestrator401by a “Scheduler modification request” message433that is sent to the orchestrator401to indicate the orchestrator401a requirement for changing or modifying the scheduling. Upon this message433the orchestrator401chooses a different service function chain template (1.) and performs reorchestration (2.) by switching the scheduling strategy434.

The message sequence diagram400represents a possible implementation of a method for scheduling radio resources in a radio communication network as described above with respect toFIG. 1.

FIG. 5shows a schematic diagram illustrating an exemplary 5G system architecture500which radio resources can be scheduled by a radio scheduler according to the disclosure.

The 5G system architecture500includes an area with 5G communication terminals501which are connected via different access technologies502to a multilayered communication structure. This multilayered communication structure includes an Infrastructure & Resources layer505, an activation layer504and an application layer503which are managed by a management & Instrumentation plane506.

The Infrastructure & Resources layer505includes the physical resources of a converged network structure of fixed and mobile network components (“Fixed-Mobile Convergence”) with access point, cloud nodes (consisting of processing and storage node), 5G devices such as mobile phones, portable devices, CPEs, machine communication modules and other network nodes and related links. 5G devices can include multiple and configurable capabilities and act, for example, as a relay or hub or can operate depending on the particular context as a computer or memory resource. These resources are provided to the higher layers504,503and the management & Instrumentation layer506via corresponding APIs (application program interfaces). Monitoring the performance and the configurations are inherent to such APIs.

The activation layer504includes a library of functions that are needed within a converged network in the form of blocks of a modular architecture. These include functions that are implemented in software modules that can be retrieved from a storage location of the desired location, and a set of configuration parameters for specific parts of the network, for example, the radio access. These features and capabilities can be accessed on demand by the management & Instrumentation layer506by using the provided APIs. Certain functions may exist in multiple variants, for example, different implementations of the same functionality having different performance or characteristic.

The application layer503includes specific applications and services of the network operator, the company, the vertical operator or by third parties who use the 5G network. The interface to the management & Instrumentation layer506allows to use certain dedicated network slices for an application, or to assign an application to an existing network slice.

The management & Instrumentation layer506is the contact point for the required use cases (use cases, business models) to put into actual network functions and slices. It defines the network slices for a given application scenario, concatenates the relevant modular network functions, assigns the relevant performance configurations and maps all to the resources of the infrastructure & resources layer505. The management & Instrumentation layer506also manages the scaling of the capacity of these functions as well as their geographical distribution. In certain applications, the management & Instrumentation layer506may also have skills that allow third parties to produce and manage their own network slices by the use of APIs. Because of the numerous tasks of the management & Instrumentation layer506, these are not a monolithic block of functionality but rather a collection of modular functions, integrating progresses that have been achieved in different network domains, such as NFV (network function virtualization), SDN (software-defined networking) or SON (self-organizing networks). The management & Instrumentation Layer506utilizes data assisted intelligence to optimize all aspects of service assembly and deployment.

The radio scheduler140described above with respect toFIG. 1may be used to schedule radio and/or network resources of the communication network500. The radio scheduler140may be a part of the network500, e.g. as shown inFIG. 2or may be arranged outside the network500, e.g. as shown inFIG. 1. The radio scheduler140may for example be implemented in the activation layer504, e.g. as a virtual network function622in a network slice or alternatively located at the management & Instrumentation level506. Alternatively, each network slice or slice instance may include a radio scheduler140. Network entities requesting resources of the communication network500may for example be network nodes of the infrastructure and resources layer505, or network nodes of the activation layer504or network slices or slice instances of the application layer503. Network entities requesting resources of the communication network500may also be mobile devices501, base stations, base station controllers, radio network controllers etc. requesting resources for initiating a communication channel over the communication network500.

The network orchestration entity130depicted inFIG. 1may for example be implemented in the management & Instrumentation layer or level506. The monitoring entity120and the controller110may be implemented for example on the application layer503, e.g. per network slice or as single entities for all network slices. Alternatively, the monitoring entity120and the controller110may be implemented for example in the management & Instrumentation layer or level506.

The 5G network500increases the efficiency of communication and provides in particular a higher data throughput, lower latency, particularly high reliability, a much higher connection density and a larger mobility area. The 5G network500increases the operational flexibility and provides tailored features and functions while saving network resources. This increased performance is accompanied by the ability to control highly heterogeneous environments and the ability to secure trust, identity and privacy of users.

FIG. 6shows a schematic diagram illustrating an exemplary 5G communication network600including a plurality of network slices which radio resources can be scheduled by a radio scheduler according to the disclosure.

The 5G-communication network600includes an infrastructure & resources layer505, an activation layer504and an application layer503, as described above with respect toFIG. 5.

The Infrastructure & Resources layer505includes all physical assets that are associated with a network operator, i.e., locations, cable, network nodes, etc. This layer505forms the basis for all network slices. It is structured as generic as possible without too many specialized engineering units. The Infrastructure & Resources layer505conceals any kind of user-specific implementation towards the upper layers, so that the remaining systems can be used optimally for different slices. Components of the infrastructure and resources layer505are based on hardware and software or firmware that is needed for each operation and that is provided to the overlying layers as resource objects. Objects of infrastructure & resources layer505, for example, include virtual machines, virtual links or connections and virtual networks, for example, virtual access node631,632,633, virtual network nodes634,635,636,637and virtual computer nodes638,639,640. As the term “virtual” implies, the infrastructure and resources layer505provides the objects in the form of an “infrastructure as a service”651, i.e. in an abstracted, virtualized form to the next higher layer504.

The activation layer504is arranged above the infrastructure & resources layer505. It uses the objects of the infrastructure & resources layer505and adds additional functionality to these objects, for example in the form of (non-physical) software objects/VNFs (virtual network functions) to enable generation of any type of network slices and hence to provide a platform as a service to the next higher layer503.

Software objects can exist in any granularity, and may include a tiny or a very large fragment of a network slice. In order to be able to allow the generation of network slices on a suitable level of abstraction in the activation layer504different abstract objects621can be combined with other abstracted objects and virtual network functions622to form combined objects623, which can be converted into aggregated objects624which can be provided in an object library625to the next higher level. Thus, the complexity can be hidden behind the network slices. For example, a user can create a mobile broadband slice and define merely a KPI (Key Performance Indicator) without having to specify specific features such as individual local antenna cover, backhaul links and specific parameterization degrees. Supporting an open environment, allowing to add or delete network functions on demand, is an important skill of the activation layer504that supports the dynamic rearrangement of functions and connectivities in a network slice, for example, by using SFC (Service Function Chaining) or modifying software so that the functionality of a slice can be completely pre-defined and can include both approximately static software modules and dynamically adaptable software modules.

A network Slice can be regarded as software-defined entity that is based on a set of objects that define a complete network. The activation layer504includes all software objects that are necessary to provide the network slices and the appropriate skills to handle the objects. The activation layer504may be considered as a type of network operating system complemented by a network production environment. An important task of the activation layer504is defining the appropriate levels of abstraction. So network operators have sufficient freedom to design their network slices while the platform operator can still keep maintaining and optimizing the physical nodes. For example, the execution of everyday tasks such as adding or replacing NodeBs, etc. is supported without the intervention of the network client. The definition of suitable objects that model a complete telecommunications network, is one of the essential tasks of the activation layer504in developing the network slices environment.

A network slice, also known as 5G Slice, supports communication services of a certain type of connection with a particular type of handling of the C (Control) and U (User Data) layer. A 5G slice is composed of a collection of different 5G network functions and specific radio access technology (RAT) settings that are combined together for the benefit of the specific use case. Therefore, a 5G Slice spans all domains of the network, for example, software modules that run on a cloud node, specific configurations of the transport network that support a flexible location of functions, a particular radio configuration or even a particular access technology as well as a configuration of 5G devices. Not all slices contain the same features, some features that today seem to be essential for a mobile network can even not occur in some slices. The intention of the 5G Slice is to provide only the functions that are necessary for the specific use case and to avoid any other unnecessary functionalities. This flexibility provides for the widening of existing applications as well as for creating new applications. Third party devices can thus be granted permission to control certain aspects of slicing through appropriate APIs to provide such customized services.

The application layer503includes all generated network Slices610b,611b,612band offers these as “network as a service” to different network users, for example, different customers. This allows for the reuse of defined network slices610b,611b,612bfor different users, for example as a new network instance610a,611a,612a. A network slice610b,611b,612b, which is associated, for example, with an automotive application can also be used for applications in various other industrial applications. The slices instances610a,611a,612a, generated by a first user, can for example be independent of the slices instances that were generated by a second user, although the entire network slice functionality may be the same.

By using the radio scheduler described above with respect toFIGS. 1 and 2, radio resources of the communication network600can be scheduled. The radio scheduler105may be a part of the network600or may be arranged outside the network600, for example in a foreign network. The radio scheduler140may for example be located in a network slice610bor slice instance610a. Network entities requesting resources of the communication network600may for example be network nodes of the infrastructure and resources layer505, or network nodes of the activation layer504or network slices or slice instances of the application layer503. Network entities requesting resources of the communication network600may also be mobile devices, base stations, base station controllers, radio network controllers etc. requesting resources for initiating a communication channel over the communication network. The network slices610b,611b,612band/or slice instances610a,611a,612amay form the logical networks131,132,133described above with respect toFIG. 1.

The methods, systems and devices described herein may be implemented as electrical and/or optical circuit within a chip or an integrated circuit or an application specific integrated circuit (ASIC). The invention can be implemented in digital and/or analogue electronic and optical circuitry.

The methods, systems and devices described herein may be implemented as software in a Digital Signal Processor (DSP), in a micro-controller or in any other side-processor or as hardware circuit within an application specific integrated circuit (ASIC) of a Digital Signal Processor (DSP).

The invention can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations thereof, e.g. in available hardware of conventional optical transceiver devices or in new hardware dedicated for processing the methods described herein.

The present disclosure also supports a computer program product including computer executable code or computer executable instructions that, when executed, causes at least one computer to execute the performing and computing steps described herein, in particular the method described above with respect toFIG. 1, the method400as described above with respect toFIG. 4and the techniques described above with respect toFIGS. 1 to 6. Such a computer program product may include a readable non-transitory storage medium storing program code thereon for use by a computer. The program code may perform the methods as described above with respect toFIGS. 1 to 6.

While a particular feature or aspect of the disclosure may have been disclosed with respect to only one of several implementations, such feature or aspect may be combined with one or more other features or aspects of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “include”, “have”, “with”, or other variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprise”. Also, the terms “exemplary”, “for example” and “e.g.” are merely meant as an example, rather than the best or optimal. The terms “coupled” and “connected”, along with derivatives may have been used. It should be understood that these terms may have been used to indicate that two elements cooperate or interact with each other regardless whether they are in direct physical or electrical contact, or they are not in direct contact with each other.