WO2018206999A1

WO2018206999A1 - Handling of data limits in machine-to-machine communications network

Info

Publication number: WO2018206999A1
Application number: PCT/IB2017/052707
Authority: WO
Inventors: George Foti; Ankur DAUNERIA
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2017-05-09
Filing date: 2017-05-09
Publication date: 2018-11-15

Abstract

An M2M monitoring entity for managing registration lifecycle of one or more loT/M2M entity when the underlying network used to provide data transmission exercise a temporary data speed restriction is provided. The M2M monitoring entity creates entries comprising a priority level for each registered loT entity associated to a subscription. Upon receiving information that temporary data speed restriction (fair usage policy) is applied by the underlying network to the subscription, the M2M monitoring entity determines which loT entity to deregister and which loT entity for which data transmission should be suspended based on the priority level and potentially the minimum data speed required by the loT entity.

Description

HANDLING OF DATA LIMITS IN MACHINE-TO-MACHINE COMMUNICATIONS

NETWORK

Technical Field

[0001] This disclosure relates generally to management of entity registration lifecycle.

Background

[0002] The concept of fair usage policy, FUP, is used by broadband or packet data network operators or internet service provider to make sure that a few customers who were heavy users didn't fill up the available bandwidth, thus negatively impacting the overall experience for the majority of the users of the same network.

[0003] Smartphones or any other user devices, as used daily, consume a large amount of data, via social applications, streaming videos from YouTube, voice and video chatting, and gaming and the likes. For example, Skype is a wildly used application offering an over the top communication service. A Skype-to-Skype call for 60 seconds could take 3MB, so a 30

minutes Skype call could use 90MB of data. Browsing Web pages and social media websites may consume about another 100MB, while emailing and doing other work Web-based applications may use about 100MB more.

Additionally, average users consume around 200 MB of data when streaming audio and video.

[0004] When operators advertise "unlimited data" as a broadband package, FUP could apply by lowering the Internet speeds after a certain determined limit or threshold is reached. FUP may be applied differently by different operators. FUP could be applicable on all "unlimited" data transfer plans. The data transfer continues to be unlimited, albeit at reduced speeds after FUP is applied. Like mentioned before, FUP limits are imposed to ensure that the best quality of broadband is available to the maximum number of internet users. For example, a user with unlimited data plan can be provided with unlimited data transfer at 100Mb/s, but after reaching a determined limit or threshold the data speed is reduced to 512 kb/s. [0005] As FUP is applied for data transfers associated to a subscription, it is expected to impact data communications from users to users, users-to- servers, but also Machine to Machine, M2M, data communications powering the Internet of Things, loT.

Summary

[0006] Broadband users are expected to have connected devices (e.g.,

wearables, connected camera, connected home, home surveillance, etc.) in addition to typical communication devices such as smartphones, tablets, computers, portable devices, etc). Broadband users typically have broadband subscription with an ISP and/or a broadband operator. The subscription may be "unlimited" data plan, i.e., unlimited data transfer but data speed may however vary depending on the network policy, resources of the ISP or of the broadband operator. As data transfer is unlimited, and users and devices consume more and more data, broadband operators and ISPs require to reduce the speed of transmission to allow more users and devices to be connected and transmit data in the network. This is referred to as fair usage policy, FUP, and is applied by many broadband operators and ISPs due to resource limitations.

[0007] Connected devices at home used in healthcare remote monitoring

(patient @home) or video surveillance application, etc. require data transfer to a destination node for processing, control and monitoring. Some applications are critical while some are not. In particular, healthcare applications are critical as it deals with patient health. Such applications require a reliable connection through the underlying network and require a minimum

transmission delay to provide continuous uninterrupted remote monitoring. When FUP is applied, registration of critical application and devices should be maintained, while registration of non-critical application that consume large amount of data that may leave the other applications starving for resources may either be suspended or released. Hence, when FUP is applied, it may impact operation of some of the connected devices applications.

Embodiments in this disclosure manage the registration lifecycle of one or more loT/M2M devices associated to a single subscription that undergoes FUP where one or more IOT devices are deregistered or temporarily suspended.

[0008] In one aspect, a method executed by an M2M monitoring server of controlling a registration status of one or more Internet of thing, loT, entity, associated to a common subscription comprises creating an entry for each registered loT entity associated with the common subscription, the entry comprises associated identities and a priority level for each of the registered loT entity. It may also comprise identity of the registrar CSE to which the one or more loT entity registered, quality of service characteristics such as the minimum required data speed for each of the registered loT entity. The method further comprises obtaining data transfer threshold information indicative that a data limit for the subscription is reached, the information comprises an updated data rate limit to be applied, due to FUP, to each of the registered loT entity associated with the common subscription. Furthermore, the method further comprises the step of determining the one or more registered loT entity to deregister based on the data transfer threshold information and entry data such as priority level and minimum data rate as well as determining the one or more registered loT entity to suspend based on the same information. Finally, the method comprises the step of sending one or more instruction indicating deregistration or suspension data transmission of the one or more registered loT entity.

[0009] In accordance with one embodiment, the entry further comprises a registration status that may indicate the registration status of the one or more registered loT entity, such as "registered", suspended", etc.

[0010] In accordance with one embodiment, the priority level and optionally the minimum data rate required for normal operation of the one or more registered loT entity are used in determining the one or more registered loT entity to deregister or suspend data transmission.

[0011] In accordance with an embodiment, the method further includes the step of sending one or more instruction indicating data transmission to be deregistered or suspended for the one or more registered loT entity. If the instruction relates to an instruction to suspend data transmission, it may include a suspension timer. [0012] In accordance with an embodiment, the M2M monitoring server receives a confirmation that the one or more registered loT entity is successfully deregistered and removing the corresponding entry associated with the one or more loT entity that is deregistered.

[0013] In another embodiment, the M2M monitoring server receives a

confirmation that the one or more registered loT entity is successfully suspended, at which point, the entry for the one or more registered loT entity that is suspended is maintained. The confirmation may include an updated suspension timer.

[0014] In an embodiment, the M2M Monitoring server monitors changes in the received data transfer threshold information and if for example the FUP is lifted by the underlying network provider, a notification to resume data transfer for the one or more registered loT entity in suspended mode is transmitted.

[0015] In one embodiment, the one or more registered loT entity is at least one of an application entity, AE, a common service entity, CSE, a dedicated application node, ADN, an application service node, ASN, and a middle node, MN as specified in oneM2M technical specification TS-0001-V2.10.0:

Functional Architecture. Brief Description of the Drawings

[0016] Embodiments of the present invention will now be described, by way of example only, with reference to the attached Figures, wherein:

[0017] Figure 1 (Prior art) is a schematic illustration of the OneM2M

architecture.

[0018] Figure 2 (Prior art) illustrates a conceptual implementation example of the oneM2M architecture.

[0019] Figure 3 (Prior art) illustrates a registration call flow of entities within the OneM2M architecture.

[0020] Figure 4 illustrates an example of an loT deployment in a user's home.

[0021] Figure 5 illustrates an example of a fair usage plan that may be offered in a subscription.

[0022] Figure 6 (prior art) illustrates a table of typical loT use cases with

corresponding characteristics. [0023] Figure 7 illustrates a procedure for registration of one or more loT entity according to an embodiment.

[0024] Figure 8 illustrates a procedure for detecting data limit reached for one or more loT entity and taking appropriate actions based on the loT application according to an embodiment.

[0025] Figure 9 illustrates a method for managing M2M registration lifecycle at a traffic monitoring server according to an embodiment.

[0026] Figure 10 illustrates a schematic illustration of a traffic monitoring

server, according to an embodiment.

[0027] Figure 1 1 illustrates a schematic illustration of a traffic monitoring

server, according to another embodiment.

Detailed Description

[0028] The following acronyms are used throughout this disclosure.

5G 5^th Generation

3GPP 3^rd Generation Partnership Project

ADN Application Dedicated Node

ADSL Asymmetric DSL

AE Application Entity

AN Access Network

ASN Application Service Node

CN Core Network

CPE customer-premise equipment

CSE Common Service Entity

DL Downlink

DSL Digital subscriber Line

GPRS General Packet Radio System

FUP Fair Usage Policy

IN Infrastructure Node

loT Internet of Things

ISP Internet Service Provider

LEE laptop-mounted equipment

LME laptop-embedded equipment

LTE Long Term Evolution M2M Machine to Machine

MN Middle Node

NB-loT Narrow Band loT

NSE Network Service Entity

PDA Personal Data Assistant

SP Service provider

UN Underlying Network

UL Uplink

WiFi Wireless Fidelity

[0029] The various features of the invention will now be described with

reference to the figures. These various aspects are described hereafter in greater detail in connection with exemplary embodiments and examples to facilitate an understanding of the invention, but should not be construed as limited to these embodiments. Rather, these embodiments are provided so that the disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0030] Many aspects of the invention are described in terms of sequences of actions or functions to be performed by elements of a computer system or other hardware capable of executing programmed instructions. It will be recognized that the various actions could be performed by specialized circuits, by program instructions being executed by one or more processors, or by a combination of both. Moreover, the invention can additionally be considered to be embodied entirely within any form of computer readable carrier or carrier wave containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.

[0031] FUP is known to be applied for communication and data transfer,

gaming, streaming, etc. from user's smartphone, tablets, computers, etc. If the user with the broadband plan subscription has multiple devices, the data consumption may further increase, especially if shared among the household members. Additionally, with the user having more connected devices including devices at home or car, etc. the data consumption is expected to increase, hence more bandwidth and higher rates could be consumed at a time under the user broadband plan owning the devices. If FUP is applied, it would likely impact all applications running under the user subscription including the user's connected devices. Figure 5 illustrates an example of a FUP that could be applied to an unlimited data broadband subscription. The data speed is reduced after a certain data usage limit is reached during the month. The user can still send and receive data but at a much lower speed until the start of a new month cycle.

[0032] Embodiments of this disclosure apply whenever FUP is applied to any broadband subscription (residential, commercial, enterprise, etc.) that comprise M2M communication.

[0033] Embodiments will be described by means of the OneM2M system 100, as illustrated in Figure 1 (prior art), using terminology which is taken from the oneM2M standards. It is however understood that this invention is applicable to any M2M or loT system. Additionally, M2M and loT are used

interchangeably when describing the embodiments of this disclosure.

[0034] oneM2M illustrated in Figure 1 (Prior art) is a global standards initiative for Machine to Machine communications and the Internet of Things. OneM2M specifies an access independent architecture as illustrated in Figure 1. It defines and supports M2M communications and management system that can be readily embedded within various hardware and software and contributes to connecting the billions of devices in the field with M2M application servers worldwide, powering the loT.

[0035] OneM2M specifications provide a common means for M2M service providers, M2M SPs, to support applications and services as diverse as:

• The smart grid

· The connected car

• Home automation

• Energy management

• Enterprise supply chain

• Public safety

· eHealth and telemedicine

[0036] OneM2M considers any loT deployment to be comprised of two

domains: the field domain and infrastructure domain as illustrated in Figure 2 (prior art). The field domain includes the loT (e.g., sensors, actuators, etc.) and gateways, whereas the infrastructure domain includes the communication networks that include access and core networks as well as data centers. From a functional perspective, each of these domains include three types of entities: an application entity, AE, a common service entity, CSE and a network service entity, NSE as illustrated in Figure 1 (Prior art).

[0037] An AE provides application logic for the end-to-end M2M solutions. It implements the vertical-specific application logic and may reside on one or multiple physical nodes in the deployment. Examples of AEs comprise: fleet tracking application, blood sugar monitoring application, power metering application, home automation, etc.

[0038] A CSE is a middleware layer that sits between AEs and underlying network services (NSE). The CSE provides the set of "service functions" that are common to the M2M environments. Example of CSE service functions include but not limited to identity management of the entities (AEs, CSEs, NSEs), registration (AE-CSE and CSE to CSE registration), discovery of entities and resources, security, group management device management, subscribe/notify, abstraction of the underlying network interface,

communication management such as selection of communication channels, scheduling, store and forward, reachability status awareness, etc. and location management.

[0039] The Network Service Entity, NSE, of Figure 1 is part of the underlying network, UN, which may consist of 3GPP core network, such as Evolved Packet Core, EPC, or 5G core network or GPRS or the like and include wireless or wired access network such as LTE, WiFi, aDSL, cable, and the like. The Network Service entity, NSE, provides services to the CSE such as QoS, device management, location services, device triggering, etc. The NSE is abstracted from the AEs by the CSEs. In fact, the oneM2M is access independent and can operate under various access and core networks. The underlying network connecting the field domain to the infrastructure domain is typically operated by an internet service provider, ISP, or a network operator (e.g., broadband operator) providing access and core network infrastructure facilitating communications between the application layer and service layer in the field domain and application layer and service layer in the infrastructure domain. [0040] As illustrated in Figure 2 (Prior art), oneM2M identifies five different types of oneM2M logical nodes:

- Application Service Node, ASN: contains one CSE and at least one AE.

ASN can communicate over Mcc with Middle node or Infrastructure Node.

- Application dedicated Node, ADN: contains at least one AE and does not have CSE. ADN may communicate with a Middle Node or infrastructure Node over a Mca reference point.

- Middle Node, MN: contains one CSE and zero or more AE. Middle node is located in the middle of OneM2M system. It can communicate with IN/MN/ASN over Mcc reference point and ADN over Mca.

- Infrastructure Node, IN: contains one CSE and zero or more AE. There is one logical Infrastructure Node per OneM2M domain per M2M service provider. IN can communicate with MN and ASN over Mcc reference points.

- Non-oneM2M Node: are legacy devices that interwork with the oneM2M architecture via the Middle node, MN.

[0041] These oneM2M logical nodes may map to one or more physical

devices or physical nodes in the network. Alternatively, some of the oneM2M logical nodes may be deployed as virtualized functions.

[0042] As used herein, one of the physical devices refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other devices. Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic signals, radio waves, infrared signals, and/or other types of signals suitable for conveying information through air. In some embodiments, a device may be configured to transmit and/or receive information without direct human interaction. For instance, a device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of devices include, but are not limited to, user equipment, UE, smart phone, mobile phone, cell phone, voice over IP, VoIP, phone, wireless local loop phone, desktop computer, personal data assistant, PDA, wireless cameras, gaming terminal devices, music storage, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop- embedded equipment, LEE, laptop-mounted equipment, LME, USB dongles, smart devices, wireless customer-premise equipment, CPE, and vehicle- mounted wireless terminal devices. The device may support device-to- device, D2D, communication, for example by implementing a 3GPP standard for sidelink communication, and may in this case be referred to as a D2D communication device. The device can be a constrained loT device or a non- constrained loT device. It 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 device and/or a network node.

The device may in this case be a machine-to-machine, M2M, device, which may in a 3GPP context be referred to as a machine-type communication, MTC, device. As one particular example, the device may be a UE

implementing the 3GPP narrow band internet of things, NB-loT standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A device as described above may represent the endpoint of a wireless connection communicating directly with the network over a wireless connection in which case the device may be referred to as a wireless device. Furthermore, a device as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

43] Wireless device may include antenna, interface, processing circuitry QQ20, device readable medium, user interface equipment, auxiliary equipment QQ34, power source and power circuitry. The wireless device may include multiple sets of one or more of the illustrated components for different wireless technologies integrated into the wireless device, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within the wireless device. [0044] Antenna may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface. In certain alternative embodiments, antenna may be separate from the wireless device and be connectable to the wireless device through an interface or port. Antenna, interface, and/or processing circuitry may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device.

[0045] As used herein, network physical node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with one or more physical device which may be a wireless device and/or with other network nodes or equipment in the communication network, which corresponds to the underlying network in the oneM2M architecture. 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, and evolved Node Bs (eNBs)). Further examples of network nodes include 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), core network nodes, application servers and the like. As another example, network node may be a virtual network node.

[0046] Accordingly:

- An ADN may map to a constrained loT device (i.e., small device with

limited CPU, memory) which could be used as a sensor, actuator, light and the likes).

- An ASN maps to typically non-constrained loT device.

- An MN physically map to a gateway (e.g., residential gateway, gateway in the network).

- An IN with a CSE only may as an example map to a server in the network.

An IN with a CSE and at least one AE may map as an example to a server in the network and may also map to a non-constrained device. [0047] Figure 2 (prior art) illustrates relationships among the oneM2M entities and nodes in the field domain and infrastructure domain. The field domain in Figure 2 (prior art) may be a user's home network where multiple nodes hosting applications are connected. The infrastructure domain includes one or more servers in the network controlling or enabling communication with the application entities in the devices in the field domain (ADN, ASN and/or MN). Applications running in the field domain would send and receive data to and from the infrastructure domain over a broadband access underlying network, hence subject to a broadband plan offered by the broadband operator or Internet Service Provider, ISP.

[0048] In order to use the M2M service, registration of the entities and nodes to a registrar CSE is required. Registration is the process of delivering AE or CSE information to another CSE in order to use M2M Services.

[0049] An AE on an ASN1/ASN2, an MN or an IN performs registration locally with the corresponding CSE in order to use M2M services offered by that

CSE. An AE on an ADN1 and ADN2 perform registration with the CSE on an IN and an MN respectively (as shown in Figure 2) in order to use M2M services offered by that CSE. An IN-AE performs registration with the corresponding CSE on an IN in order to use M2M services offered by that IN CSE. An AE can have interactions with its Registrar CSE (when it is the target

CSE) without the need to have the Registrar CSE register with other CSEs.

[0050] The CSE on ASN2 performs registration with the CSE in the MN in order to be able to use M2M Services offered by the CSE in the MN. As a result of successful ASN2-CSE registration with the MN-CSE, the CSEs on the ASN2 and the MN establish a relationship allowing them to exchange information.

[0051] The CSE on an MN performs registration with the CSE of another MN (not shown in Figure 2) in order to be able to use M2M Services offered by the CSE in the other MN. As a result of successful MN-CSE registration with the other MN-CSE, the CSEs on the MNs establish a relationship allowing them to exchange information.

[0052] The CSE on ASN1 or on an MN perform registration with the CSE in the IN in order to be able to use M2M Services offered by the CSE in the IN. As a result of successful ASN1/MN registration with the IN-CSE, the CSEs on ASN/MN and IN establish a relationship allowing them to exchange information.

[0053] Following a successful registration of an AE to a CSE, the AE is able to access, assuming access privilege is granted, the resources in all the CSEs that are potential targets of request from the Registrar CSE.

[0054] Figure 3 (prior art) illustrates an example of registration flow based on the implementation example shown in Figure 2 (prior art). For simplification of the registration flow of Figure 3 (prior art) registration of ASN2 and ADN1 are omitted.

