Detecting rogue terminals sending false capabilities

Abstract

A method performed by a network node (111). The method is for a first wireless device (131). The first network node (11) operates via a wireless communications network (100). The first network node (111) determines (201) a first type of the first wireless device (131) based on an inconsistency in information provided by the first wireless device (131) indicating a capability of the first wireless device (131). The first network node (111) also initiates (203) one or more actions based on a result of the determination.

Description

[0001] NETWORK NODE, AND METHODS PERFORMED THEREBY, FOR HANDLING A FIRST

[0002] WIRELESS DEVICE

[0003] TECHNICAL FIELD

[0004] The present disclosure relates generally to a first network node and methods performed thereby for handling a first wireless device. The present disclosure also relates generally to a computer program and computer-readable storage medium, having stored thereon the computer program to carry out this method.

[0005] BACKGROUND

[0006] Wireless devices within a wireless communications network may be e.g., User Equipments (UEs), stations (STAs), mobile terminals, wireless terminals, terminals, and / or Mobile Stations (MS). Wireless devices are enabled to communicate wirelessly in a cellular communications network or wireless communication network, sometimes also referred to as a cellular radio system, cellular system, or cellular network. The communication may be performed e.g., between two wireless devices, between a wireless device and a regular telephone and / or between a wireless device and a server via a Radio Access Network (RAN) and possibly one or more core networks, comprised within the wireless communications network. Wireless devices may further be referred to as mobile telephones, cellular telephones, laptops, or tablets with wireless capability, just to mention some further examples. The wireless devices in the present context may be, for example, portable, pocket-storable, hand-held, computer-comprised, or vehicle-mounted mobile devices, enabled to communicate voice and / or data, via the RAN, with another entity, such as another terminal or a server.

[0007] The wireless communications network covers a geographical area which may be divided into cell areas, each cell area being served by a network node, which may be an access node such as a radio network node, radio node or a base station (BS), e.g., a Radio Base Station (RBS), which sometimes may be referred to as e.g., gNB, evolved Node B (“eNB”), “eNodeB”, “NodeB”, “B node”, Transmission Point (TP), or BTS (Base Transceiver Station), depending on the technology and terminology used. The base stations may be of different classes such as e.g., Wide Area Base Stations, Medium Range Base Stations, Local Area Base Stations, Home Base Stations, pico base stations, etc... , based on transmission power and thereby also cell size. A cell is the geographical area where radio coverage is provided by the base station or radio node at a base station site, or radio node site, respectively. One base station, situated on the base station site, may serve one or several cells. Further, each base station may support one or several communication technologies. The base stations may communicate over the air interface operating on radio frequencies with the terminals within range of the base stations. The wireless communications network may also comprise network nodes which may serve receiving nodes, such as wireless devices, with serving beams. In 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), base stations, which may be referred to as eNodeBs or even eNBs, may be directly connected to one or more core networks. In the context of this disclosure, the expression Downlink (DL) may be used for the transmission path from the base station to the wireless device. The expression Uplink (UL) may be used for the transmission path in the opposite direction i.e. , from the wireless device to the base station.

[0008] The standardization organization 3GPP is currently in the process of specifying a New Radio Interface called NR or 5G-UTRA, as well as a Fifth Generation (5G) Packet Core Network (CN), which may be referred to as Next Generation (NG) Core Network, abbreviated as NG-CN, NGC, 5G CN or 5G Core (5GC). NG may be understood to refer to the interface / reference point between the Radio Access Network (RAN) and the CN in 5G / NR. In a 5G System (5GS), a radio base station in NR may be referred to as a gNB or 5G Node B. An NR UE may be referred to as an nUE.

[0009] 3GPP introduced the 5G radio access technology NR, New Radio, in release 15 with enhancements done as part of release 16 and later. In release 15-16 there may be understood to be only one UE type supported having a set of mandatory minimum requirements in terms of supported functionality, e.g., support for up to 100 MHz bandwidth and having 2 Receiver (Rx) or 4 Rx branches, that is, antennas, for different Frequency Range 1 (FR1) bands [1], Additionally, there may be a set of optional functions for which the support may be signalled per individual UE.

[0010] NR Reduced Capability (RedCap) Devices

[0011] In 3GPP release 17, the support for devices with Reduced Capability, called RedCap, was introduced such that it became possible for these devices to operate in NR cells together with other and / or standard NR devices, referred to below as non-RedCap devices. Allowing these RedCap devices to access and / or operate in a network may be performed on a per cell basis.

[0012] RedCap devices may be understood to offer lower complexity, reduced power consumption, and cost-efficient and / or reduced approaches compared to regular NR devices, such as Enhanced Mobile Broadband (eMBB) devices, such as smartphones or Fixed Wireless Access (FWA) routers, while still benefiting from NR connectivity. These RedCap devices may be understood to be designed for a wide range of applications that may not require the extreme performance of high-end devices but may have better throughput and latency capabilities compared to the simpler Internet of Things (loT) technologies, such as LTE for Machines (LTE- M) or NarrowBand loT (NB-loT). Compared to standard NR devices, RedCap devices may be understood to be allowed to have fewer antennas, e.g., 1 or2, reduced bandwidth, e.g., 20 MHz for FR1 , and lower maximum throughput. They may be ideal for applications such as wearables, smart sensors, pocket routers and industrial loT (HoT) devices that may not need ultra-high speed or massive throughput, but may still require reliable NR connectivity. Optimized for battery-powered devices, RedCap may be understood to enable extended operational periods without frequent recharging, which may be crucial for applications, such as wearables and loT devices. With fewer Multiple Input Multiple Output (MIMO) layers, e.g., 1 or 2, and narrower bandwidth, e.g., from 100 MHz down to 20 MHz for FR1 , RedCap devices may be understood to be simpler and cheaper to manufacture, but they may be understood to remain more capable than NB-loT or LTE-M devices. The release 17 version of RedCap is targeted to correspond to throughput capabilities such as, or slightly higher than, LTE categories 1-4. This may be understood to provide a balanced approach for certain use cases where moderate data rates, extended battery life, and reduced complexity may be relevant. 3GPP release 18 specifies an even further reduced version of RedCap, denoted as enhanced RedCap (eRedCap) that may be understood to be targeted to correspond to LTE category Ibis with a throughput limit of ~10 Mbps.

[0013] Due to the reduced capabilities described above, these devices may be typically treated differently in the network compared to non-RedCap devices when it comes to different functionalities and / or algorithms. Examples of this include, but are not limited to, traffic steering, link adaptation algorithms, and parameter configuration settings for different functions such as connected mode Discontinuous Reception (DRX), Search Space Set Group (SSSG) switching, timer-based release.

[0014] More information on RedCap, in addition to 3GPP specifications such as [1][3], may be found for example in [2],

[0015] UE Capability

[0016] UE capability information may be understood to be relevant for the network to retrieve as soon as possible after the UE may enter CONNECTED mode to ensure efficient network utilization and provide appropriate services to different UEs. UE capability information may be understood to define what a device may do in terms of connectivity, performance, and communication protocols, ensuring that it may interact correctly with the network infrastructure. UE capability information may include various aspects such as the supported radio access technologies, e.g., LTE, NR, and UE type, e.g., normal / non-RedCap, RedCap, eRedCap, supported frequency bands, supported carrier aggregation, that is, how many carriers and band combinations a UE may aggregate, highest supported modulation e.g., 64 Quadrature Amplitude Modulation (QAM), 256QAM, 1024QAM and MIMO support, e.g., 2x2, 4x4, protocol, e.g., Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), PHYsical (PHY) functions and parameters, and other device-specific features. UE capability information may be exchanged between the UE and the network during the initial network attachment procedure through Radio Resource Control (RRC) messages. This information may enable the network to optimize resource allocation, select appropriate configurations, and offer services tailored to the specific capabilities of the UE.

[0017] The performance of a communications network may be degraded by misuse of UE capability information in existing methods.

[0018] SUMMARY

[0019] It is an object of embodiments herein to improve the handling of a wireless device in a wireless communications network.

[0020] According to a first aspect of embodiments herein, the object is achieved by a method, performed by a network node. The method is for handling a first wireless device. The network node operates via a wireless communications network. The network node determines a first type of the first wireless device. The determining is based on an inconsistency in information provided by the first wireless device. The information indicates a capability of the wireless device. The network node also initiates one or more actions based on a result of the determination.

[0021] According to a second aspect of embodiments herein, the object is achieved by a method, performed by the network node. The method is for handling the first wireless device. The network node operates via the wireless communications network. The network node is configured to determine the first type of the first wireless device based on the inconsistency in the information configured to be provided by the wireless device configured to indicate the capability of the wireless device. The network node is also be configured to initiate the one or more actions based on the result of the determination.

[0022] According to a fifth aspect of embodiments herein, the object is achieved by a computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the first node.

[0023] According to a sixth aspect of embodiments herein, the object is achieved by a computer-readable storage medium, having stored thereon the computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the first node.

[0024] By the network node determining the first type of the first wireless device, the network node may be able to detect if the first wireless device may have lower than expected capabilities for certain bands or misrepresent its capabilities, and therefore, by initiating the one or more actions, be enabled to implement policies to handle such a wireless device, or apply special treatments to prevent potential network disruptions or unfair usage scenarios.

[0025] For example, the network node may detect that the first wireless device may be exploiting, e.g., its UE capability report, by identifying deviations in one or more parameters or values within said report or behavior of the first wireless device throughout its connection, from those expected according to the standards for the first wireless device. Based on said detection, the network node may then be enabled to apply different treatments of the first wireless device compared to a second UE that may report its UE capability and behave according to the expected standards.

[0026] BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Examples of embodiments herein are described in more detail with reference to the accompanying drawings, according to the following description.

[0028] Figure 1 is a schematic diagram depicting an example of a wireless communications network, according to embodiments herein.

[0029] Figure 2 is a flowchart depicting a method in a network node, according to embodiments herein.

[0030] Figure 3 is a schematic block diagram illustrating an embodiment of a network node, according to embodiments herein.

[0031] Figure 4 is a flowchart depicting a method in a network node, according to an example associated to embodiments herein.

[0032] Figure 5 is a schematic block diagram illustrating an example of a communication system 500 in accordance with some embodiments.

[0033] Figure 6 is a schematic block diagram illustrating an example of a UE 600 in accordance with some embodiments.

[0034] Figure 7 is a schematic block diagram illustrating an example of a network node 700 in accordance with some embodiments.

[0035] Figure 8 is a block diagram illustrating an example of a virtualization environment 800 in which functions implemented by some embodiments may be virtualized.

[0036] DETAILED DESCRIPTION

[0037] As part of the development of embodiments herein, one or more challenges with the existing technology will first be identified and discussed.

