Patent Description:
In Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), if user equipment (UE) requests a service either visible or not visible from the perspective of an end user, the UE typically has to initiate a random access procedure and then a Radio Resource Control (RRC) connection setup procedure, followed with a UE-associated logical S1 connection establishment procedure. In the case that the service is visible and initiated by the end user, a default E-UTRAN Radio Access Bearer (E-RAB) setup procedure is further triggered upon the establishment of the UE-associated logical S1 connection.

After these procedures are successful, the UE would be provided with the service. However, quality of the provided services may differ from cell to cell. The quality of the provided services means how good or bad the end user perceives the provided services, which depends on a lot of factors. For example, considering there is an overlapping between two cells and the UE may in principle camp in both of the two cells currently, there is no information communicated to the UE that would indicate which cell is better one in terms of Quality of Service (QoS) when the UE is in a RRC Idle state. Thus, if the UE entered a worse cell and got a requested service in the cell, worse quality even a service drop may be caused. <CIT> has disclosed barring the access of the terminal to the network based on a control parameter previously received from the network. <CIT> has disclosed a method by which a central unit of a base station updates access control barring related parameters in a wireless communication system.

In general, example embodiments of the present disclosure provide a network device, method and computer readable storage medium for access control barring (ACB) based on cell quality.

In a first aspect, a network device is provided. The device comprises means for determining a set of metrics, each metric being related to quality of service, QoS, performance for a plurality of services in a cell in a measurement period; and means for determining access control barring, ACB, configuration in the cell based on comparison of the set of metrics with a set of thresholds; wherein the measurement period comprises a plurality of time intervals, and the means for determining the set of metrics is further configured for : determining at least a subset of metrics in the set of metrics at the end of a time interval of the plurality of time intervals; and comparing at least the subset of metrics with thresholds associated with at least the subset of metrics in the set of thresholds; wherein the means for determining the ACB configuration is further configured for: determining, based on the comparison of the at least one subset of metrics and the associated thresholds, whether requested QoS is achieved in the cell in the time interval; in response to determining that the requested QoS is unachieved, counting the time interval into a time period in which the requested QoS is unachieved in the cell; and determining the ACB configuration based on the time period.

In a second aspect, a method is provided. In the method, a network device determines a set of metrics, each metric being related to QoS performance for a plurality of services in a cell in a measurement period. The network device determines ACB configuration in the cell based on comparison of the set of metrics with a set of thresholds. Wherein the measurement period comprises a plurality of time intervals, and determining the set of metrics comprises: determining at least a subset of metrics in the set of metrics at the end of a time interval of the plurality of time intervals; and comparing at least the subset of metrics with thresholds associated with at least the subset of metrics in the set of thresholds; wherein determining the ACB configuration comprises: determining, based on the comparison of the at least one subset of metrics and the associated thresholds, whether requested QoS is achieved in the cell in the time interval; in response to determining that the requested QoS is unachieved, counting the time interval into a time period in which the requested QoS is unachieved in the cell; and determining the ACB configuration based on the time period.

In a third aspect, there is provided a computer readable storage medium comprising program instructions stored thereon. The instructions, when executed by a processor of a network device, cause the network device to perform the method according to the second aspect.

It is to be understood that the summary section is not intended to identify key or essential features of example embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure.

It is to be understood that these example embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure.

As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wireless communications with each other or with the network device. The communications may involve transmitting and/or receiving wireless signals using electromagnetic signals, radio waves, infrared signals, and/or other types of signals suitable for conveying information over air. In some example embodiments, the UE may be configured to transmit and/or receive information without direct human interaction. For example, the UE may transmit information to the network device on predetermined schedules, when triggered by an internal or external event, or in response to requests from the network side.

Examples of the UE include, but are not limited to, smart phones, wireless-enabled tablet computers, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), wireless customer-premises equipment (CPE), sensors, metering devices, personal wearables such as watches, and/or vehicles that are capable of communication. For the purpose of discussion, some example embodiments will be described with reference to UEs as examples of the terminal devices, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of the present disclosure.