[0055] Figure 3 (prior art) illustrates an MN-CSE registering with the oneM2M service platform IN-CSE over the underlying network in accordance with oneM2M Functional architecture TS-0001-V2.10.0. The MN-AE internally registers with the MN-CSE. ADN2-AE registers with the MN-CSE. Application on smart device, ASN1-AE, internally registers with the ASN 1-CSE. ASN1- CSE registers with the oneM2M service platform, IN-CSE. An application in the infrastructure domain, IN-AE that can control, manage monitor applications in the field domain registers with the oneM2M service platform, IN-CSE. Once registration is completed, the IN-CSE announces the IN-AE to MN-CSE and ASN1-CSE. Using a discovery request with specific filter criteria, the MN-AE and the ASN1-AE discover the IN-AE from the MN-CSE and ASN1-CSE respectively. The MN-AE creates an access control policy resource granting ADN2-AE, MN-AE and IN-AE access to the container and content instance resource. Similarly, the ASN1-AE creates an access control policy resource granting ASN1-AE and IN-AE access to the container and content instance resource.

[0056] Registration information included in the registration of a CSE or AE of a logical node comprise:

- Identifier of the Node.

- Reachability schedules; which are elements of a Node's policy, and

specify when messaging can occur between Nodes. Reachability schedules can be used in conjunction with other policy elements. When reachability schedules are not present in a Node then that Node is expected to be always reachable. - Managing connection state of communication channel to the registered AE or CSE.

[0057] Following a successful registration of an AE to a CSE, the AE is able to access and use the resources in the registrar CSE to use the M2M service. The registered AEs (ADN2-AE, ASN1-AE, MN-AE) in the field domain as illustrate in Figure 3 would be able to communicate or exchange data with other AEs in the infrastructure domain (IN-AE) (or even other AEs within the field domain). The communication is facilitated by the MN-CSE and the ASN1- CSE in the field domain and IN-CSE in the infrastructure domain. The amount of data exchanged vary from application to application. All traffic (signaling, data) between the AEs and CSEs in the field domain and the AEs and CSEs in the infrastructure domain are transported by an access and core network provided by an ISP or broadband network provider that is typically different from the M2M SP that provides the AEs and CSEs services. Consequently, the exchanged traffic is expected to be subject to any broadband subscription plan.

[0058] If user's monthly broadband subscription data limit is reached as per the FUP table exemplified in Figure 5, the M2M SP (which is typically different from the internet service provider, ISP, or the broadband operator providing broadband access) does not know if the ISP or the broadband operator has reduced the data speed due to applying FUP. When FUP is applied, the operation of some of the registered AEs (application) and the registered M2M devices will likely be impacted. Today, registration lifecycle of M2M

applications and M2M devices would be managed by the M2M SP

independently of the FUP imposed by the underlying network operator, which may be problematic to the M2M SP and to the applications which critically depend on the network speed and availability of a reliable continuous connectivity. Even more problematic is if a single broadband subscription is used to cover connected devices (smartphone, TV, gaming, video

surveillance, telemedicine or ehealth (if patient @home), etc.) that include user devices (smartphone, tablets, computers, eReaders, etc.). Under the user single broadband subscription, the data limit prior to applying FUP would be quickly reached, hence experiencing lower speeds for perhaps much longer period. [0059] Furthermore, the M2M SPs operating costs may be impacted as cost is incurred towards supervising the resources to manage device registration lifecycle. The cost may be reduced when for example one or more M2M application that can no longer function properly due to FUP, i.e., network speed (UL/DL) reduction is deregistered and/or Non-critical applications are deregistered and/or Potentially suspending ad-hoc emergency applications Other policies may be applied on the basis of the criticality, priority, data speed limit and bandwidth of the application.

[0060] Figure 4 illustrates an example of an loT deployment in a user's home, where the M2M/loT entities (TV, light, blood pressure meter, scale, game console, video surveillance camera, etc.) share the same broadband subscription as the user's subscription established by the ISP/broadband operator for transmitting data to the infrastructure entities in the infrastructure domain over the underlying network of the ISP or broadband operator. The M2M/loT entities comprise ADNs, ASNs and a middle node, MN. The ADNs,

ASNs and MN are hosted in multiple devices as illustrated in Figure 4.

[0061] Figure 6 (prior art) illustrates few of the characteristics of some

applications that may be used by connected devices. Figure 6 may be used to identify the potential impact of applying FUP (as exemplified in Figure 5) on some loT use cases and applications. For example:

[0062] Applications that require very low data rate and consume very low bandwidth, e.g., sensors, lights, etc. These applications may be critical or non-critical, in which case they could be assigned a high or low priority depending on how critical the application is to the user or by the M2M service provider.

[0063] Applications that consume large amount of bandwidth, but not critical, such as for example, wearables (sports application data sharing), video streaming. A relatively lower priority could be assigned by the user or by the M2M service provider.

[0064] Applications that consume some bandwidth but are critical such as telemedicine, ehealth (patient @home), etc. A relatively higher priority could be assigned by the user or by the M2M service provider as it relates to the health of the patient at home. [0065] Accordingly, when an application is considered critical, its M2M registration should be maintained providing a minimum data speed. When an application may be used to report or manage an adhoc emergency situation, the registration should be maintained. Alternatively, the data transfer may be suspended (registration suspended). The data transfer may be resumed only when an emergency should be reported or controlled via the M2M application. When an application is not critical or not used to report or control any ad-hoc emergency, the application or the M2M device may be deregistered.

[0066] Figure 7 illustrates registration flow in the context of oneM2M showing one M2M device 700 in a field domain registering to a registrar in the infrastructure domain according to one embodiment. The M2M device 700 in Figure 7 may be of any type as they may host any of the following logical M2M nodes: ADN, ASN, and an MN hosting a CSE (and may also host an AE). Figure 7 illustrates registration from one M2M device 700, however, it is understood that there may be one or more M2M devices 700 of any type deployed within the field domain and all are assumed to be able to register with a registrar in the infrastructure domain. The field domain may be a user's home, car, an enterprise, etc. The AEs may represent different types of applications. For example, in a user's home, the user may have multiple connected devices such as wearables, household devices, TV, gaming consoles, video camera's for surveillance and may even have some telemedicine devices if a patient is being monitored at home. All these devices host different applications which have different characteristics. Some of the applications are critical as they require permanent connectivity and minimum data rate (or speed) to be maintained and to ensure normal operation, while others may not be very critical. Other applications may not be permanently critical albeit they may be used to notify of an emergency situation. Other applications may be used to control the user's environment.