[0038] A problem with the current 3GPP specification [3] may be understood to be that UEs may be allowed to freely signal UE capabilities using a wide value range that may not be according to the minimum RF requirements specified in [1] with regards to UE bandwidth and number of UE receiver antennas. Due to this, UEs with lower capabilities, that is, not 3GPP standard compliant, may try to connect to the network and may impact the operations negatively. This may become particularly problematic if a RedCap UE, e.g., only capable of 20 MHz bandwidth and 1-2 Rx antennas, ignores to include the RedCap parameter indication, e.g., RedCapParameters-r17 or ERedCapParameters-r18 [3], in its capability signaling when accessing a cell to falsely present itself as a normal and / or non-RedCap device. Other simplified UE types, for example UEs limited to 40 MHz instead of 100 MHz on certain bands may also degrade the performance in a network.

[0039] Detecting and managing such UEs that exploit their capabilities may be important for efficient network performance and ensuring fair usage of network resources. This may involve identifying UEs that may have lower than expected capabilities for certain bands or misrepresent their capabilities, implementing policies to handle such UEs, or applying special treatments to prevent potential network disruptions or unfair usage scenarios.

[0040] As an example, a scenario may be considered of an operator that may already provide services for standard NR devices that may not yet have invested in supporting RedCap devices, or that may not be interested -either temporarily or permanently- in serving RedCap devices due to their lower capabilities and potentially lower spectrum efficiency. Vendors with RedCap devices may therefore take the opportunity to use their RedCap devices to establish deceptive connections, falsifying their UE capabilities, with the network, falsely presenting themselves as NR devices with lower capabilities, on par with a RedCap device.

[0041] In the below description the terminology rogue UE may be used to refer to a UE that may connect to the network (NW) with capabilities lower than what 3GPP may have specified as minimum required for non-RedCap and RedCap UEs.

[0042] Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. Embodiments herein may be generally understood to relate to a method for detection and management of misuse of UE capabilities.

[0043] Methods are introduced in one or more network nodes, e.g., they may be collaborative, for the detection and special treatment of NR / 5G UEs exploiting the UE capability reporting framework, to report NR capabilities that may be below, and thus not compliant to, the minimum RF requirements for an NR UE as specified by 3GPP in [1], These requirements may specifically refer to the UE minimum channel bandwidth, specified per band in section 5.3.5 for non-RedCap UEs and in section 5.3I for RedCap UEs, and the minimum number of RX antenna ports, specified per band in section 7.2 for all UE types. Additionally, [5] states for capability lEs supportedBandwidthDL and supportedBandwidthUL that when this field is included in a band combination with a single band entry and a single [Component Carrier] (CC) entry (i.e. non-[Carrier Aggregation] (CA) band combination), the UE may be required to indicate the maximum channel bandwidth for the band according to TS 38. 101-1 and TS 38. 101-2. In one specific example, a UE may deceptively be reporting NR capabilities, presenting itself as a standard, e.g., non-RedCap NR device, that is, not include RedCap capability parameter, with low capabilities on par with a RedCap device for its supported bandwidth and number of antennas. The special treatment may be one or more of the following. Additional examples are provided later: a. Handing over, or releasing the UE without or with re-direct information, potentially to other bands and / or Radio Access Technologies (RATs) where such UEs may be handled without affecting traffic on the specific band the UE may have set up its connection, e.g., these may be bands prioritized by the operator for performance. In one aspect, the special treatment may be assigning these UEs to specific slices on which they may potentially be served with degraded quality of experience. b. Assigning the UE to Unified Access Control (UAC) groups for which access may not be allowed, e.g., based on collaboration between Core Network (CN), e.g., the Access and Mobility Management Function (AMF) and Radio Access Network (RAN), e.g., gNB. c. If the gNB decides that the UE may be admitted, e.g., on a specific band, or on any band, degradation actions may be taken for this UE. Such degradation actions may be one or more of:

[0044] 1) Lowering scheduling priority, delaying scheduling, e.g., potentially beyond specified Quality of Service (QoS) limits.

[0045] 2) Using a higher Block Error Rate (BLER) target or residual error rate.

[0046] 3) Assigning less frequent Scheduling Request (SR) / Physical Uplink Control CHannel (PUCCH) occasions.

[0047] 4) Bundling these UEs so that they may share a same Connected-mode Discontinuous Reception (C-DRX) onDuration and / or SSSG offset.

[0048] 5) Limit Carrier Aggregation (CA), # Transmitter (Tx) chains Multiple Input Multiple Output (MIMO), modulation, e.g., <64QAM, Transport Block Size (TBS) size, # Physical Resource Blocks (PRBs) for Physical Uplink Shared Channel (PUSCH) and / or Physical Downlink Shared Channel (PDSCH).

[0049] Some of the embodiments contemplated will now be described more fully hereinafter with reference to the accompanying drawings, in which examples are shown. In this section, the embodiments herein will be illustrated in more detail by a number of exemplary embodiments. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. It should be noted that the exemplary embodiments herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. Figure 1 depicts two non-limiting examples, in panel a) and panel b), respectively, of a wireless network or wireless communications network 100, sometimes also referred to as a wireless communications system, cellular radio system, or cellular network, in which embodiments herein may be implemented. The wireless communications network 100 may be a 5G system, 5G network, or Next Gen System. In other examples, the wireless communications network 100 may be a newer system with similar functionality, e.g., a Sixth Generation (6G) network. In other examples, the wireless communications network 100 may, e.g., alternatively or additionally, support other technologies such as, for example, Long-Term Evolution (LTE), e.g., LTE for Machines (LTE-M), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), LTE operating in an unlicensed band, such as LTE Licensed-Assisted Access (LAA), enhanced LAA (eLAA), further enhanced LAA (feLAA) and / or MulteFire. Yet in other examples, the wireless communications network 100 may further support other technologies such as, for example Wideband Code Division Multiple Access (WCDMA), Universal Terrestrial Radio Access (UTRA) TDD, Global System for Mobile communications (GSM) network, GSM / Enhanced Data Rates for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, network comprising any combination of Radio Access Technologies (RATs) such as e.g., Multi-Standard Radio (MSR) base stations, multi-RAT base stations etc., any 6rd Generation Partnership Project (3GPP) cellular network, WiFi networks, Worldwide Interoperability for Microwave Access (WiMax), or any cellular network or system. The wireless communications network 100 may support Machine Type Communication (MTC), enhanced MTC (eMTC), Internet of Things (loT) and / or NarrowBand loT (NB-loT). Thus, although terminology from 5G / NR and LTE may be used in this disclosure to exemplify embodiments herein, this should not be seen as limiting the scope of the embodiments herein to only the aforementioned system.

[0050] The wireless communications network 100 may comprise a plurality of network nodes, whereof a network node 111 is depicted in the non-limiting example of Figure 1. In some embodiments, as depicted in the non-limiting examples of Figure 1 , the wireless communications network 100 may comprise another network node 112. Any of the network node 111 and the another network node 112 may be a radio network node. That is, a transmission point such as a radio base station, for example a gNB, or any other network node with similar features capable of serving a user equipment, such as a wireless device or a machine type communication device, in the wireless communications network 100. In some examples, such as that depicted in Figure 1 b for the network node 111 , any of the network node 111 and the another network node 112 may be a distributed node, and may partially perform its functions in collaboration with a virtual node 114 in a cloud 115. Any of the network node 111 and the another network node 112 may be directly connected to one or more core networks, e.g., to one or more network nodes in the one or more core networks.

[0051] The wireless communications network 100 may cover a geographical area, which in some embodiments may be divided into cell areas, wherein each cell area may be served by a radio network node, although, one radio network node may serve one or several cells. The wireless communications network 100 may comprise a first cell 121 and another cell 122. In the example of Figure 1 , the network node 111 serves the first cell 121 and the another network node 112 serves the another cell 122. However, in other examples the network node 111 may serve the first cell 121 and the another cell 122. In some examples, the network node 111 may be the same network node as the another network node 112. It may be understood that the number of cells depicted in the non-limiting examples of Figure 1 is for illustrative purposes only. Additional cells may be served by any of the network node 111 and the another network node 112.

[0052] Any of the network node 111 and the another network node 112 may serve cells on different frequency bands, e.g., multiple cells, e.g., a first first cell 121a, a second first cell 121b, a third first cell 121c, etc... , which may have different coverage due to that they may use different frequencies, e.g., bands n7, n20, n78, respectively.

[0053] Any of the network node 111 and the another network node 112 may be of different classes, such as, e.g., macro base station, home base station or pico base station, based on transmission power and thereby also cell size. In some examples, the any of the network node 111 and the another network node 112 may serve receiving nodes with serving beams. Any of the network node 111 and the another network node 112 may support one or several communication technologies, and its name may depend on the technology and terminology used.

[0054] A plurality of wireless devices may be located in the wireless communication network 100, whereof a first wireless device 131 is depicted in the non-limiting example of Figure 1. In some embodiments, as depicted in the non-limiting examples of Figure 1 , the wireless communications network 100 may comprise one or more second wireless devices 132. In some particular examples, as depicted in the non-limiting examples of Figure 1, the first wireless device 131 may be comprised in a group of wireless devices 133. The group of wireless devices 133 may comprise one or more third wireless devices 134. Any of the first wireless device 131 , the one or more second wireless devices 132 and the one or more third wireless devices 134 comprised in the wireless communications network 100 may be a wireless communication device such as a UE, a 5G UE or nil E, which may also be known as e.g., mobile terminal, wireless terminal and / or mobile station, a mobile telephone, cellular telephone, or laptop with wireless capability, just to mention some further examples. Any of the first wireless device 131 , the one or more second wireless devices 132 and the one or more third wireless devices 134 may be, for example, portable, pocket-storable, hand-held, computer-comprised, or a vehicle-mounted mobile device, enabled to communicate voice and / or data, via the RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, Machine-to-Machine (M2M) device, a sensor, loT device, NB-loT device, device equipped with a wireless interface, such as a printer or a file storage device, modem, or any other radio network unit capable of communicating over a radio link in a communications system. Any of the first wireless device 131 , the one or more second wireless devices 132 and the one or more third wireless devices 134 comprised in the wireless communications network 100 may be enabled to communicate wirelessly in the wireless communications network 100. The communication may be performed e.g., via a RAN, and possibly the one or more core networks, which may be comprised within the wireless communications network 100.

[0055] The first wireless device 131 may be configured to communicate within the wireless communications network 100 with the network node 111 over a first link 141 , e.g., a radio link. The network node 111 may be configured to communicate within the wireless communications network 100 with the virtual node 114 over a second link 142, e.g., a radio link or a wired link. Any of the one or more second wireless devices 132 and the one or more third wireless devices 134 may be configured to communicate within the wireless communications network 100 with the network node 111 , over a respective link, e.g., a radio link, which is not depicted in Figure 1 to simplify the figure. The first wireless device 131 may be configured to communicate within the wireless communications network 100 with the another network node 112 over a third link, e.g., a radio link, which is not depicted in Figure 1 to simplify the figure.

[0056] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0057] In general, the usage of “first”, “second”, and / or “third” herein may be understood to be an arbitrary way to denote different elements or entities, and may be understood to not confer a cumulative or chronological character to the nouns they modify, unless otherwise noted, based on context.