As used herein, the term "network device" refers to a network device via which services can be provided to a terminal device in a communication network. The network device may comprise any suitable device via which a terminal device or UE can access the communication network. Examples of the network devices include a relay, an access point (AP), a transmission point (TRP), a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a New Radio (NR) NodeB (gNB), a Remote Radio Module (RRU), a radio header (RH), a remote radio head (RRH), a low power node such as a femto, a pico, and the like.

As used herein, the term "cell" refers to an area covered and served by a network device in which the network device can provide services. One network device may serve one or more cells. Difference cells may or may not use the same frequency resources such as sub-carriers.

As used herein, the terms "first", "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. For example, a first element could be referred to as a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.

As described above, if the UE requests a service, the UE typically will not obtain data related to the requested service until several procedures are successful. Even if these procedures are successful, the quality of the provided service may be worse, or even the service may be dropped. For example, in the scenario that the UE camp in both of the two overlapping cells currently, there is no information that would indicate to the UE in the RRC Idle state which cell is better one in terms of QoS, or would restrict the UE for network access to the cell.

Nowadays, a cell can utilize a control process, which is called "Access Control", to control (or limit) the amount of access from UEs to prevent overload of an access channel under critical conditions. There are several different approaches for Access Control. One mechanism of these approaches is to accept an initial request from a UE but send a Reject message to the UE at a network side. This mechanism may be performed with a RRC Connection Reject message in a RRC layer or an Attach Reject message in a non-access stratum (NAS) layer.

Another mechanism for Access Control is to prevent a UE from attempt of the initial request. Two typical application cases of this mechanism are as follows: one case is to bar every UE from any type of access even for an emergency call, and the other case is to bar only a specific UE from a specific service, for example, with specific marking in UMTS Subscriber Identity Module (USIM). This mechanism may be performed with various system information block (SIB) settings. For example, the barring of all UEs from any type of access may be configured by SIBI, and the barring of the specific UE from the specific service may be configured by SIB2. Moreover, many implementations of this mechanism have evolved as cellular technology evolves.

The inventor finds that an overload situation of a cell may be separated from other conditions that may lead to insufficient QoS. For example, after a UE is allowed for network access, QoS for the UE may be degraded due to some reasons. This may cause a dropped session, a big delay of packet data convergence protocol (PDCP) service data units (SDUs), low scheduled International Protocol (IP) throughput, and the like. In a case, when the UE has a guaranteed bit rate (GBR) service ongoing, radio conditions may become bad in a cell. Thus, despite there is no radio link failure (RLF) detected for the UE, the UE may be abnormally released because QoS requirements for the UE such as throughput and delay cannot be achieved. In another case, the UE may have a non-GBR service ongoing. In this case, if a RLF has been detected, a UE may also be abnormally released.

In both the above cases, although an eNB try to provide requested QoS to the UEs in the cell, for example, the eNB may employ very robust techniques, such as the most robust modulation coding schemes (MCSs) and thus maximum possible resources, the maximum UE transmit power and other possible techniques such as handover (HO), redirection and the like, it may be not possible to keep the UEs active in the cell with the requested QoS simply because there is no needed capacity in the cell.

Each of the cases can be thus seen as an overload situation of a cell in which there is not enough capacity to keep the UE active in the cell with requested QoS. Currently, there is no consideration of associating a QoS issue with an overload issue, and thus there is no access control related to provided QoS.

Example embodiments of the present disclosure provide a novel access class barring (ACB) mechanism. This ACB mechanism configures ACB based on QoS performance in a cell. The QoS performance may be indicated by related metrics. The metrics may reflect any QoS characteristics such as throughput, latency and the like. For example, if QoS requirement of end users is evaluated, by using the metrics related to the QoS performance, to be unsatisfied even when relatively robust transmission schemes such as the most robust MCSs, the maximum possible resources, the maximum UE transmit power and the like have been utilized in a cell, UEs may be barred from access to the cell.

This ACB mechanism transforms a cell quality issue to an overload issue of the access channel. Accordingly, the ACB configuration may be based on the cell quality in a cell. For example, it may be configured when ACB will activated and which ACB parameters will be used. This ACB mechanism may ensure the cell quality and thus may be more effective and efficient. Accordingly, system performance and efficiency may be improved.