[0067] At step 701 , the M2M device 700 performs an attachment to resources in the underlying network, UN, (access network and core network AC-CN

(UN) 710) to receive an internet protocol IP address from the ISP or the broadband operator in accordance with the broadband subscription plan established between the subscriber of the M2M device 700 and the underlying network provider. The attachment procedure allows The ISP or broadband provider to provide the bit pipe to transport all M2M traffic (e.g., M2M registration, application data) exchanged between the service layers and application layers in the field domain and infrastructure domain as illustrated in Figure 1 (prior art). The ISP and broadband network provider manage the bandwidth, data rate of the bit pipe and control the traffic carried over the bit pipe. As previously indicated, one such control consists of exercising an FUP policy whenever a certain data limit is reached and reduce the data rate over the bit pipe (this is sometimes referred to as throttling).

[0068] The attachment procedure depends on the technology supported by the AC-CN(UN) 710. If the AC-CN(UN) 710 uses 3GPP LTE and EPC technology and the M2M device 700 supports the technology, the M2M device 700 uses the attachment procedure as described in 3GPP Technical

Specification 23.401 , where the M2M device 700 sends an attach request to a control node (Mobility Management Entity, MME) in the AC-CN(UN) 710 through a base station eNodeB in the AC-CN(UN) 710. The AC_CN(UN) 710 authenticates the M2M device 700, assigns an IP address and establishes a bearer between a gateway in the AC_CN(UN) 710 and the M2M device 700 through the base station in the AC-CN(UN) 710. The established bearer through the AC-CN(UN) 710 provides the bit pipe for all subsequent M2M related traffic. Additionally, the AC-CN(UN) 710 may assign an external identifier to the M2M device to be used by the M2M Service Provider to reference M2M access subscriptions for M2M entities. The external identifier may be provided to the M2M device 700 in the attachment procedure. The external identifier is used by the M2M SP to reach the M2M device in the AC- CN (UN) 710. The AC-CN (UN) 710 or a node in the M2M SP maintains a mapping between the M2M device ID and the external identifier.

[0069] At step 702, the M2M device 700 performs an M2M registration request to the registrar CSE, in this embodiment, the IN-CSE 730 is illustrated as a registrar CSE. The M2M registration is requested by the M2M device 700 in order to be able to use M2M Services offered by the CSE in the IN. As a result of successful M2M device 700 (ASN/MN/AND) registration with the IN- CSE 730, the CSEs on ASN/MN and IN establish a relationship allowing them to exchange information. If the M2M device 700 hosts an MN in the field domain, the registration is an MN-CSE registration to the CSE registrar (i.e., IN-CSE 730) in the infrastructure domain. If the M2M device 700 hosts an ASN, the registration is a CSE registration to the IN-CSE 730 in the infrastructure domain. If the M2M device 700 hosts an ADN, the registration is an AE registration to the IN-CSE 730 in the infrastructure domain. The M2M registration at step 702 comprises the following information:

- Identifier of the M2M logical Node: ADN, ASN or MN identifier.

- Reachability schedules; which are elements of a Node's policy, and

specify when messaging can occur between Nodes. Reachability schedules can be used in conjunction with other policy elements. When reachability schedules are not present in a Node then that Node is expected to be always reachable.

- Managing connection state of communication channel to the registered AE or CSE.

- May comprise an external identity that may be assigned by the AC- CN(UN) 730 during the attachment procedure of step 701. The M2M

Service Provider uses the external identifier to reference the M2M access subscription for the M2M logical nodes in the AN-CN(UN) 710.

- may comprise a priority.

[0070] Based on the type of M2M logical node (i.e., ADN, ASN, MN) hosted in the M2M device 700, and/or the application (AE) type and characteristics of the AE as described above and optionally the user preference, a priority may be assigned to each of the AE and/or M2M logical node. Namely, an MN- CSE, ASN-CSE, ASN-AE, ADN-AE, MN-AE will each be configured by a priority level by the M2M SP. In some instances, the priority level may also be allocated or configured by the owner of the devices hosting ADNs, ASNs and/or MNs in the field domain. If the priority is pre-configured in the M2M device 700, the M2M registration at step 702 may include the priority level.

[0071] At step 703, the IN-CSE 730 retrieves the profile of the loT entity

hosted in the M2M device. The profile may include a priority level for the registered loT entity, where the loT entity is an M2M logical node (ADN, ASN,

MN) or entity (i.e., AE, CSE) and may include quality of service characteristics of the loT entity and in particular, quality of service characteristics of registered AEs. If the M2M registration at step 702 included a priority level, the IN-CSE 730 compares the priority level received in the M2M registration against the priority level received in the profile and allocated to the

Registering M2M entity by the M2M SP. If the priority levels are equal, then registration is accepted; not withstanding successful authentication. If the priority levels don't match, the priority level in the profile may take precedence over the priority level included in the M2M registration message. The M2M registration should still be accepted using the priority level retrieved in the profile. Additionally, if the M2M registration request of step 702 does not include any priority level then the priority level included in the profile will be used.

[0072] At step 704, if the IN-CSE 730 has determined that the M2M

registration is accepted, the IN-CSE 730 instructs an M2M-monitoring server 740 to create an entry for the M2M logical node(s) associated with the M2M subscription. The M2M-monitoring server 740 keeps track of registered M2M nodes and entities (CSE, AEs) and is notified by the AC-CN (UN) 710 directly or through the IN-CSE 730 when the data limit is reached for the broadband or data subscription associated with the use of the underlying network resources of the AC-CN (UN) 710 by the one or more M2M device 700. The IN-CSE 730 sends all the relevant and available information for each M2M entity associated with the subscription to the M2M monitoring server 740. The M2M monitoring server 740 stores the information with the corresponding entry.

[0073] At step 705, the M2M Monitoring server 740 creates an entry for each M2M subscription based on the information received from the registrar (i.e., IN-CSE 730 as per embodiment of Figure 7). Each entry comprises some or all of the following information:

- The M2M subscription ID

- a binding between

o the M2M logical node (ADN, MN, ASN),

o the External identifier assigned to the M2M device hosting the M2M logical node, o the Registrar-ID (CSE-ID for registrar CSE which can be MN-CSE,

ASN-CSE, IN-CSE) and

o the AE-ID hosted by any of the M2M logical node.