[0058] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

[0059] More specifically, the following are embodiments related to a network node, such as the network node 111 , e.g., a gNB.

[0060] Some embodiments herein will now be further described with some non-limiting examples, which may be combined with the embodiments described. In this section, the 5G radio access technology NR may be used to explain the embodiments herein, but similar approaches may be applied to both legacy systems, such as LTE, or future systems such as 6G, where different UE capabilities may be used.

[0061] In the following description, any reference to a / the UE, based on context, and / or rogue UE, and / or RedCap UE may be understood to equally refer the first wireless device 131 ; any reference to a / the non-RedCap UE and / or normal UE may be understood to equally refer to any of the one or more second wireless devices 132; any reference to a / the gNB and / or a / the network and / or a / the network node may be understood to equally refer to the network node 111.

[0062] Embodiments of a method, performed by a network node, such as the network node 111 , will now be described with reference to the flowchart depicted in Figure 2. The method is for handling a first wireless device such as the first wireless device 131. The network node 111 operates via a wireless communications network, such as the wireless communications network 100.

[0063] The method may be understood to be computer-implemented.

[0064] In some embodiments, the wireless communications network 100 may support New Radio (NR).

[0065] Several embodiments are comprised herein. The method may comprise one or more of the following actions. In some embodiments, all the actions may be performed. In some examples, Action 201 and Action 203 may be performed. One or more embodiments may be combined, where applicable. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. All possible combinations are not described to simplify the description. A non-limiting example of the method performed by the network node 111 is depicted in Figure 2. In Figure 2, optional actions in some embodiments may be represented with dashed lines. In some embodiments, the actions may be performed in a different order than that depicted Figure 2.

[0066] Action 201

[0067] In this Action 201 , the network node 111 determines a first type of the first wireless device 131.

[0068] Determining may be understood as calculating, deriving, or similar.

[0069] The first type may be, e.g., a UE type, such as RedCap UE or non-RedCap UE. Examples of UE types are provided later.

[0070] The determining in this Action 201 is based on an inconsistency in information provided by the first wireless device 131. The information indicates a capability of the first wireless device 131. The first wireless device 131 may operate in the wireless communications network 100.

[0071] A capability may be understood to indicate what feature or features a wireless device, such as the first wireless device 131, may support, and what parametrizations of those features may be supported.

[0072] That the information indicates, e.g., the capability, may be understood as that the information may be understood to point to the capability, by for example, comprising an explicit indication of the capability, or by enabling to derive the capability by, for example, comprising an implicit indication that may enable a derivation of the capability. For example, the information may be an identity of the first wireless device 131, previously mapped to one or more first capabilities in a first database.

[0073] The inconsistency may be, for example, a deviation, or a lack of correspondence, from an expected indication, e.g., value, parameter, signal or behavior. The deviation or deviations may be based on parameters, and / or values, and / or observed behavior related to the standardized supported connection type and minimum RF requirements for the first wireless device 131, which may be related to one or more of: a) support of the first wireless device 131 for a specific band, e.g., TDD, FDD, or a specific TDD / FDD band, b) minimum channel bandwidth of the first wireless device 131 for a specific band, c) minimum number of RX antenna ports for a band, d) carrier aggregation support, e) dual connectivity support, f) UE type, e.g., RedCap or eRedCap, and g) indicated accessStratumRelease capability IE.

[0074] Said behavior detection may be based on observations in the network node 111 that the first wireless device 131 , throughout its connection, may transmit measurement reports and / or reference signals in a manner where the reported support for connection type and / or reported RF characteristics may not be fully met. For example, the first wireless device 131 may never report rank 4 despite having reported 4 Rx capability, may transmit measurement reports that may consistently disfavor carrier aggregation, dual connectivity, or alike despite having reported support for said features.

[0075] The information may comprise one or more of: one or more parameters and one or more values indicative of one or more of the following: one or more radio access capabilities, one or more radio frequency requirements, support for a specific band, a minimum channel bandwidth, e.g., per band, a minimum number of receiver antenna ports, e.g., per band, carrier aggregation support, dual connectivity support, type of wireless device, e.g., UE type, and accessstratum Release capability, e.g., indicated accessstratum Release capability IE.

[0076] The information may have been provided by the first wireless device 131 in a capability report.

[0077] The information may be provided by the first wireless device 131 in one or more of the following: the capability report, one or more measurement reports, one or more reference signals, the identity of the first wireless device 131 , previously mapped to one or more first capabilities in the first database, and the identity of the first wireless device 131 lacking a corresponding identity in a second database.

[0078] For example, when the first wireless device 131 connects, e.g., when the first wireless device 131 may enter CONNECTED mode from IDLE mode, the network node 111 may get information of the associated UE radio access capabilities either from the “UE capability transfer” procedure on RRC level [3] or, if the first wireless device 131 already is Non-Access Stratum (NAS) registered, from the AMF, in the 5GC, in a Next Generation Application Protocol (NGAP) message, e.g., as part of UE context setup [4],

[0079] In some embodiments, one of the following may apply. According to one option, the type of wireless device comprised in the information may be different from the first type and inconsistent with the other one or more of: one or more parameters and / or one or more values comprised in the information.

[0080] According to another option, the information may lack an explicit indication of the type of wireless device.

[0081] In some embodiments, one or more of the following may apply. According to one option, one or more first indications comprised in the information may correspond to a non-reduced capability wireless device, e.g., non-reduced capability UE, and one or more second indications comprised in the information may correspond to a reduced capability wireless device, e.g., reduced capability UE. According to another option, the determined first type may be of a reduced capability wireless device, e.g., reduced capability UE.

[0082] According to embodiments herein, despite the first wireless device 131 presenting itself as a specific UE type, e.g., standard non-RedCap UE, through its reported capabilities, its radio access capabilities may be used by the network node 111 to identify and classify the first wireless device 131 into one of several predefined UE types. This may be achieved through different methods, and including a combination thereof, such as the following.

[0083] In some examples, the network node 111 to may identify and classify the first wireless device 131 into one of several predefined UE types by examining one or more of the reported first wireless device 131 radio access capability information elements and their fields, e.g., parameters and / or values of the parameters, by comparing them with specific values, e.g., or value ranges, to determine the UE type.

[0084] In some examples, the network node 111 to may identify and classify the first wireless device 131 into one of several predefined UE types by examining the behavior of the first wireless device 131 throughout its connection. Such behavior detection may be based on observations in a NW node that the first wireless device 131 , throughout its connection, may transmit measurement reports and / or reference signals in a manner where the reported support for connection type and / or reported RF characteristics may not be fully met. For example, the first wireless device 131 may never report rank 4 despite having reported 4 Rx capability, may transmit measurement reports that consistently disfavor carrier aggregation, dual connectivity, or alike despite having reported support for said features.

[0085] In some examples, the network node 111 to may identify and classify the first wireless device 131 into one of several predefined UE types by using a signaled UE identifier, e.g., International Mobile Equipment Identity (IMEI) / IMEI_ Software Version (SV) / IMEI_Type Allocation Code (TAC), International Mobile Subscriber Identity (IMSI), any other type of standardized or proprietary identifier, or alike, that may be mapped to a UE type, for example, in a database that may be queried. The database may be either external or internal to the network node 111. Its contents may be provided by an operator, or dynamically built up by the network node 111 itself based on historical data.

[0086] In some examples, the network node 111 to may identify and classify the first wireless device 131 into one of several predefined UE types by using a signaled UE identifier, e.g., IMEI / IMEI_SV / IMEI_TAC, IMSI, any other type of standardized or proprietary identifier, or alike, that may not be present in an exemption database. The database may be either external or internal to the network node 111. Its contents may be provided by an operator, or dynamically built up by the network node 111 itself based on historical data.

[0087] Type of wireless device, e.g., UE type

[0088] In the following, embodiments herein may be described using NR / 5G terminology with an example of five different UE types. It may be noted that additional UE types may exist, and not all may need to be supported in a product implementing embodiments herein. That is, the following examples may be understood to be provided for illustrative purposes and are not limiting. Examples of UE types may be described as follows, where the set may be defined as follows, with each type explained in more detail in the Table 1 below:

[0089] UeType = {UeType_Normal, UeType_Rogue_RedCap, UeType_Rogue_BW, UeType_Rogue_2Rx, UeType_Rogue_BW_2Rx}

[0090] Table 1

[0091] In the following, embodiments herein may be described using NR / 5G terminology with an example of five different UE types and 12 different action alternatives. It may be noted that additional UE types and actions may exist, and not all may need to be supported in a product implementing embodiments herein.

[0092] In one aspect, the first wireless device 131 may report capabilities that may conform to the described “UeType_Normal”, however throughout its connection(s), it may consistently deviate from a behavior of a typical UeType_Normal. For example, the first wireless device 131 may have reported maxNumberMIMO-LayersPDSCH according to the standardized capability, as a UeType_Normal may have reported, however throughout its connection, it may consistently report rank and / or transmit UL reference signals, e.g., Sounding Reference Signals (SRS) such that only fewer layers than what may have been reported as capabilities may be employed. For example, despite having reported maxNumberMIMO-LayersPDSCH = fourLayers, the first wireless device 131 may consistently report rank < 4 in its Channel State Information (CSI) reports, e.g., may consistently report rank=1 , e.g., the first wireless device 131 may potentially be a 1 Rx UE. As such, based on observed behavior, this first wireless device 131 may then also be categorized as a rogue UE by the network node 111. In one example, before categorizing this first wireless device 131 as rogue, the network node 111 may gather observations from multiple connections, potentially observing not only this first wireless device 131 but other UEs fully or partially sharing a same identity such as IMEI / TAC, e.g. same device brand and / or model and / or software (SW) / hardware (HW) version, or alike.

[0093] In some embodiments, the first type may be a type referred to herein as a rogue type.

[0094] The rogue type may, in some particular non-limiting examples, correspond to NR / 5G UEs that may exploit the UE capability reporting framework, to report NR capabilities that may be below, and thus not compliant to, the minimum RF requirements for an NR UE as specified by 3GPP in [1], These requirements may specifically refer to the UE minimum channel bandwidth, specified per band in section 5.3.5 for non-RedCap UEs and in section 5.3I for RedCap UEs, and the minimum number of Rx antenna ports, specified per band in section 7.2 for all UE types. In some embodiments, the method may further comprise one or more of the following four actions 202, 204, 205, 206.

[0095] By the network node 111 determining the first type of the first wireless device 131 in this Action 201 , the network node 111 may be able to detect if the first wireless device 131 may have lower than expected capabilities for certain bands or misrepresent its capabilities, and therefore, be enabled to implement policies to handle such a wireless device, or apply special treatments to prevent potential network disruptions or unfair usage scenarios.

[0096] For example, the network node 111 may detect that the first wireless device 131 may be exploiting, e.g., its UE capability report, by identifying deviations in one or more parameters or values within said report or behavior of the first wireless device 131 throughout its connection, from those expected according to the standards for the first wireless device 131 . Based on said detection, the network node 111 may then be enabled to apply different treatments of the first wireless device 131 compared to a second UE that may report its UE capability and behave according to the expected standards.