<FIG> shows an example environment <NUM> in which example embodiments of the present disclosure can be implemented. The environment <NUM>, which may be a part of a communication network, comprises a network device <NUM> serving a cell <NUM>. Three terminal devices <NUM>-<NUM>, <NUM>-<NUM>,. , <NUM>-N (N represents a positive integer), collectively referred to as terminal devices <NUM>, are located in the cell <NUM>. Accordingly, the network device <NUM> can provide various services to the terminal devices <NUM> in the cell <NUM>.

It is to be understood that one network device and three terminal devices are shown in the environment <NUM> only for the purpose of illustration, without suggesting any limitation to the scope of the present disclosure. Any suitable number of network devices may be deployed in the environment <NUM>. One network device may serve one or more cells, and any suitable number of terminal devices may be located in one cell.

It is also to be understood that the environment <NUM> may comprise other network parts and network entities or functionalities (not shown). As an example, the environment <NUM> may include a network entity in a core network such as evolved packet core (EPC) or the fifth generation (<NUM>) core.

The terminal device <NUM>-<NUM> can communicate with the network device <NUM> or with another terminal device <NUM>-<NUM> or <NUM>-<NUM> directly or indirectly via the network device <NUM>. The communication may follow any suitable communication standards or protocols, which are already in existence or to be developed in the future, such as E-UTRAN, Universal Mobile Telecommunications System (UMTS), long term evolution (LTE), LTE-Advanced (LTE-A), the fifth generation (<NUM>) New Radio (NR), Wireless Fidelity (Wi-Fi) and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employs any suitable communication technologies, including, for example, Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), time division multiplexing (TDM), frequency division multiplexing (FDM), code division multiplexing (CDM), Bluetooth, ZigBee, and machine type communication (MTC), enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable low latency communication (URLLC), Carrier Aggregation (CA), Dual Connection (DC), and New Radio Unlicensed (NR-U) technologies.

In the environment <NUM>, the network device <NUM> may activate ACB by broadcasting via SIB to bar terminal devices (for example, in a RRC Idle State) from access to the cell <NUM>. The activation of ACB may be triggered due to no overload of an access channel under critical conditions as defined in the 3rd Generation Partnership Project (3GPP) specifications (for example, 3GPP TS <NUM>). In some cases, there may be no overload of the access channel, but there is cell critical conditions due to lack of features and functionalities to keep the terminal devices <NUM> active in the cell <NUM> with guaranteed or requested QoS. In various example embodiments of the present disclosure, the cell overload under the cell critical conditions is mapped to the QoS performance issue. This cell overload may also trigger the activation of ACB in the cell <NUM> to restrict terminal devices for access to the cell <NUM>.

<FIG> shows a flowchart of an example method <NUM> according to some example embodiments of the present disclosure. The method <NUM> can be implemented by the network device <NUM> as shown in <FIG>. For the purpose of discussion, the method <NUM> will be described with reference to <FIG>.

At block <NUM>, the network device <NUM> determines a set of metrics related to QoS performance for a plurality of services in the cell <NUM> in a measurement period. In some example embodiments, the QoS performance may be overall QoS performance for all the services to obtain more general statistics for the cell <NUM>. The more general statistics may represent QoS characteristics in the whole cell <NUM> by taking all active terminal devices <NUM> into account. In general, the critical conditions for both the access channel and cell overloads may be related to just limited number of terminal devices in a cell. The remaining terminal devices may be provided with needed QoS. The more general statistics may be more effective and efficient for a network optimization.

The metrics related to the QoS performance may reflect any QoS characteristics such as throughput and latency in the cell <NUM>. In some example embodiments, the metrics may comprise values of Key Performance Indicators (KPIs) as defined in the 3GPP specifications (for example, 3GPP TS <NUM>). It is possible that the metrics are related to other performance indication or indications that is already existed or to be developed in the future.