- the associated priority level of the AE and of the CSE associated to the logical M2M node and may include the priority level of the registered CSEs.

- may include the quality of service characteristics including the minimum data rate/speed required for the AEs or the registered M2M logical node and may include the minimum bandwidth.

- A registration status.

[0074] The M2M monitoring server 740 sends at step 706 a response to IN- CSE 730 indicating that the request to create the entry is successful. Step 706 may be sent in parallel to step 705 or after creating the entry, i.e., after execution of step 705. Optionally, at step 707, the IN-CSE 730 sends a message to the AN-CN(UN)710 (e.g., an interworking function) to instruct the AN-CN (UN) 710 to notify the M2M monitoring server 740 or the IN-CSE 730 when the data/broadband subscription data limit is reached/crossed for the one or more M2M devices registered under the subscription and includes the identity of the M2M monitoring function 740 or of the IN-CSE 730 and external identifier assigned to a registered M2M device)

[0075] AT step 708, the IN-CSE 730 sends a registration reply to the M2M device 700, which may include the priority level provided to the M2M monitoring server 740. Note that step 708 may occur any time after step 703.

[0076] Figure 8 illustrates an embodiment of the actions to be undertaken by the M2M Monitoring function 740 when it is notified that a data/broadband limit/threshold is reached/crossed in the AC-CN(UN) 710 for the broadband or data subscription associated with the one or more registered M2M devices 700. Namely, one or more M2M logical nodes hosted in one or more M2M device 700 may share the same broadband or data subscription. These data limits are configurable by the AC-CN (UN) 710 provider, which may be an ISP or a broadband operator. [0077] Note that if the M2M node in the M2M device 700 de-registers from the IN-CSE 730 (registrar). The IN-CSE 730 730 will inform the M2M Monitoring server 740 accordingly so that the corresponding entry is removed.

[0078] Following successful M2M registration as illustrated in Figure 7,

signaling and data are exchanged over the bit pipe between the one or more

M2M devices associated to the subscription. At step 801 , If the data limit is reached for the subscription, the provider of the AC-CN(UN) 710 (e.g., ISP or broadband fixed or mobile operator) enforces a fair usage policy, FUP, by reducing the data speed of the bit pipe for the subscription. Figure 5 illustrates an example of an FUP that may be applied. At step 802, the AC-CN (UN) 710 issues a notification to the M2M Monitoring server 740 to notify the data limit is reached. The notification may comprise the M2M subscription ID, or the external identities of the one or more M2M devices associated with the same subscription, updated data speed being enforced by the UC-CN(UN) 710 where FUP is applied.

[0079] At step 803, the M2M monitoring server 740 derives the corresponding M2M registrar CSE-ID from the entry, i.e., the identity of the IN-CSE 730 in accordance with embodiment of Figure 7. It then determines the M2M logical node (ADN, ASN, MN) or entity (AE, CSE) to deregister or to suspend.

[0080] The traffic monitoring server determines the priority level associated with the M2M logical node/entity and if available the minimum data speed limit required for the normal operation of the M2M logical node/entity and optionally the minimum bandwidth. A low priority level could indicate a non-critical application for which de-registration will not cause negative effect. A high priority level could indicate a critical application that requires constant and reliable monitoring, hence de-registration should perhaps not be performed. There may be multiple priority levels, medium priority level applications may be suspended instead of deregistered. At a minimum there should be two priority levels to indicate critical and non-critical applications, where non- critical applications/nodes can be deregistered when FUP is applied while maintaining registration of critical applications/nodes.

[0081] In addition to the priority, the traffic monitoring server may additionally use the minimum data speed/rate required for normal operation of the application and optionally the bandwidth used by the M2M logical node/entity if available to determine the M2M logical node and/or entity to deregister or suspend. If the FUP reduced data speed is less than an M2M logical node/entity minimum required data speed/rate, the M2M monitoring server may de-register the node/entity or suspend it depending on its priority level. Different types of policy determination by the traffic monitoring server can be derived on the basis of the priority level, minimum data speed/limit of the node/entity and minimum required bandwidth if available in the entry.

[0082] At step 804, The M2M monitoring server 740 instructs the registrar CSE (IN-CSE 730) of the one or more M2M logical node/entity to deregister or suspend. A single notification per M2M logical node/entity that comprises the external identity associated with the M2M device 700 is sent to the IN-CSE 730. Alternatively, an aggregate notification that includes all the one or more M2M logical node/entity to deregister or suspend for the subscription is sent to the IN-CSE 730. Note that if the registrar is an MN-CSE with whom only ADNs are registered, then the M2M Monitoring server 740 can de-register some or all of the ADNs registered to the MN-CSE. Regardless, every M2M logical node\entity to be de-registered shall be notified.

[0083] At step 805, the IN-CSE 730 initiates the deregistration procedure in accordance with the deregistration procedure specified in oneM2M technical specification. For deregistration of the one or more M2M device 700, the IN-

CSE 730 start the deregistration timer and sends at step 806, a deregistration notification to the one or more M2M device 700 requesting deregistration of the M2M logical node/entity hosted in the M2M device 700. If at step 804, the IN-CSE 730 received a request to suspend data for one or more logical node/entity, the IN-CSE 730 starts suspending transmission of data to the registered node\entity, starts a suspension timer and sends at step 806 a suspend notification to the one or more M2M device 700 affected by the suspension order.

[0084] At step 807, the M2M device 700 that received a deregistration

notification, initiates a deregistration procedure. The M2M device 700 sends at step 808, a deregistration message for the logical M2M node/entity to the registrar (IN-CSE 730). Upon receiving the deregistration from the M2M device 700, the IN-CSE 730 stops the deregistration timer and sends at step 809, an update-entry message to the M2M monitoring server 740 indicating the deregistered logical M2M node/entity. At step 810, the M2M monitoring server 740 removes the entry for the deregistered M2M node\entity and sends a response back to IN-CSE 730 (the registrar) at step 81 1 to inform that the update to the entry is completed. Notified M2M node/entity is expected to explicitly de-register within a time limit after which it will be de-registered administratively, and the M2M monitoring server 740 will be notified so that the entry is removed.

[0085] Furthermore, if at step 807, the M2M device 700 that received a