[0097] Action 202

[0098] In some embodiments, in this Action 202, the network node 111 may assign the determined first type to the first wireless device 131 .

[0099] For example, based on the detection performed in Action 201 , the first wireless device 131 may be categorized into one of several predefined UE types.

[0100] For each predefined UE type, a set of rules and / or parameter values may be defined to control the treatment / handling of a UE belonging to that UE type when connected to a specific cell and / or during certain time and / or during certain scenarios. For example, the handling may be different at times of day, in specific areas, or during scenarios such as during congestion versus during low traffic.

[0101] By assigning the first type to the first wireless device 131 in this Action 202, the network node 111 may be enabled to store the determined first type in association with an identifier of the first wireless device 131 in e.g., the first database, so that upon new connections, the network node 111 , or another network node or device, may be enabled to retrieve information from said first database for potential identification of the first UE type.

[0102] Action 203

[0103] In this Action 203, the network node 111 initiates one or more actions.

[0104] Initiating may comprise starting or triggering.

[0105] The initiating of the one or more actions are based on a result of the determination.

[0106] When the first wireless device 131 may be classified as a specific UE type, certain actions and / or parameters for controlling its behavior may be applied by the network node 111 , e.g., a gNB, throughout the connection of the first wireless device 131 in one or more cells. Thus, these actions / parameters may be cell specific and be configured from a set of alternatives.

[0107] The one or more actions may be understood to correspond to treatments that may be configured per type of wireless device, e.g., UE Type. It may be noted that multiple treatments may also be applied for a given type of wireless device, e.g., UE type. However, some treatments may be exclusively applied without combining them with other treatments. An example of this is provided further below.

[0108] In some embodiments, the one or more actions may comprise one of the following options.

[0109] According to one option, the one or more actions may comprise handing over the first wireless device 131 to another network node 112, another cell 122, another radio access technology or another band. The another cell 122 may be served in some examples, by the network node 111. In one example referred to herein as “I”, based on action setting, the treatment may be handing over the first wireless device 131, e.g., a “rogue type” UE, to other bands and / or RATs than those used primarily for other, rogue or standard, UEs, which may be considered second UEs. For example, the current band and / or RAT may be prioritized by the operator for performance where the first wireless device 131 , e.g., the “rogue” UE, may not be desired.

[0110] According to another option, the one or more actions may comprise releasing the first wireless device 131. In some examples, the one or more actions may comprise a release with re-direct information, wherein the first wireless device 131 may be handed over via the first wireless device 131 going via IDLE mode. In one example referred to herein as “II”, based on action setting, the treatment may be rejecting, or releasing the first wireless device 131, e.g., a “rogue type” UE, without or with re-direct information, potentially to other bands and / or RATs than those used, e.g., primarily, for other UEs. Such release or redirect may contain further instructions to the first wireless device 131. For example, referred to herein as “I I. a”, in one aspect, the band the first wireless device 131 may be redirected to may not even be supported by the network node 111 , e.g., the first wireless device 131 may be redirected to non-existing coverage. In one other example, referred to herein as “II. b”, the RRC Release message may include additional information that may discourage the first wireless device 131 to retry camping on the current cell and / or carrier and / or band and / or RAT. Further potentially including information about cell / freguency / band / RAT deprioritization and / or barring timer. For example, the RRC Release message may include the IE “deprioritisationReq” [3], meaning that the first wireless device 131 may be required to consider current frequency and or all frequencies of NR to be the lowest priority, e.g., lower than any of the network configured values, during a configured time (deprioritisationTimer [3]). In one other example, referred to herein as “ll.c”, the RRC Release or RRC Reject message may be used for rejecting the first wireless device 131 without any further assistance on where the first wireless device 131 may have to seek coverage. As such, the RRC Release or Reject message may contain the IE “waittime” [3] during which the first wireless device 131 may be barred from accessing the cell.

[0111] According to a further option, the one or more actions may comprise assigning the first wireless device 131 to a slice with degraded quality of experience in comparison with one or more second wireless devices 132 with non-reduced capability. In one example referred to herein as “III”, based on action setting, the treatment may be assigning the first wireless device 131, e.g., a “rogue type” UE, to a specific slice on which it may potentially be served with degraded quality of experience.

[0112] According to yet another option, the one or more actions may comprise assigning the first wireless device 131 to a group of wireless devices 133 for which access is not allowed. In one example referred to herein as “IV”, based on action setting, the treatment may be assigning the first wireless device 131, e.g., a “rogue type” UE, to UAC groups for which access may be not allowed. For example, based on collaboration between CN, e.g., AMF, and RAN, e.g., the network node 111, which may be a gNB.

[0113] According to another option, the one or more actions may comprise admitting the first wireless device 131 as a wireless device having the determined first type, e.g., RedCap UE.

[0114] According to yet another option, the one or more actions may comprise admitting the first wireless device 131 with one or more degraded actions of: i) lowering a scheduling priority of the first wireless device 131 , e.g., in one example referred to herein as “a”, lower scheduling priority, delaying scheduling, potentially beyond specified QoS limits, ii) increasing a Block Error Rate or a residual error rate for the first wireless device 131, e.g., e.g., in one example referred to herein as “b”, using a higher BLER target or residual error rate iii) assigning fewer scheduling requests and Physical Uplink Control Channel (PUCCH) occasions to the first wireless device 131 , e.g., in one example referred to herein as “c”, assigning less frequent Scheduling Request (SR) / PUCCH occasions, iv) bundling the group of wireless devices 133 to share one or more of: a Connected-mode Discontinuous Reception (DRX) and a Search Space Set Group (SSSG), e.g., in one example referred to herein as “d”, bundling the first UE types, e.g., all UEs of the first UE type, so that they may share same C-DRX onDuration and / or SSSG offset, v) limiting carrier aggregation of the first wireless device 131 , e.g., in one example referred to herein as “e”, limit / not use carrier aggregation or dual connectivity, vi) limiting usage of transmitter (Tx) chains by the first wireless device 131 , e.g., in one example referred to herein as “f”, limit Tx chains usage e.g., in MIMO, vii) limiting modulation for the first wireless device 131 , e.g., in one example referred to herein as “g”, limit modulation, e.g. <64QAM, viii) limiting transport block size (TBS) for the first wireless device 131, in one example referred to herein as “h”, and ix) limiting a number of resources for transmission for the first wireless device 131 e.g., in one example referred to herein as “i”, limit the number of PRBs for PUSCH / PDSCH transmission. In one example referred to herein as “V”, based on action setting, the treatment may be that, if the network node 111 decides that the first wireless device 131 , e.g., a “rogue type” UE, may be admitted, e.g., on a specific band, or on any band, degradation actions may be taken while serving the first wireless device 131 , e.g., the “rogue type” UE. Such degradation actions may be one or more of examples a)-i) in this paragraph.

[0115] Based on action setting, the treatment may be one or more of examples I -V, a-i as described in the previous paragraph.

[0116] From the list above, the following sub-set of treatments may be assumed to be used, where the first two “TreatAsNormal / ’TreatAsRedCap" may be included to be able to configure that no special treatment / action may be applied for rogue UE types: UeType_Treatments={TreatAsNormal (N / A), TreatAsRedCap (N / A), HandoverlntraRAT (I.), ReleaseWithoutRedirect (II.), ReleaseWithRedirectlntraRAT (II.), ReleaseWithRedirectlnterRAT (II.), AssignUAC (IV.), DegradeSchedulingPrio (V.a.), ApplyHigherBLER (V.b.), LongSR_Period (V.c.), LimitModulation(V.g.), LimitPrb(V.i.)}.

[0117] It may be noted that extra configuration parameters may be needed for each of the items in the list above, but may not be described in detail as part of this disclosure, as many of them are known for people skilled in the art. Some of these parameters are provided in the examples below.

[0118] In a first group of embodiments, the one or more actions may comprise admitting the first wireless device 131 in the first cell 121 wherein the network node 111 may be communicating with the first wireless device 131 .

[0119] In some of the embodiments in the first group, the first wireless device 131 may be admitted in the first cell 121 as having the determined first type, e.g., RedCap UE.

[0120] In some of these embodiments in the first group, one of the following options may apply. According to one option, the first type is not allowed, supported or enabled in the first cell 121 . According to another option, the first type is allowed, supported or enabled in the first cell 121.

[0121] In some embodiments a second group of embodiments, the reduced capability wireless device, e.g., reduced capability UE, may be handed over to operate in the another cell 122.

[0122] In some embodiments in the second group, the reduced capability wireless device, e.g., reduced capability UE, may be admitted in the another cell 122 with the one or more degraded actions.

[0123] In some embodiments in the second group of embodiments, the first type may be not allowed, supported or enabled in the first cell 121.

[0124] In some embodiments, the one or more actions may be applied according to the assigned first type. In this disclosure, mechanisms may be introduced that may enable the network node 111 to detect, in particular examples of Action 201 , and, in particular examples of this Action 203, provide special treatment for NR / 5G UEs that may exploit the UE capability reporting framework, to report NR capabilities that may be below, and thus not compliant to, the minimum RF requirements for an NR UE as specified by 3GPP in [1], These requirements may specifically refer to the UE minimum channel bandwidth, specified per band in section 5.3.5 for non-RedCap UEs and in section 5.3I for RedCap UEs, and the minimum number of Rx antenna ports, specified per band in section 7.2 for all UE types.

[0125] Even if this disclosure may refer to the minimum capabilities as standardized by 3GPP in [1] per band, an implementation of this may select other less stringent values compared to what is written in a certain version / release of the 38.101 specification. For example, if version 18.7.0 requires a UE to support 100 MHz for a certain band, e.g., n40 for SubCarrier Spacing (SCS) 30kHz, a lower value, such as 80 MHz, may be used as minimum bandwidth requirement threshold, since this was the minimum requirement specified in version 16.21.0. Even lower values may be used that may have never been part of any version of the 38.101 standard, starting from version 15.0.0, for example, if there are certain popular UEs deployed with such a capability. The minimum requirements may further be adapted to depend on the release the first wireless device 131 may indicate in UE capability IE accessStratumRelease.

[0126] Examples

[0127] A scenario may be assumed where an operator may have NR cells deployed on multiple bands according to the following:

[0128] - n7 (2600 MHz), FDD, 20 MHz

[0129] - n20 (800 MHz), FDD, 15 MHz

[0130] - n78 (3500 MHz), TDD, 100 MHz

[0131] The operator may have different strategies for how different UEs may have to be treated when accessing cells on different bands and a few examples are provided below where all assume the above deployment. Note that the same operator may apply different strategies on different parts of its NW as a configuration may be set per cell. Detailed examples have been provided of treatments that may be configured per UeType, for example using the set described above.

[0132] Example 1 :

[0133] RedCap is enabled on band n20 and if rogue RedCap UEs access on that cell, they are treated as other RedCap UEs. Rogue UEs on band n7, except the ones that may support 4Rx, which may be understood to be required for that band, are re-directed to n20. All rogue UEs accessing band n78 are re-directed to band n20.