The measurement period for determining the metrics may be defined based on performance management (PM) counters as defined in the 3GPP specifications (for example, 3GPP TS <NUM>). Alternatively, the measurement period may be set or configured by the network device <NUM> or another network entity or even a network operator according to operational requirements.

In some embodiments, the measurement period is split into a plurality of time intervals (in a unit of ms, for example). The determination of the metrics is implemented on a time interval basis. For example, at end of one of the time intervals, at least a subset of the metrics is determined to evaluate the QoS performance in the time interval. In some example embodiments, the metrics may be detected or monitored in the whole time interval. In some other example embodiments, the metrics may be monitored and averaged in a longer observation interval such as hours. At the end of a time interval included in the measure period, the snapshot of the metrics is taken by the network device <NUM>, or taken and reported to the network device <NUM> by other devices such as the terminal device <NUM> or other network entities or functionalities. With this average in the longer observation interval, more general statistics on the QoS performance may be obtained.

The services may be of any suitable type depending on network deployment and end user's need, which may include voice, data, video and the like. These services may be in different QoS levels. Different QoS levels represents different QoS requirement. A QoS level may refer to a QoS Class Identifier (QCI) in E-UTRAN or QoS Flow Identifier (QFI) in <NUM> NR.

In some example embodiments, the determination of the QoS performance in the cell <NUM> may be performed per QoS level. In some embodiments, the set of metrics may comprise a plurality of subsets of metrics, and each subset of metrics is associated with one of the QoS levels. For example, KPIs per QCI in E-UTRAN may include E-RAB retainability per QCI, scheduled IP throughput per QCI and IP latency per QCI. In the embodiments where the metrics comprise values of KPIs and a QoS level is a QCI in E-UTRAN, E-RAB retainability per QCI, scheduled International Protocol (IP) throughput per QCI and IP latency per QCI may be detected or monitored as the metrics of the QoS performance in the cell <NUM>.

In some example embodiments, the time intervals included in the measurement period may be associated with different QoS levels. In these embodiments, a subset of metrics may be determined at the end of the corresponding time interval based on the QoS level associated with both the metrics and time interval.

After the set of metrics is determined, at block <NUM>, the network device <NUM> determines ACB configuration in the cell <NUM> based on comparison of the set of metrics with a set of thresholds. The thresholds may be set or configured at a network side. For example, the metrics may be compared with the associated thresholds at the end of the measurement period. If the metrics are configured per QoS level, the thresholds may also be set or configured per QoS level.

Based on the comparison of the metrics and the thresholds, the network device <NUM> may determine whether ACB is to be activated in the cell <NUM>. For example, if it is determined that requested QoS is not achieved in the cell <NUM>, the network device <NUM> may determine that ACB is to be activated. In some example embodiments, the achievement of the requested QoS may be determined based on the number of metrics that are degraded compared with the associated thresholds. In the case that the metrics are associated with different QoS levels, the achievement of the requested QoS may be determined further based on impacted QoS levels.

If the ACB is to be activated, the network device <NUM> may additionally determine or configure ACB parameters such as ac-BarringFactor and timers according to the 3GPP specifications (for example, 3GPP TS <NUM>). The configuration of the ACB parameters may depend on in which area degradation has been observed in the cell <NUM>, whether it is retainability, throughput or delay or all of them, and impacted services (or QCIs or QFIs). For example, more significant degradation in all of the areas and for majority of services is observed or detected, more aggressive parameters may be selected or configured.

<FIG> shows a flowchart of an example process <NUM> of ACB configuration based on QoS performance in a cell according to some example embodiments of the present disclosure.

The process <NUM> is an example implementation process of the method <NUM>. In this example, the metrics comprise values of KPIs associated with different QoS levels that are indicated by QCIs in E-UTRAN. It is to be understood that some example embodiments are described in the context of E-UTRAN only for the purpose of illustration, without suggesting any limitation. Embodiments and implementations of the present disclosure are not limitted to E-UTRAN, but applicable using any suitable technology including <NUM>, for example.

As shown, at block <NUM>, the overall QoS performance is monitored for a measurement period in the cell <NUM> via KPIs such as E-RAB drop ratio, scheduled IP throughput, PDCP SDU latency and the like. In this example, the measurement period includes a plurality of time intervals. These KPIs are detected or monitored in the individual time intervals.