suspension notification, initiates a suspension procedure and stops transmitting any data. The suspension may be temporary in which case a suspension timer set at the IN-CSE 730 may be provided in the suspension notification. The M2M device 700 suspends sending data and signaling towards the infrastructure node over the AC-CN(UN) 710 until it receives a resume data instruction or until a suspension timer has expired. The M2M device 700 sends at step 808 a message to confirm to the registrar IN-CSE 730 that data is suspended until a resume is received or until expiration of the suspension timer. Upon receiving the suspended data confirmation from the M2M device 700, the IN-CSE 730 updates the node/entity status to

"suspended" and sends at step 809 an update-entry message to the M2M monitoring server 740. The update may indicate the suspension timer. At step 810, the M2M monitoring server 740 updates the entry for the suspended M2M node\entity to indicate that data transfer to/from the device/node/entity is suspended and sends a response back to IN-CSE 730 (the registrar) at step 81 1 to inform that the update to the entry is completed.

[0086] Data transfer could be resumed for the suspended M2M nodes/entities when for example any of the following condition occurs:

- the FUP is lifted, or

- the suspension period has expired, or

- The registered nodes with high priority level that were not affected by the application of the FUP had eventually deregistered.

[0087] If FUP is lifted before expiry of the suspension timer, the AC-CN(UN) 710 may send a message to the M2M monitoring server 740 (directly or through the IN-CSE 730) indicating the data limit is lifted and normal (higher) data speed is resumed. The M2M monitoring server 740 determines if there are any M2M node/entity associated to the subscription in the entry table that are in suspended mode due to FUP. If any M2M node/entity is identified, the M2M monitoring server 740 notifies the IN-CSE 730 or the AN-CN (UN) 710 to resume the data transfer. Furthermore, the one or more M2M affected M2M devices are instructed by the IN-CSE 730 or the AN-CN (UN) 710 to resume data transfer.

[0088] Figure 9 illustrates an embodiment of a method 90 executed at the traffic monitoring server (or function if virtualized). Step 91 illustrates a step of creating an entry for each registered M2M logical node (ADN, ASN,

MN)/entity (CSE, AE) (both referred to as loT entity in general) associated with the data/broadband subscription provided by the AC-CN (UN) 710 provider. The M2M monitoring server creates an entry upon obtaining information from a registrar when an M2M logical node/entity is registered. Each entry created includes at least a priority level and identification information that comprise:

- Identity of the registered M2M logical node/entity,

- corresponding external identifier assigned to the corresponding M2M device hosting the M2M node/entity,

- the registrar identity;

[0089] The priority level is used to determine which M2M logical node/entity to deregister or suspend if FUP is applied over the bit pipe by the AC-CN(UN) provider (e.g., ISP, broadband mobile operator).

[0090] In addition to the identification and the priority, the entry may include:

- Subscription identity if more than one M2M device is associated with the subscription, else the external identity can be used to identify the subscription in the AN-CN(UN) 710.

- quality of service characteristics including the minimum data rate/speed required for the M2M logical node/entity to operate

- minimum bandwidth

see for example Figure 6 for example of quality of service information for some loT applications). - Registration status to indicated: active, suspended, suspended pending, deregistration pending.

- Suspension timer

If an entry includes a suspension timer, the entry is removed after the suspension timer has expired.

[0091] At step 92, the M2M monitoring server obtains a notification that data limit/threshold is reached at the AN-CN (UN) for the data/broadband subscription associated to the one or more M2M logical node/entity. The AC- CN (UN) is applying FUP on the subscription. The notification indicates updated data rate limit to be applied on the bit pipe providing data

transmission for the one or more M2M logical node/entity associated with the subscription.

[0092] Based on the updated data speed at the AC-CN (UN) and the entry data obtained and created at step 91 , the M2M monitoring server determines at step 93 which of the one or more M2M logical node/entity to deregister and which of the one or more M2M logical node/entity to suspend data

transmission, step 94.

[0093] The traffic monitoring server determines the priority level associated with the M2M logical node/entity and if available the minimum data speed limit required for the normal operation of the M2M logical node/entity and optionally the minimum bandwidth. A low priority level could indicate a non-critical application for which de-registration will not cause negative effect. A high priority level could indicate a critical application that requires constant and reliable monitoring, hence de-registration should perhaps not be performed. There may be multiple priority levels, medium priority level applications may be suspended instead of deregistered. At a minimum there should be two priority levels to indicate critical and non-critical applications, where non- critical applications/nodes can be deregistered when FUP is applied while maintaining registration of critical applications/nodes.

[0094] In addition to the priority, the traffic monitoring server may additionally use the minimum data speed/rate required for normal operation of the application and optionally the bandwidth used by the M2M logical node/entity if available to determine the M2M logical node and/or entity to deregister or suspend. Other characteristics as indicated in Figure 6 such as security or duty cycle could also be used in that determination. If the FUP reduced data speed is less than an M2M logical node/entity minimum required data speed/rate, the M2M monitoring server may de-register the node/entity or suspend it depending on its priority level. Different types of policy

determination by the traffic monitoring server can be derived on the basis of the priority level, minimum data speed/limit of the node/entity and minimum required bandwidth if available in the entry.