[0134] Example 2:

[0135] Similar to example 1 but with the difference that rogue RedCap UE types on n20 are treated with lower scheduling priority, compared to “normal” UEs, e.g., non-RedCap and RedCap UEs, e.g., UeType_Rogue_RedCap= DegradeSchedulingPrio on n20.

[0136] Example 3:

[0137] RedCap is not enabled on any band due to that the operator does not have correct gNB SW, or SW license, to secure proper operation / handling of RedCap UEs in the network. In this case, there may be a default treatment / action in the network node 111 for rogue RedCap UE types that may not be changed by the operator, until proper software (SW) and / or license may be installed on the network node 111. Similar may apply to other rogue UEs.

[0138] In this example, the default treatment of all identified rogue UEs may be to lower the scheduling priority and set the SR / PUCCH period to e.g., above or equal to 80 ms.

[0139] By the network node 111 initiating the one or more actions based on a result of the determination of Action 201 , the network node may be able to implement policies to handle the first wireless device if the network node detects that the first wireless device may have lower than expected capabilities for certain bands or misrepresent its capabilities, or be enabled to, or apply special treatments to prevent potential network disruptions or unfair usage scenarios.

[0140] Action 204

[0141] In this Action 204, the network node 111 may store an identity of the first wireless device 131 in the first database. The identity may be e.g., IMEI, IMEI / SV, IMEI / TAC, IMSI, any other type of standardized or proprietary identifier, or alike, information of the first type of the first wireless device 131 , e.g. the first UE type.

[0142] The identity may be mapped to the one or more first capabilities in the first database.

[0143] The contents of the first database may further be configured by an external NW node or an operator.

[0144] Action 205

[0145] In this Action 205, the network node 111 may store the identity of the first wireless device 131 in a second database.

[0146] The storing in this Action 205 of the identity of the first wireless device 131 in a second database may be for exemption handling. That is, to apply one or more exceptions to the first wireless device 131.

[0147] For example, UEs identified to be of the first type may be exempt from special treatment in case their identity matches the contents of the second database. Action 206

[0148] In this Action 206, the network node 111 may retrieve the identity of the first wireless device 131 from the first database at a later time point. As stated earlier, upon new connections, network node 111 may retrieve information from said first database for potential identification of the first type of the first wireless device 131 , e.g., the first UE type.

[0149] Non-limiting examples of embodiments herein may include the following.

[0150] In a first non-limiting example, a method in which a NW node may detect that a first UE is exploiting its UE capability report by identifying deviations in one or more parameters or values within said report or behavior of the UE throughout its connection from those expected according to the standards for the first UE. Based on said detection, the NW node may apply different treatments of the first UE compared to a second UE that may reports its UE capability and behave according to the expected standards.

[0151] In a second non-limiting example, the method of the first non-limiting example, wherein the deviations may be based on parameters, and / or values, and / or observed behavior related to the standardized supported connection type and minimum RF requirements for a UE, which may be related to one or more of: a) UE support for a specific band, e.g., TDD, FDD, or a specific TDD / FDD band, b) UE minimum channel bandwidth for a specific band, c) minimum number of RX antenna ports for a band, d) carrier aggregation support, e) dual connectivity support, f) UE type, e.g., RedCap or eRedCap, and g) indicated accessstratum Release capability IE.

[0152] In a third non-limiting example, the method of any of the preceding first - second nonlimiting examples, wherein said behavior detection may be based on observations in the NW node that the UE, throughout its connection, may transmit measurement reports and / or reference signals in a manner where the reported support for connection type and / or reported RF characteristics may not be fully met. For example, the UE may never report rank 4 despite having reported 4 Rx capability, may transmit measurement reports that may consistently disfavor carrier aggregation, dual connectivity, or alike despite having reported support for said features.

[0153] In a fourth non-limiting example, the method of any of the preceding first-third nonlimiting examples, wherein based on said detection, the first UE may be categorized into one of several predefined UE types.

[0154] In a fifth non-limiting example, the method of any of the preceding first-fourth non-limiting examples, wherein for each predefined UE type, a set of rules and / or parameter values may be defined to control the treatment / handling of a UE belonging to that UE type when connected to a specific cell and / or during certain time and / or during certain scenarios. For example, the handling may be different at times of day, in specific areas, or during scenarios such as during congestion versus during low traffic.

[0155] In a sixth non-limiting example, the method of any of the preceding first-fifth non-limiting examples, wherein the treatment may be one or more of: a. Handing over the first UE to other bands / RATs than those used primarily for second UEs. For example, the current band / RAT may be prioritized by the operator for performance where the first UE may be not desired. b. Rejecting or releasing the first UE without or with re-direct information, potentially to other bands / RATs than those used primarily for second UEs. Further potentially including information about cell / freguency / band / RAT deprioritization and / or barring timer. c. Assigning the first UE to a specific slice on which it may potentially be served with degraded quality of experience. d. Assigning the first UE to UAC groups for which access may be not allowed. For example, based on collaboration between CN (AMF) and RAN (gNB). e. If the gNB decides that the first UE may be admitted, e.g., on a specific band, or on any band, degradation actions may be taken while serving the first UE, such degradation actions may be one or more of: i) lower scheduling priority, delaying scheduling, potentially beyond specified QoS limits, ii) using a higher BLER target or residual error rate, iii) assigning less frequent Scheduling Request (SR) / PUCCH occasions, iv) bundling all UEs of the first UE type so that they may share same C-DRX onDuration and / or SSSG offset, v) limit / not use carrier aggregation or dual connectivity, vi) limit Tx chains usage (MIMO), vii) limit modulation (e.g. <64QAM), viii) limit TBS size, and ix) limit number of PRBs for PUSCH / PDSCH transmission.

[0156] In a seventh non-limiting example, the method of any of the preceding first-sixth nonlimiting examples, the treatment may be storing an identity, e.g., IMEI, IMEI / SV, IMEI / TAC, I MSI, any other type of standardized or proprietary identifier, or alike, information of first UE type in a first database. The contents of the first database may further be configured by an external NW node or an operator.

[0157] In an eight non-limiting example, the method of any of the preceding first-seventh nonlimiting examples, wherein upon new connections, the treatment may be retrieving information from said first database for potential identification of a first UE type.

[0158] In a ninth non-limiting example, the method of any of the preceding first-eighth nonlimiting examples, wherein the treatment may be storing identity, e.g., IMEI / IMEI_SV / IMEI_TAC, IMSI, any other type of standardized or proprietary identifier, or alike, information of UE in a second database for exemption handling. For example, UEs identified to be of a first type may be exempt from special treatment in case their identity matches the contents of a second database. Figure 3 depicts an example of the arrangement that the network node 111 may comprise to perform the method actions described above in relation to Figure 2. The network node 111 is for handling the first wireless device 131. The first network node 111 is configured to operate via the wireless communications network 100.

[0159] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the network node 111 and will thus not be repeated here. For example, the identity may be configured to be e.g., IMEI, IMEI / SV, IMEI / TAC, IMSI, any other type of standardized or proprietary identifier, or alike, information of the first type of the first wireless device 131, e.g. the first UE type.

[0160] In Figure 3, an optional unit is indicated with a dashed box.

[0161] The network node 111 is configured to perform the determining in Action 201 , e.g. by means of a processing circuitry 301 within the network node 111 configured to, determine the first type of the first wireless device 131 based on the inconsistency in the information configured to be provided by the first wireless device 131 configured to indicate the capability of the first wireless device 131.

[0162] The network node 111 is also be configured to perform the initiating in Action 203, e.g. by means of the processing circuitry 301 within the network node 111 configured to, initiate the one or more actions based on the result of the determination.

[0163] In some embodiments, the information may be configured to comprise one or more of: the one or more parameters and the one or more values configured to be indicative of the one or more of: one or more radio access capabilities, one or more radio frequency requirements, support for a specific band, the minimum channel bandwidth per band, the minimum number of receiver antenna ports per band, carrier aggregation support, dual connectivity support, type of wireless device, and accessStratumRelease capability.

[0164] In some embodiments, one of the following may apply: a) the type of wireless device configured to be comprised in the information may be different from the first type and inconsistent with the other one or more of: the one or more parameters and the one or more values configured to be comprised in the information, and b) the information may be configured to lack an explicit indication of the type of wireless device.

[0165] In some embodiments, one or more of the following may apply: a) the one or more first indications configured to be comprised in the information may be configured to correspond to a non-reduced capability wireless device, and the one or more second indications configured to be comprised in the information may be configured to correspond to a reduced capability wireless device, and b) the determined first type may be of a reduced capability wireless device.

[0166] In some embodiments, the one or more actions may be configured to comprise one of the following: a) handing over the first wireless device 131 to another network node 112, another cell 122, another radio access technology or another band, b) releasing the first wireless device 131 , c) assigning the first wireless device 131 to the group of wireless devices 133 for which access may be configured to be not allowed, c) assigning the first wireless device 131 to the slice with degraded quality of experience in comparison with the one or more second wireless devices 132 with non-reduced capability, d) admitting the first wireless device 131 as a wireless device having the determined first type, and e) admitting the first wireless device 131 with one or more degraded actions of: i) lowering the scheduling priority of the first wireless device 131 , ii) increasing the Block Error Rate or the residual error rate for the first wireless device 131 , iii) assigning fewer scheduling requests and Physical Uplink Control Channel occasions to the first wireless device 131, iv) bundling the group of wireless devices 133 to share one or more of: the Connected-mode Discontinuous Reception and the Search Space Set Group, v) limiting the carrier aggregation of the first wireless device 131 , vi) limiting usage of transmitter chains by the first wireless device 131, vii) limiting modulation for the first wireless device 131 , viii) limiting the transport block size for the first wireless device 131 , and limiting the number of resources for transmission for the first wireless device 131.

[0167] In some embodiments, the one or more actions may be configured to comprise admitting the first wireless device 131 in the first cell 121 wherein the network node 111 may be configured to be communicating with the first wireless device 131.

[0168] In some embodiments, the network node 111 may be configured to admit the first wireless device 131 in the first cell 121 as having the determined first type.

[0169] In some embodiments, one of the following may apply: a) the first type may be configured to be not allowed, supported or enabled in the first cell 121 , and b) the first type may be configured to be allowed, supported or enabled in the first cell 121.

[0170] In some embodiments, the network node 111 may be configured to hand over the reduced capability wireless device to operate in the another cell 122.

[0171] In some embodiments, the network node 111 may be configured to admit the reduced capability wireless device in the another cell 122 with the one or more degraded actions.

[0172] In some embodiments, the first type may be configured to be not allowed, supported or enabled in the first cell 121

[0173] In some embodiments, the network node 111 may be further configured with one or more of the following four configurations. The network node 111 may be configured to perform the assigning in Action 202, e.g. by means of the processing circuitry 301 within the network node 111 configured to, assign the first type configured to be determined to the first wireless device 131, and the one or more actions may be configured to be applied according to the assigned first type.