At block <NUM>, the KPI values are compared with the associated thresholds in the time intervals. The thresholds are set by a network operator. At block <NUM>, it is determined whether the KPI values are degraded compared to the thresholds. If no, the process <NUM> returns to block <NUM> and starts a new turn of QoS monitoring. If it is determined that there are degraded KPIs at block <NUM>, the process <NUM> proceeds to block <NUM> where based on the number of degraded KPI values and the impacted QCIs, the network device <NUM> starts ACB broadcasting via SIB and sets ACB parameters such as AC-Barring factors and timers.

In some embodiments, the achievement of the requested QoS are determined per time interval. For example, in each of the time intervals within the measurement period, the metrics are determined and compared with the associated thresholds. Based on the comparison, the network device <NUM> determines whether the requested QoS is achieved in the individual time intervals. For example, if the metrics are degraded compared to the associated thresholds, it may be determined that the requested QoS is unachieved. In the embodiments where different time intervals are associated with different QoS levels, the degradation of the metrics may further be determined per QoS level.

The time intervals in which the requested QoS is unachieved are summed up. The summed-up time intervals are considered as a time period in which the requested QoS is unachieved in the measurement period. An example process of determining the time period will be discussed with reference to <FIG>.

<FIG> shows an example message flow <NUM> for determining the time period according to some example embodiments of the present disclosure.

The message flow <NUM> may be implemented in the environment <NUM> as shown in <FIG>. In this example, the terminal device <NUM> is implemented by a UE <NUM>, and the network device <NUM> is implemented by an eNB or gNB <NUM>. The environment <NUM> further includes an EPC or <NUM> Core <NUM>.

As shown, the eNB or gNB <NUM> starts (<NUM>) a measurement period that includes a plurality of time intervals (or internal sampling intervals). The eNB or gNB <NUM> determines (<NUM>) whether a time interval is ended. If the time interval is not ended, the eNB or gNB <NUM> repeatedly determines (<NUM>) whether a next time interval is ended. If the time interval is ended, the snapshot of QoS KPIs is taken (<NUM>). The KPIs may include UE throughput, PDCP SDU delay, PDCP SDU loss rate, retainality and the like. The QoS KPIs may be provided as average from a longer observation interval such as hours. The snapshot is taken at the end of a time interval within the measurement period. The snapshot may be taken by any suitable devices such as the UE <NUM>, the eNB or gNB <NUM> or the EPC or <NUM> Core <NUM>.

The eNB or gNB <NUM> determines (<NUM>) whether a KPI is degraded compared to an associated threshold configured by the network operator, for example. The threshold may be configured per QCI or QFI if needed. If no KPI is degraded, the eNB or gNB <NUM> repeatedly determines (<NUM>) whether a next time interval is ended. If the KPI is degraded, the current time interval is counted (<NUM>) into the time period in which the requested QoS is unachieved. Then, the eNB or gNB <NUM> determines (<NUM>) whether the measurement period is ended. If the measurement period is not ended, the eNB or gNB <NUM> determines (<NUM>) again whether a next time interval within the measurement period is ended. If the measurement period is ended, the eNB or gNB <NUM> determines (<NUM>) that the requested QoS cannot be achieved in the cell <NUM> in the first period. The counter is reset (<NUM>), and the flow <NUM> ends (<NUM>).

Based on the time period, the ACB configuration may be determined in the cell <NUM>. For example, based on a length of the time period, it may be determined whether ACB is to be activated in the cell in a time period subsequent to the measurement period. This time period may be a whole measurement period next to the current measurement period or just a part of the next measurement period. It may also be possible that the time period may comprise more than one subsequent measurement period. The length of the time period for activation of ACB in the cell may be determined according to actual needs.