[0095] At step 95, the M2M monitoring server execute the steps of sending one or more instruction (to the registrar CSE or AN-CN (UN) indicating deregistration or registration suspension suspending data transmission of the one or more M2M logical node\entity. The M2M monitoring server instructs the registrar CSE of the one or more M2M logical node/entity to deregister or suspend. A single notification per M2M logical node/entity that comprises the external identity associated with the M2M device is sent to the registrar CSE.

Alternatively, an aggregate notification that includes all the one or more M2M logical node/entity to deregister or suspend for the subscription is sent to the registrar CSE. Note that if the registrar is an MN-CSE with whom only ADNs are registered, then the M2M Monitoring server can de-register some or all of the ADNs registered to the MN-CSE. Regardless, every M2M logical node\entity to be de-registered shall be notified.

[0096] When the M2M monitoring server sends an instruction to deregister the one or more selected M2M logical node/entity, it may set a registration status to "deregister pending", and when it receives confirmation that the M2M logical node\entity has successfully deregistered, it removes the entry from the entry table.

[0097] When the M2M monitoring server sends an instruction to suspend transmission for the one or more selected M2M logical node/entity, it may include a suspension timer that may be determined by the M2M monitoring server. The M2M monitoring server may also set a registration status to

"suspended pending". When it receives a confirmation that the M2M logical node\entity has successfully suspended transmission, it updates the registration status to "suspended". If an updated suspension timer is included, it adds or updates the suspension timer in the entry and starts the timer. If before expiration of the suspension timer, a notification is received that FUP is lifted at the AC-NC (UN), it may send a message to corresponding registrar CSE (identity stored in the entry) to resume data transmission for all the M2M logical node/entity that are in "suspended" state. When a notification is received that the transmission is resumed, the M2M monitoring

server/function changes the registration status from "suspended" to

"registered".

[0098] If the M2M monitoring server receives a deregistration message for one or more registered M2M logical node/entity while FUP is applied, it may decide to resume transmission for some selected M2M logical node/entity in

"suspended" state assuming the minimum required data speed is acceptable.

[0099] If the suspension timer is expired before the FUP is lifted, the

corresponding entry is removed.

[00100] In one embodiment illustrated in Figure 10, a server 740 (M2M

monitoring server) or network entity comprises a circuitry 1000 which executes the method steps according to the embodiments as described in Figure 7 along with steps 704-706 and Figure 8 along with steps 802-804 and 809-811 and Figure 9 in addition to other embodiments described herein. In one embodiment, the circuitry 1000 may comprise a processor 1001 and a storage 1002 (also referred to as memory) containing instructions, which when executed, cause the processor 1001 to perform the steps in a method according to embodiments described herein. The circuitry 1000 may further comprise a communication interface 1003 to communicate with the registrar CSEs and AN-CN(UN) 710 for enabling management of M2M registration cycle when the broadband subscription of the underlying network becomes temporary limited.

[00101] The server 740 according to some other embodiments of the present disclosure includes one or more modules, each of which is implemented in software. The module(s) provide the functionality of the server described herein.

[00102] Figure 1 1 illustrates an embodiment of the server 740 comprising a processing module 1101 configured to create an entry for each registered loT entity of the one or more loT entity and associated with the subscription, the entry comprising associated identities and a priority level for each of the registered loT entity and storing in the memory module 1 102, each of the entry with the corresponding information. The processing module 1 101 further configured to obtain over the communication module 1 103 data transfer threshold information indicative that a data limit for the subscription is reached, the information comprising an updated data rate limit to be applied to each of the registered loT entity associated with the subscription. The processing module 1 101 is also configured to determine the one or more loT entity to deregister based on the data transfer threshold information and data in the entry and to determine the one or more loT entity to suspend based on the data transfer threshold information and data in the entry. The processing module 1 101 is also configured to send over the communication module 1 103 one or more instruction indicating deregistration or suspension data transmission of the one or more loT entity.

[00103] In some embodiments, a computer program including instructions

which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the server 740 according to any of the embodiments described herein is provided. In some embodiments, a carrier containing the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[00104] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.

Claims

What is claimed is:

1. A method of controlling a registration status of one or more registered Internet of thing, loT, entity, associated to a common subscription, the method comprising:

- creating an entry for each registered loT entity associated with the

common subscription, the entry comprising associated identities and a priority level for each of the registered loT entity;

- obtaining data transfer threshold information indicative that a data limit for the common subscription is reached, the information comprising an updated data rate limit to be applied to each of the registered loT entity associated with the common subscription;

- determining the one or more registered loT entity to deregister based on the data transfer threshold information and data in the entry;

- determining the one or more registered loT entity to suspend based on the data transfer threshold information and data in the entry; and

- sending one or more instructions indicating deregistration or suspension data transmission of the one or more registered loT entity.

2. The method of claim 1 , wherein the entry further comprises an identity of a registrar the one or more registered loT entity register thereto.

3. The method of claim 1 , wherein the entry further comprises quality of service characteristics associated with the one or more registered loT entity.

4. The method of claim 3, wherein the quality of service characteristics comprises a minimum data speed limit required for normal operation of the one or more registered loT entity.

5. The method of claim 1 , wherein the entry further comprises a registration status indicating the state of the loT registration of the one or more registered loT entity.

6. The method of claim 1 , wherein determining the one or more registered loT entity to deregister is based on the priority level of the one or more registered loT entity.

7. The method of claims 1 , 3 and 4, wherein determining the one or more registered loT entry to deregister is based on the priority level of the one or more registered loT entity and the quality of service characteristics associated with the one or more registered loT entity.

8. The method of claim 1 , wherein determining the one or more registered loT entity to suspend is based on the priority level of the one or more registered loT entity.

9. The method of claims 1 , 3 and 4, wherein determining the one or more registered loT entity to suspend is based on the priority level of the one or more registered loT entity and the quality of service characteristics associated with the one or more registered loT entity.

10. The method of claim 1 , wherein sending the one or more instructions indicating data transmission to be suspended for the one or more registered loT entity comprises a suspension timer indicating a period for suspending data transmission.

11. The method of claim 1 , further comprising receiving a confirmation that the one or more registered loT entity is successfully deregistered and removing the entries associated to the one or more registered loT entity that is deregistered.

12. The method of claim 1 , further comprising

receiving a confirmation that the one or more registered loT entity is successfully suspended,

maintaining the entry for the registered one or more loT entity that is suspended.

13. The method of claim 12, wherein the confirmation comprises an updated suspension timer.

14. The method of claims 1 , 12 and 13 further comprising monitoring changes in the data transfer threshold information and sending a notification to resume data transfer for the one or more registered loT entity in suspended mode if an updated data transfer threshold information is received indicating the data limit for the common subscription is lifted.

15. The method of claim 1 , wherein the one or more registered loT entity is at least one of an application entity, AE, a common service entity, CSE, a dedicated application node, ADN, an application service node, ASN, and a middle node, MN.

16. A computer program, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1 to 14.

17. A carrier containing the computer program of claim 15, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

18. A network entity comprising a circuitry configured to:

- create an entry for each registered Internet of Things, loT, entity

associated with the common subscription, the entry comprising associated identities and a priority level for each of the registered loT entity;

- obtain data transfer threshold information indicative that a data limit for the common subscription is reached, the information comprising an updated data rate limit to be applied to each of the registered loT entity associated with the common subscription;

- determine the one or more registered loT entity to deregister based on the data transfer threshold information and data in the entry;

- determine the one or more registered loT entity to suspend based on the data transfer threshold information and data in the entry; and - send one or more instruction to indicate deregistration or suspension data transmission of the one or more registered loT entity.

19. The network entity of claim 17, wherein the circuitry comprises a processor, a communication interface and a memory, the memory containing instructions executable by the processor.