[0174] The network node 111 may be configured to perform the storing in Action 204, e.g. by means of the processing circuitry 301 within the network node 111 configured to, store the identity of the first wireless device 131 in the first database. The identity may be configured to be mapped to the one or more first capabilities in the first database.

[0175] The network node 111 may be configured to perform the retrieving in Action 206, e.g. by means of the processing circuitry 301 within the network node 111 configured to, retrieve the identity of the first wireless device 131 from the first database at a later time point.

[0176] The network node 111 may be configured to perform the storing in Action 205, e.g. by means of the processing circuitry 301 within the network node 111 configured to, store the identity of the first wireless device 131 in the second database to apply one or more exceptions to the first wireless device 131.

[0177] In some embodiments, the first type may be configured to be a rogue type.

[0178] In some embodiments, the information may be configured to be provided by the first wireless device 131 in one or more of: the capability report, the one or more measurement reports, the one or more reference signals, the identity of the first wireless device 131, previously mapped to the one or more first capabilities in the first database, and the identity of the first wireless device 131 lacking the corresponding identity in the second database.

[0179] The embodiments herein in the network node 111 may be implemented through one or more processors, such as a processing circuitry 301 in the network node 111 depicted in Figure 3a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node 111. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the network node 111.

[0180] The network node 111 may further comprise a memory 302 comprising one or more memory units. The memory 302 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the network node 111.

[0181] In some embodiments, the network node 111 may receive information from, e.g., the first wireless device 131 , the second network node 112, the second wireless device 132, any of the one or more third wireless devices 134 in the group of wireless devices 133, the first cell 121, the another cell 122, the virtual node 114, or another structure in the wireless communications network 100, through a receiving port 303. In some embodiments, the receiving port 303 may be, for example, connected to one or more antennas in network node 111. In other embodiments, the network node 111 may receive information from another structure in the wireless communications network 100 through the receiving port 303. Since the receiving port 303 may be in communication with the processing circuitry 301, the receiving port 303 may then send the received information to the processing circuitry 301. The receiving port 303 may also be configured to receive other information.

[0182] The processing circuitry 301 in the network node 111 may be further configured to transmit or send information to e.g., the first wireless device 131 , the second network node 112, the second wireless device 132, any of the one or more third wireless devices 134 in the group of wireless devices 133, the first cell 121 , the another cell 132, the virtual node 114, or another structure in the wireless communications network 100, through a sending port 304, which may be in communication with the processing circuitry 301, and the memory 302.

[0183] Those skilled in the art will also appreciate that the processing circuitry 301 described above may comprise a combination of analog and digital modules, and / or one or more processors configured with software and / or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processing circuitry 301 , perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

[0184] The processing circuitry 301 may be configured to, or operable to, perform the method actions according to Figure 2.

[0185] Also, in some embodiments, the network node 111 may be configured to perform the actions of Figure 2 with respective units that may be implemented as one or more applications running on one or more processors such as the processing circuitry 301.

[0186] Thus, the methods according to the embodiments described herein for the network node 111 may be respectively implemented by means of a computer program 305 product, comprising instructions, i.e., software code portions, which, when executed on at least one processing circuitry 301 , cause the at least one processing circuitry 301 to carry out the actions described herein, as performed by the network node 111. The computer program 305 product may be stored on a computer-readable storage medium 306. The computer- readable storage medium 306, having stored thereon the computer program 305, may comprise instructions which, when executed on at least one processing circuitry 301 , cause the at least one processing circuitry 301 to carry out the actions described herein, as performed by the network node 111. In some embodiments, the computer-readable storage medium 306 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 305 product may be stored on a carrier containing the computer program 305 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 306, as described above.

[0187] The network node 111 may comprise a communication interface configured to facilitate communications between the network node 111 and other nodes or devices, e.g., the first wireless device 131 , the second network node 112, the second wireless device 132, any of the one or more third wireless devices 134 in the group of wireless devices 133, the first cell 121, the another cell 132, the virtual node 114, or another structure in the wireless communications network 100. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0188] In other embodiments, the network node 111 may also comprise a radio circuitry 307, which may comprise e.g., the receiving port 303 and the sending port 304. The radio circuitry 307 may be configured to set up and maintain at least a wireless connection with the first wireless device 131 , the second network node 112, the second wireless device 132, any of the one or more third wireless devices 134 in the group of wireless devices 133, the first cell 121, the another cell 132, the virtual node 114, or another structure in the wireless communications network 100. Circuitry may be understood herein as a hardware component.

[0189] Hence, embodiments herein also relate to the network node 111 comprising the processing circuitry 301 and the memory 302, said memory 302 containing instructions executable by said processing circuitry 301 , whereby the network node 111 is operative to perform the actions described herein in relation to the network node 111, e.g., in Figure 2.

[0190] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description. As used herein, the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “and” term, may be understood to mean that only one of the list of alternatives may apply, more than one of the list of alternatives may apply or all of the list of alternatives may apply. This expression may be understood to be equivalent to the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “or” term.

[0191] EXAMPLES related to embodiments herein

[0192] The following are examples related to embodiments herein. Any of the features described in relation to Figures 1-3 may be combined with the actions of the examples related to embodiments herein, described in relation to Figure 4.

[0193] The network node 111 examples relate to Figure 4, Figure 3, and Figures 5-8.

[0194] A method, performed by a network node, such as the network node 111 is described herein. The method may be understood to be for handling a first wireless device such as the a first wireless device 131 . The network node 111 may operate in a wireless communications network, such as the wireless communications network 100.

[0195] In some examples, the wireless communications network 100 may support New Radio (NR).

[0196] The method may comprise one or more of the following actions. In some examples, all the actions may be performed. In some examples, Action 201 and Action 203 may be performed. One or more examples may be combined, where applicable. Components from one example may be tacitly assumed to be present in another example and it will be obvious to a person skilled in the art how those components may be used in the other exemplary examples. All possible combinations are not described to simplify the description. A nonlimiting example of the method performed by the network node 111 is depicted in Figure 4. In Figure 4, optional actions in some examples may be represented with dashed lines. In some examples, the actions may be performed in a different order than that depicted Figure 4.

[0197] The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the wireless device 130 and will thus not be repeated here to simplify the description. For example, the first information may comprise any of the first indication, the second indication and the third indication. o Determining 201 a first type of the first wireless device 131 . The network node 111 may be configured to perform the determining in this Action 201 .

[0198] Determining may be understood as calculating, deriving, or similar.

[0199] The first type may be, e.g., a UE type, such as RedCap UE or non-RedCap UE. The determining in this Action 201 may be based on an inconsistency in information provided by the wireless device 131. The information may indicate a capability of the wireless device 131. The wireless device 130 may operate in the wireless communications network 100.

[0200] The inconsistency may be, for example, a deviation, or a lack of correspondence, from an expected indication, e.g., value, parameter, signal or behavior.

[0201] The information may have been provided by the first wireless device 131 in a capability report.

[0202] The information may comprise one or more of: one or more parameters and one or more values indicative of one or more of the following:

[0203] - one or more radio access capabilities,

[0204] - one or more radio frequency requirements,

[0205] - support for a specific band,

[0206] - a minimum channel bandwidth, e.g., per band,

[0207] - a minimum number of receiver antenna ports, e.g., per band,

[0208] - carrier aggregation support,

[0209] - dual connectivity support,

[0210] - type of wireless device, e.g., UE type, and

[0211] - accessstratum Release capability.

[0212] In some examples, one of the following may apply:

[0213] - the type of wireless device comprised in the information may be different from the first type and inconsistent with the other one or more of: one or more parameters and / or one or more values comprised in the information, and

[0214] - the information may lack an explicit indication of the type of wireless device.

[0215] In some examples, one or more of the following may apply:

[0216] - one or more first indications comprised in the information may correspond to a non-reduced capability wireless device, e.g., non-reduced capability UE, and one or more second indications comprised in the information may correspond to a reduced capability wireless device, e.g., reduced capability UE, and

[0217] - the determined first type may be of a reduced capability wireless device, e.g., reduced capability UE.

[0218] The first type may be a type referred to herein as a rogue type. o Initiating 203 one or more actions. The network node 111 may be configured to perform the initiating in this Action 203.

[0219] Initiating may comprise starting or triggering.

[0220] The initiating of the one or more actions may be based on a result of the determination.

[0221] In some examples, the one or more actions may comprise one of the following: - handing over the first wireless device 131 to another network node 112, another cell 122, another radio access technology or another band; the another cell 122 may be served in some examples, by the network node 111,

[0222] - releasing the first wireless device 131 ; in some examples, the one or more actions may comprise a release with re-direct information, wherein the first wireless device 131 may be handed over via the wireless device 131 going via IDLE mode,

[0223] - assigning the first wireless device 131 to a group of wireless devices 133 for which access is not allowed,

[0224] - assigning the first wireless device 131 to a slice with degraded quality of experience in comparison with one or more second wireless devices 132 with non-reduced capability,

[0225] - admitting the first wireless device 131 as a wireless device having the determined first type, e.g., RedCap UE,

[0226] - admitting the first wireless device 131 with one or more degraded actions of: i. lowering a scheduling priority of the first wireless device 131, ii. increasing a Block Error Rate or a residual error rate for the first wireless device 131 , iii. assigning fewer scheduling requests and Physical Uplink Control Channel occasions to the first wireless device 131 , iv. bundling the group of wireless devices 133 to share one or more of: a Connected-mode Discontinuous Reception and a Search Space Set Group, v. limiting carrier aggregation of the first wireless device 131, vi. limiting usage of transmitter chains by the first wireless device 131, vii. limiting modulation for the first wireless device 131 , viii. limiting transport block size for the first wireless device 131 , and ix. limiting a number of resources for transmission for the first wireless device 131.

[0227] In a first group of examples, the one or more actions may comprise admitting the first wireless device 131 in the first cell 121 wherein the network node 111 may be communicating with the first wireless device 131.

[0228] In some of the examples in the first group, the first wireless device 131 may be admitted in the first cell 121 as having the determined first type, e.g., RedCap UE.

[0229] In some of these examples in the first group, one of the following may apply:

[0230] - the first type is not allowed, supported or enabled in the first cell 121 , and

[0231] - the first type is allowed, supported or enabled in the first cell 121. In some examples a second group of examples, the reduced capability wireless device, e.g., reduced capability UE, may be handed over to operate in the another cell 122.

[0232] In some examples in the second group, the reduced capability wireless device, e.g., reduced capability UE, may be admitted in the another cell 122 with the one or more degraded actions.

[0233] In some examples in the second group of examples, the first type may be not allowed, supported or enabled in the first cell 121.

[0234] In some examples, the method may further comprise one or more of the following four actions: o Assigning 202 the determined first type to the first wireless device 131.

[0235] The network node 111 may be configured to perform the assigning in this Action 202.

[0236] The one or more actions may be applied according to the assigned first type. o Storing 204 an identity of the first wireless device 131 in a first database.