The ACB mechanism according to example embodiments of the present disclosure is acting as a filter for barring some of UEs for network access to a given cell if the number of UEs that cannot be kept alive with guaranteed or requested QoS is being increased. For example, at the beginning when only a slight degrade of the QoS performance is monitored via KPIs (for example, in 3GPP TS <NUM>), relatively non-aggressive ACB parameters as defined according to 3GPP TS <NUM> may be selected or configured. As the significant degradation is observed, the ACB parameters may be set to be more aggressive.

The ACB procedures in the cell <NUM> may follow any designs that is existed or to be developed in the future, for example as defined in the 3GPP specifications such as 3GPP TS <NUM>. All the options for ACB as defined in the 3GPP specifications may be re-used herein.

In some example embodiments, the network device <NUM> may determine the ACB configuration based on overlapping of the cell <NUM> with one or more neighboring cells (not shown) and the QoS performance of the neighboring cells. The overlapping may be indicated by an overlapping factor related to an overlapping area between the cells. According to network deployment, the network device <NUM> may know how an area of the cell <NUM> is covered by the neighboring cells. If the neighboring cells are served by the network device <NUM>, the network device <NUM> may detect or monitor the QoS performance in the cells. If the overlapping cells belong to different network devices, the QoS related information exchange between the overlapping cells can be implemented via an X2 interface between the network devices using a principle similar to overload information exchange.

If the requested QoS of the terminal devices <NUM> are not satisfied or achieved in the cell <NUM>, other terminal devices, for example, in a RRC Idle state are barred from access to this cell <NUM>. One or more ACB parameters such as ac-BarringFactors and timers as defined in 3GPP TS <NUM> may be set based on the ovelaping factors and QoS performance of the neighboring cells. For example, if the neighboring cells cover majority of the area of the cell <NUM> and have excellent QoS, more aggressive ACB parameters may be used in the cell <NUM> because the bared terminal devices <NUM> will be handled by the neighboring cells with excellent QoS.

In some example embodiments, the following use case may be added into 3GPP TS <NUM>:.

It is possible that the metrics or measurements are monitored or used by a network operator outside of the network device <NUM> such as an eNB, a gNB or a cell for optimization, for example. The related use case may be specified or defined in the 3GPP specifications.

In some example embodiments, the following new measurement may be added into the 3GPP TS <NUM>:.

In some example embodiments, new measurement in 3GPP TS <NUM> may be defined as follows:.

<FIG> is a simplified block diagram of a device <NUM> that is suitable for implementing example embodiments of the present disclosure. The device <NUM> can be implemented at or as a part of the network device <NUM> as shown in <FIG>.

As shown, the device <NUM> includes a processor <NUM>, a memory <NUM> coupled to the processor <NUM>, a communication module <NUM> coupled to the processor <NUM>, and a communication interface (not shown) coupled to the communication module <NUM>. The memory <NUM> stores at least a program <NUM>. The communication module <NUM> is for bidirectional communications, for example, via multiple antennas. The communication interface may represent any interface that is necessary for communication.

The program <NUM> is assumed to include program instructions that, when executed by the associated processor <NUM>, enable the device <NUM> to operate in accordance with the example embodiments of the present disclosure, as discussed herein with reference to <FIG>. The example embodiments herein may be implemented by computer software executable by the processor <NUM> of the device <NUM>, or by hardware, or by a combination of software and hardware. The processor <NUM> may be configured to implement various example embodiments of the present disclosure, for example, any of the method <NUM>, the process <NUM> and the flow <NUM>.

The memory <NUM> may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory <NUM> is shown in the device <NUM>, there may be several physically distinct memory modules in the device <NUM>. The processor <NUM> may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.

When the device <NUM> acts as the network device <NUM> or a part of the network device <NUM>, the processor <NUM> and the communication module <NUM> may cooperate to implement the method <NUM>, the process <NUM> and the flow <NUM> as described above with reference to <FIG>.

All operations and features as described above with reference to <FIG> are likewise applicable to the device <NUM> and have similar effects. For the purpose of simplification, the details will be omitted.

Generally, various example embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. While various aspects of example embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method <NUM>, the process <NUM> and the flow <NUM> as described above with reference to <FIG>. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various example embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Examples of the carrier include a signal, a computer readable medium and the like.