[0237] The network node 111 may be configured to perform the storing in this Action 204.

[0238] The identity may be mapped to the one or more first capabilities in the first database. o Retrieving 206 the identity of the first wireless device 131 from the first database at a later time point. The network node 111 may be configured to perform the retrieving in this Action 206. o Storing 205 the identity of the first wireless device 131 in a second database. The network node 111 may be configured to perform the storing in this Action 205.

[0239] The storing in this Action 205 of the identity of the first wireless device 131 in a second database may be to apply one exceptions to the first wireless device 131.

[0240] The information may be provided by the first wireless device 131 in one or more of the following:

[0241] - the capability report,

[0242] - one or more measurement reports,

[0243] - one or more reference signals,

[0244] - the identity of the first wireless device 131, previously mapped to the one or more first capabilities in the first database,

[0245] - the identity of the first wireless device 131 lacking a corresponding identity in the second database.

[0246] In Figure 3, optional units are indicated with dashed boxes.

[0247] The network node 111 may comprise an arrangement as shown in Figure 3 or in Figure

[0248] 7.

[0249] Selected examples of embodiments herein may be as follows. Example 1. A method performed by a network node (111), the method being for handling a first wireless device (131), the network node (111) operating via a wireless communications network (100), the method comprising:

[0250] - determining (201) a first type of the first wireless device (131) based on an inconsistency in information provided by the wireless device (131) indicating a capability of the wireless device (131), and

[0251] - initiating (203) one or more actions based on a result of the determination.

[0252] Example 2. The method according to example 1, wherein the information comprises one or more of: one or more parameters and one or more values indicative of one or more of:

[0253] - one or more radio access capabilities,

[0254] - one or more radio frequency requirements,

[0255] - support for a specific band,

[0256] - a minimum channel bandwidth per band,

[0257] - a minimum number of receiver antenna ports per band

[0258] - carrier aggregation support,

[0259] - dual connectivity support,

[0260] - type of wireless device, e.g., UE type, and

[0261] - accessstratum Release capability.

[0262] Example 3. The method according to example 2, wherein one of:

[0263] - the type of wireless device comprised in the information is different from the first type and inconsistent with the other one or more of: one or more parameters and one or more values comprised in the information, and

[0264] - the information lacks an explicit indication of the type of wireless device.

[0265] Example 4. The method according to any of examples 1-3, wherein one or more of:

[0266] - one or more first indications comprised in the information correspond to a nonreduced capability wireless device, e.g., non-reduced capability UE, and one or more second indications comprised in the information correspond to a reduced capability wireless device, e.g., reduced capability UE, and

[0267] - the determined first type is of a reduced capability wireless device, e.g., reduced capability UE.

[0268] Example 5. The method according to any of examples 1-4, wherein the one or more actions comprise one of: - handing over the first wireless device (131) to another network node (112), another cell (122), another radio access technology or another band,

[0269] - releasing the first wireless device (131),

[0270] - assigning the first wireless device (131) to a group of wireless devices (133) for which access is not allowed,

[0271] - assigning the first wireless device (131) to a slice with degraded quality of experience in comparison with one or more second wireless devices (132) with non-reduced capability,

[0272] - admitting the first wireless device (131) as a wireless device having the determined first type, e.g., RedCap UE,

[0273] - admitting the first wireless device (131) with one or more degraded actions of: i. lowering a scheduling priority of the first wireless device (131), ii. increasing a Block Error Rate or a residual error rate for the first wireless device (131), iii. assigning fewer scheduling requests and Physical Uplink Control Channel occasions to the first wireless device (131), iv. bundling the group of wireless devices (133) to share one or more of: a Connected-mode Discontinuous Reception and a Search Space Set Group, v. limiting carrier aggregation of the first wireless device (131), vi. limiting usage of transmitter chains by the first wireless device (131), vii. limiting modulation for the first wireless device (131), viii. limiting transport block size for the first wireless device (131), and ix. limiting a number of resources for transmission for the first wireless device (131).

[0274] Example 6. The method according to any of examples 1-4, wherein the one or more actions comprise admitting the first wireless device (131) in a first cell (121) wherein the network node (111) is communicating with the first wireless device (131).

[0275] Example 7. The method according to example 6, wherein the first wireless device (131) is admitted in the first cell (121) as having the determined first type, e.g., RedCap UE.

[0276] Example 8. The method according to any of examples 6-7, wherein one of: the first type is not allowed, supported or enabled in the first cell (121), and the first type is allowed, supported or enabled in the first cell (121). Example 9. The method according to examples 4 and 5, wherein the reduced capability wireless device, e.g., reduced capability UE, is handed over to operate in the another cell (122).

[0277] Example 10. The method according to example 9, wherein the reduced capability wireless device, e.g., reduced capability UE, is admitted in the another cell (122) with the one or more degraded actions.

[0278] Example 11. The method according to any of examples 9-10, wherein the first type is not allowed, supported or enabled in the first cell (121).

[0279] Example 12. The method according to any of examples 1-11, further comprising one or more of:

[0280] - assigning (202) the determined first type to the first wireless device (131), and wherein the one or more actions are applied according to the assigned first type,

[0281] - storing (204) an identity of the first wireless device (131) in a first database, wherein the identity is mapped to the one or more first capabilities in the first database,

[0282] - retrieving (206) the identity of the first wireless device (131) from the first database at a later time point, and

[0283] - storing (205) the identity of the first wireless device (131) in a second database to apply one exceptions to the first wireless device (131).

[0284] Example 13. The method according to any of examples 1-12, wherein the first type is a rogue type.

[0285] Example 14. The method according to any of examples 12-13, wherein the information is provided by the first wireless device (131) in one or more of:

[0286] - a capability report,

[0287] - one or more measurement reports,

[0288] - one or more reference signals,

[0289] - the identity of the first wireless device (131), previously mapped to the one or more first capabilities in the first database, the identity of the first wireless device (131) lacking a corresponding identity in the second database.

[0290] Figure 4 is a flowchart depicting a method in the network node 111 , according to a nonlimiting example associated to embodiments herein. The actions depicted correspond to those described in Figure 2. In Figure 4, optional actions are represented with dashed lines. In some examples, the actions may be performed in a different order than that depicted Figure 4.

[0291] Further Extensions And Variations

[0292] Figure 5 shows an example of a communication system 500 in accordance with some embodiments.

[0293] In the example, the communication system 500, such as the wireless communications network 100, includes a telecommunication network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes, such as the network node 111 , such as network nodes 510a and 510b (one or more of which may be generally referred to as network nodes 510), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 502 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 502, including one or more network nodes 510 and / or core network nodes 508.

[0294] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 510 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 512a, 512b, 512c, and 512d (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections. Any of the UEs 512a, 512b, 512c, and 512d are examples of any of the first wireless device 131 , the second wireless device 132 and the one or more third wireless devices 134 in the group of wireless devices 133.

[0295] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0296] Any of the first wireless device 131 , the second wireless device 132 and the one or more third wireless devices 134 in the group of wireless devices 133, exemplified in Figure 5 as the UEs 512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network node 111 , exemplified in Figure 5 as network nodes 510 and other communication devices. Similarly, the network nodes 510 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 512 and / or with other network nodes or equipment in the telecommunication network 502 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 502.

[0297] In the depicted example, the core network 506 connects the network nodes 510 to one or more host computing systems, such as host 516. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 506 includes one more core network nodes (e.g., core network node 508) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0298] The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and / or the telecommunication network 502. The host 516 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0299] As a whole, the communication system 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0300] In some examples, the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunications network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0301] In some examples, the UEs 512 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0302] In the example, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512c and / or 512d) and network nodes (e.g., network node 510b). In some examples, the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 510, or by executable code, script, process, or other instructions in the hub 514. As another example, the hub 514 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 514 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0303] The hub 514 may have a constant / persistent or intermittent connection to the network node 510b. The hub 514 may also allow for a different communication scheme and / or schedule between the hub 514 and UEs (e.g., UE 512c and / or 512d), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and / or one or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to an M2M service provider over the access network 504 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 510b. In other embodiments, the hub 514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 510b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0304] Figure 6 shows a UE 600 in accordance with some embodiments. The UE 600 presents additional details of some embodiments of the UE 512 of Figure 1 . As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0305] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0306] The UE 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input / output interface 606, a power source 608, a memory 610, a communication interface 612, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 6. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0307] The processing circuitry 602 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 610. The processing circuitry 602 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 602 may include multiple central processing units (CPUs).

[0308] In the example, the input / output interface 606 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 600. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0309] In some embodiments, the power source 608 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 608 may further include power circuitry for delivering power from the power source 608 itself, and / or an external power source, to the various parts of the UE 600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 608. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 608 to make the power suitable for the respective components of the UE 600 to which power is supplied.

[0310] The memory 610 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 610 includes one or more application programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616. The memory 610 may store, for use by the UE 600, any of a variety of various operating systems or combinations of operating systems.

[0311] The memory 610 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated IIICC (illlCC) or a removable IIICC commonly known as ‘SIM card.’ The memory 610 may allow the UE 600 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 610, which may be or comprise a device-readable storage medium.

[0312] The processing circuitry 602 may be configured to communicate with an access network or other network using the communication interface 612. The communication interface 612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 622. The communication interface 612 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 618 and / or a receiver 620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g., antenna 622) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0313] In the illustrated embodiment, communication functions of the communication interface 612 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0314] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 612, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0315] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0316] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 600 shown in Figure 6.

[0317] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0318] In practice, any number of UEs may be used together with respect to a single example. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. Figure 7 shows a network node 700 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0319] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0320] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0321] The network node 700 includes a processing circuitry 702, a memory 704, a communication interface 706, and a power source 708. The network node 700 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 700 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 704 for different RATs) and some components may be reused (e.g., a same antenna 710 may be shared by different RATs). The network node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 700.

[0322] The processing circuitry 702 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 700 components, such as the memory 704, to provide network node 700 functionality.

[0323] In some embodiments, the processing circuitry 702 includes a system on a chip (SOC). In some embodiments, the processing circuitry 702 includes one or more of radio frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714. In some embodiments, the radio frequency (RF) transceiver circuitry 712 and the baseband processing circuitry 714 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 712 and baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units.

[0324] The memory 704 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 702. The memory 704 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 702 and utilized by the network node 700. The memory 704 may be used to store any calculations made by the processing circuitry 702 and / or any data received via the communication interface 706. In some embodiments, the processing circuitry 702 and memory 704 is integrated.

[0325] The communication interface 706 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 706 comprises port(s) / terminal(s) 716 to send and receive data, for example to and from a network over a wired connection. The communication interface 706 also includes radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, the antenna 710. Radio front-end circuitry 718 comprises filters 720 and amplifiers 722. The radio front-end circuitry 718 may be connected to an antenna 710 and processing circuitry 702. The radio front-end circuitry may be configured to condition signals communicated between antenna 710 and processing circuitry 702. The radio front-end circuitry 718 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 720 and / or amplifiers 722. The radio signal may then be transmitted via the antenna 710. Similarly, when receiving data, the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718. The digital data may be passed to the processing circuitry 702. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0326] In certain alternative embodiments, the network node 700 does not include separate radio front-end circuitry 718, instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes one or more ports or terminals 716, the radio frontend circuitry 718, and the RF transceiver circuitry 712, as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).

[0327] The antenna 710 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 710 may be coupled to the radio front-end circuitry 718 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 710 is separate from the network node 700 and connectable to the network node 700 through an interface or port.

[0328] The antenna 710, communication interface 706, and / or the processing circuitry 702 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 710, the communication interface 706, and / or the processing circuitry 702 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0329] The power source 708 provides power to the various components of network node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein. For example, the network node 700 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708. As a further example, the power source 708 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0330] Embodiments of the network node 700 may include additional components beyond those shown in Figure 7 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 700 may include user interface equipment to allow input of information into the network node 700 and to allow output of information from the network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 700. In some embodiments providing a core network node, such as core network node 108 of FIG. 5, some components, such as the radio front-end circuitry 718 and the RF transceiver circuitry 712 may be omitted.

[0331] Figure 8 is a block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0332] Applications 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0333] Hardware 804 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 808a and 808b (one or more of which may be generally referred to as VMs 808), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to the VMs 808.

[0334] The VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0335] In the context of NFV, a VM 808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 808, and that part of hardware 804 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 808 on top of the hardware 804 and corresponds to the application 802.

[0336] Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization. Alternatively, hardware 804 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 810, which, among others, oversees lifecycle management of applications 802. In some embodiments, hardware 804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units.

[0337] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0338] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0339] The network node 111 embodiments relate to Figure 2, Figure 3, and Figures 5-8.

[0340] The network node 111 may comprise an arrangement as shown in Figure 3 or in Figure 7.

[0341] REFERENCES

[0342] 1. 3GPP TS 38.101 V18.7.0.

[0343] 2. https: / / www.ericsson.eom / en / blog / 2021 / 2 / reduced-cap-nr.

[0344] 3. 3GPP TS 38.331 V18.3.0.

[0345] 4. 3GPP TS 38.413 V18.3.0.

[0346] 5. 3GPP TS 38.306 V18.3.0.

Claims

1. 53CLAIMS:

1. A method performed by a network node (111), the method being for handling a first wireless device (131), the network node (111) operating via a wireless communications network (100), the method comprising:- determining (201) a first type of the first wireless device (131) based on an inconsistency in information provided by the first wireless device (131) indicating a capability of the first wireless device (131), and- initiating (203) one or more actions based on a result of the determination.

2. The method according to claim 1, wherein the information comprises one or more of: one or more parameters and one or more values indicative of one or more of:- one or more radio access capabilities,- one or more radio frequency requirements,- support for a specific band,- a minimum channel bandwidth per band,- a minimum number of receiver antenna ports per band,- carrier aggregation support,- dual connectivity support,- type of wireless device, and- accessstratum Release capability.

3. The method according to claim 2, wherein one of:- the type of wireless device comprised in the information is different from the first type and inconsistent with the other one or more of: one or more parameters and one or more values comprised in the information, and- the information lacks an explicit indication of the type of wireless device.

4. The method according to any of claims 1-3, wherein one or more of:- one or more first indications comprised in the information correspond to a nonreduced capability wireless device, and one or more second indications comprised in the information correspond to a reduced capability wireless device, and- the determined first type is of a reduced capability wireless device.

545. The method according to any of claims 1-4, wherein the one or more actions comprise one of:- handing over the first wireless device (131) to another network node (112), another cell (122), another radio access technology or another band,- releasing the first wireless device (131),- assigning the first wireless device (131) to a group of wireless devices (133) for which access is not allowed,- assigning the first wireless device (131) to a slice with degraded quality of experience in comparison with one or more second wireless devices (132) with non-reduced capability,- admitting the first wireless device (131) as a wireless device having the determined first type, and- admitting the first wireless device (131) with one or more degraded actions of: i. lowering a scheduling priority of the first wireless device (131), ii. increasing a Block Error Rate or a residual error rate for the first wireless device (131), iii. assigning fewer scheduling requests and Physical Uplink Control Channel occasions to the first wireless device (131), iv. bundling the group of wireless devices (133) to share one or more of: a Connected-mode Discontinuous Reception and a Search Space Set Group, v. limiting carrier aggregation of the first wireless device (131), vi. limiting usage of transmitter chains by the first wireless device (131), vii. limiting modulation for the first wireless device (131), viii. limiting transport block size for the first wireless device (131), and ix. limiting a number of resources for transmission for the first wireless device (131).

6. The method according to any of claims 1-4, wherein the one or more actions comprise admitting the first wireless device (131) in a first cell (121) wherein the network node (111) is communicating with the first wireless device (131).

7. The method according to claim 6, wherein the first wireless device (131) is admitted in the first cell (121) as having the determined first type.

8. The method according to any of claims 6-7, wherein one of:55 the first type is not allowed, supported or enabled in the first cell (121), and the first type is allowed, supported or enabled in the first cell (121).

9. The method according to claims 4 and 5, wherein the reduced capability wireless device, is handed over to operate in the another cell (122).

10. The method according to claim 9, wherein the reduced capability wireless device, is admitted in the another cell (122) with the one or more degraded actions.

11. The method according to any of claims 9-10, wherein the first type is not allowed, supported or enabled in the first cell (121).

12. The method according to any of claims 1-11, further comprising one or more of:- assigning (202) the determined first type to the first wireless device (131), and wherein the one or more actions are applied according to the assigned first type,- storing (204) an identity of the first wireless device (131) in a first database, wherein the identity is mapped to one or more first capabilities in the first database,- retrieving (206) the identity of the first wireless device (131) from the first database at a later time point, and- storing (205) the identity of the first wireless device (131) in a second database to apply one or more exceptions to the first wireless device (131).

13. The method according to any of claims 1-12, wherein the first type is a rogue type.

14. The method according to any of claims 12-13, wherein the information is provided by the first wireless device (131) in one or more of:- a capability report,- one or more measurement reports,- one or more reference signals,- the identity of the first wireless device (131), previously mapped to the one or more first capabilities in the first database, and- the identity of the first wireless device (131) lacking a corresponding identity in the second database.5615. A network node (111), for handling a first wireless device (131), the network node (111) being configured to operate via a wireless communications network (100), the network node (111) being further configured to:- determine a first type of the first wireless device (131) based on an inconsistency in information configured to be provided by the first wireless device (131) configured to indicate a capability of the first wireless device (131), and- initiate one or more actions based on a result of the determination.

16. The network node (111) according to claim 15, wherein the information is configured to comprise one or more of: one or more parameters and one or more values configured to be indicative of one or more of:- one or more radio access capabilities,- one or more radio frequency requirements,- support for a specific band,- a minimum channel bandwidth per band,- a minimum number of receiver antenna ports per band,- carrier aggregation support,- dual connectivity support,- type of wireless device, and- accessstratum Release capability.

17. The network node (111) according to claim 16, wherein one of:- the type of wireless device configured to be comprised in the information is different from the first type and inconsistent with the other one or more of: one or more parameters and one or more values configured to be comprised in the information, and- the information is configured to lack an explicit indication of the type of wireless device.

18. The network node (111) according to any of claims 15-17, wherein one or more of:- one or more first indications configured to be comprised in the information are configured to correspond to a non-reduced capability wireless device, and one or more second indications configured to be comprised in the information are configured to correspond to a reduced capability wireless device, and- the determined first type is of a reduced capability wireless device.

19. The network node (111) according to any of claims 15-18, wherein the one or more actions are configured to comprise one of:- handing over the first wireless device (131) to another network node (112), another cell (122), another radio access technology or another band,- releasing the first wireless device (131),- assigning the first wireless device (131) to a group of wireless devices (133) for which access is configured to be not allowed,- assigning the first wireless device (131) to a slice with degraded quality of experience in comparison with one or more second wireless devices (132) with non-reduced capability,- admitting the first wireless device (131) as a wireless device having the determined first type, and- admitting the first wireless device (131) with one or more degraded actions of: i. lowering a scheduling priority of the first wireless device (131), ii. increasing a Block Error Rate or a residual error rate for the first wireless device (131), iii. assigning fewer scheduling requests and Physical Uplink Control Channel occasions to the first wireless device (131), iv. bundling the group of wireless devices (133) to share one or more of: a Connected-mode Discontinuous Reception and a Search Space Set Group, v. limiting carrier aggregation of the first wireless device (131), vi. limiting usage of transmitter chains by the first wireless device (131), vii. limiting modulation for the first wireless device (131), viii. limiting transport block size for the first wireless device (131), and ix. limiting a number of resources for transmission for the first wireless device (131).

20. The network node (111) according to any of claims 15-18, wherein the one or more actions are configured to comprise admitting the first wireless device (131) in a first cell (121) wherein the network node (111) is configured to be communicating with the first wireless device (131).

21. The network node (111) according to claim 20, wherein the network node (111) is configured to admit the first wireless device (131) in the first cell (121) as having the determined first type.

22. The network node (111) according to any of claims 20-21, wherein one of:- the first type is configured to be not allowed, supported or enabled in the first cell (121), and- the first type is configured to be allowed, supported or enabled in the first cell (121).

23. The network node (111) according to claims 18 and 19, wherein the network node (111) is configured to hand over the reduced capability wireless device to operate in the another cell (122).

24. The network node (111) according to claim 23, wherein the network node (111) is configured to admit the reduced capability wireless device in the another cell (122) with the one or more degraded actions.

25. The network node (111) according to any of claims 23-24, wherein the first type is configured to be not allowed, supported or enabled in the first cell (121).

26. The network node (111) according to any of claims 15-25, further configured to one or more of:- assign the first type configured to be determined to the first wireless device (131), and wherein the one or more actions are configured to be applied according to the assigned first type,- store an identity of the first wireless device (131) in a first database, wherein the identity is configured to be mapped to one or more first capabilities in the first database,- retrieve the identity of the first wireless device (131) from the first database at a later time point, and- store the identity of the first wireless device (131) in a second database to apply one or more exceptions to the first wireless device (131).

27. The network node (111) according to any of claims 15-26, wherein the first type is configured to be a rogue type.

28. The network node (111) according to any of claims 26-27, wherein the information is configured to be provided by the first wireless device (131) in one or more of:- a capability report,- one or more measurement reports,- one or more reference signals,- the identity of the first wireless device (131), previously mapped to the one or more first capabilities in the first database, and - the identity of the first wireless device (131) lacking a corresponding identity in the second database.

29. A computer program (305), comprising instructions which, when executed on at least one processing circuitry (301), cause the at least one processing circuitry (301) to carry out the method according to any of claims 1-14.

30. A computer-readable storage medium (306), having stored thereon a computer program (305), comprising instructions which, when executed on at least one processing circuitry (301), cause the at least one processing circuitry (301) to carry out the method according to any of claims 1-14.

Images