More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), Digital Versatile Disc (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular example embodiments. Certain features that are described in the context of separate example embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple example embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in languages specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above.

Various example embodiments of the techniques have been described. In addition to or as an alternative to the above, the following examples are described. The features described in any of the following examples may be utilized with any of the other examples described herein.

In some aspects, a device comprises: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the device to: determine a set of metrics related to quality of service (QoS) performance for a plurality of services in a cell in a measurement period; and determine access control barring (ACB) configuration in the cell based on comparison of the set of metrics with a set of thresholds.

In some example embodiments, the measurement period comprises a plurality of time intervals, and the device is caused to determine the set of metrics by: determining at least a subset of metrics in the set of metrics at the end of a time interval of the plurality of time intervals; and comparing at least the subset of metrics with thresholds associated with at least the subset of metrics in the set of thresholds.

In some example embodiments, the device is caused to determine the ACB configuration by: determining, based on the comparison of the at least one subset of metrics and the associated thresholds, whether requested QoS is achieved in the cell in the time interval; in response to determining that the requested QoS is unachieved, counting the time interval into a time period in which the requested QoS is unachieved in the cell; and determining the ACB configuration based on the time period.

In some example embodiments, the time interval is associated with a QoS level of a plurality of QoS levels for the plurality of services, the subset of metrics is associated with the QoS level, and the device is caused to determine the at least the subset of metrics by: determining the subset of metrics at the end of the time interval.

In some example embodiments, the device is caused to determine the ACB configuration by: determining that ACB is to be activated in the cell based on the comparison of the set of metrics with the set of thresholds.

In some example embodiments, the device is caused to determine that the ACB is to be activated by: determining, in the set of metrics, a number of metrics that are degraded compared with thresholds associated with the number of metrics in the set of thresholds; determining, at least in part based on the number of metrics, whether requested QoS is achieved in the cell in the measurement period; and in response to determining that the requested QoS is unachieved, determining that the ACB is to be activated in the cell.

In some example embodiments, the number of metrics are associated with a set of QoS levels for the plurality of services, and the device is caused to determine whether the requested QoS is achieved by: determining, further based on the set of QoS levels, whether the requested QoS is achieved in the measurement period in the cell.

In some example embodiments, the device is further caused to determine the ACB configuration by: determining overlapping of the cell with a neighboring cell and QoS performance of the neighboring cell; and determining a parameter for the ACB based on the overlapping of the cell with the neighboring cell and the QoS performance of the neighboring cell.

In some aspects, a method comprises: determining, by a network device, a set of metrics related to quality of service (QoS) performance for a plurality of services in a cell in a measurement period; and determining access control barring (ACB) configuration in the cell based on comparison of the set of metrics with a set of thresholds.

In some example embodiments, the measurement period comprises a plurality of time intervals, and determining the set of metrics comprises: determining at least a subset of metrics in the set of metrics at the end of a time interval of the plurality of time intervals; and comparing at least the subset of metrics with thresholds associated with at least the subset of metrics in the set of thresholds.

In some example embodiments, determining the ACB configuration comprises: determining, based on the comparison of the at least one subset of metrics and the associated thresholds, whether requested QoS is achieved in the cell in the time interval; in response to determining that the requested QoS is unachieved, counting the time interval into a time period in which the requested QoS is unachieved in the cell; and determining the ACB configuration based on the time period.

In some example embodiments, determining the ACB configuration based on the time period comprises: determining, based on a length of the time period, that ACB is to be activated in the cell in a time period subsequent to the measurement period.

In some example embodiments, the time interval is associated with a QoS level of a plurality of QoS levels for the plurality of services, the subset of metrics is associated with the QoS level, and determining the at least the subset of metrics comprises: determining the subset of metrics at the end of the time interval.

In some example embodiments, determining the ACB configuration comprises: determining that ACB is to be activated in the cell based on the comparison of the set of metrics with the set of thresholds.

In some example embodiments, determining that the ACB is to be activated comprises: determining, in the set of metrics, a number of metrics that are degraded compared with thresholds associated with the number of metrics in the set of thresholds; determining, at least in part based on the number of metrics, whether requested QoS is achieved in the cell in the measurement period; and in response to determining that the requested QoS is unachieved, determining that the ACB is to be activated in the cell.

In some example embodiments, the number of metrics are associated with a set of QoS levels for the plurality of services, and determining whether the requested QoS is achieved comprises: determining, further based on the set of QoS levels, whether the requested QoS is achieved in the measurement period in the cell.

In some example embodiments, determining the ACB configuration further comprises: determining overlapping of the cell with a neighboring cell and QoS performance of the neighboring cell; and determining a parameter for the ACB based on the overlapping of the cell with the neighboring cell and the QoS performance of the neighboring cell.

In some aspects, an apparatus comprises: means for determining, by a network device, a set of metrics related to quality of service (QoS) performance for a plurality of services in a cell in a measurement period; and means for determining access control barring (ACB) configuration in the cell based on comparison of the set of metrics with a set of thresholds.

In some example embodiments, the measurement period comprises a plurality of time intervals, and the means for determining the set of metrics comprises: means for determining at least a subset of metrics in the set of metrics at the end of a time interval of the plurality of time intervals; and means for comparing at least the subset of metrics with thresholds associated with at least the subset of metrics in the set of thresholds.

In some example embodiments, the means for determining the ACB configuration comprises: means for determining, based on the comparison of the at least one subset of metrics and the associated thresholds, whether requested QoS is achieved in the cell in the time interval; means for in response to determining that the requested QoS is unachieved, counting the time interval into a time period in which the requested QoS is unachieved in the cell; and means for determining the ACB configuration based on the time period.

In some example embodiments, the means for determining the ACB configuration based on the time period comprises: means for determining, based on a length of the time period, that ACB is to be activated in the cell in a time period subsequent to the measurement period.

In some example embodiments, the time interval is associated with a QoS level of a plurality of QoS levels for the plurality of services, the subset of metrics is associated with the QoS level, and the means for determining the at least the subset of metrics comprises: means for determining the subset of metrics at the end of the time interval.

In some example embodiments, the means for determining the ACB configuration comprises: means for determining that ACB is to be activated in the cell based on the comparison of the set of metrics with the set of thresholds.

In some example embodiments, the means for determining that the ACB is to be activated comprises: means for determining, in the set of metrics, a number of metrics that are degraded compared with thresholds associated with the number of metrics in the set of thresholds; means for determining, at least in part based on the number of metrics, whether requested QoS is achieved in the cell in the measurement period; and means for in response to determining that the requested QoS is unachieved, determining that the ACB is to be activated in the cell.

In some example embodiments, the number of metrics are associated with a set of QoS levels for the plurality of services, and the means for determining whether the requested QoS is achieved comprises: means for determining, further based on the set of QoS levels, whether the requested QoS is achieved in the measurement period in the cell.

In some example embodiments, the means for determining the ACB configuration further comprises: means for determining overlapping of the cell with a neighboring cell and QoS performance of the neighboring cell; and means for determining a parameter for the ACB based on the overlapping of the cell with the neighboring cell and the QoS performance of the neighboring cell.

Claim 1:
A network device (<NUM>), comprising:
means for determining a set of metrics, each metric being related to quality of service, QoS, performance for a plurality of services in a cell (<NUM>) in a measurement period; and
means for determining access control barring, ACB, configuration in the cell (<NUM>) based on comparison of the set of metrics with a set of thresholds;
wherein the measurement period comprises a plurality of time intervals, and the means for determining the set of metrics is further configured for :
determining at least a subset of metrics in the set of metrics at the end of a time interval of the plurality of time intervals; and
comparing at least the subset of metrics with thresholds associated with at least the subset of metrics in the set of thresholds;
wherein the means for determining the ACB configuration is further configured for:
determining, based on the comparison of the at least one subset of metrics and the associated thresholds, whether requested QoS is achieved in the cell (<NUM>) in the time interval;
in response to determining that the requested QoS is unachieved, counting the time interval into a time period in which the requested QoS is unachieved in the cell (<NUM>); and
determining the ACB configuration based on the time period.