Scheduling an appointment window for a communication session

Abstract

A first network device (200), an loT server device (220), methods, and computer programs are disclosed. The first network device (200) is in a cellular network (210), for scheduling an appointment window for a communication session between an Internet-of-Things, loT, server device (220), and one or more loT devices (230, 231, 232). The first network device (200) is configured to: receive a booking request (240) from the loT server device (220) for the communication session; create a booking identifier (250) associated to the booking request (240), and an appointment window (260) based on the booking request (240), if the loT server device (220) is authorized to perform the booking request (240); send a booking response (270) to the loT server device (220).

Description

[0001] SCHEDULING AN APPOINTMENT WINDOW FOR A COMMUNICATION SESSION

[0002] TECHNICAL FIELD

[0003] The invention relates to a first network device in a communication network, the first network device comprising for scheduling an appointment window for a communication session between an Internet-of-Things (loT) server device and one or more loT devices; an loT server device for scheduling an appointment window for the communication session between the loT server device and the one or more loT devices; corresponding methods; corresponding computer programs; and a corresponding computer readable storage medium.

[0004] BACKGROUND

[0005] An Internet-of-Things (loT) device may be in different modes. The different modes may be, for example, active mode, or sleep mode. The loT device may spend a significant part of its lifetime in the sleep mode. While in the sleep mode, the loT device may be registered in a 3rd Generation Partnership Project (3GPP) cellular network. However, the loT device is unreachable while in sleep mode.

[0006] An loT server can subscribe to Monitoring Event notifications, such as Monitoring Procedures over a T8 interface as defined in 3GPP TS 29.122, for example version V18.3.0.

[0007] The loT server may configure one or more device related cellular network parameters by using Procedures for Network Parameter Configuration as defined in 3GPP TS 29.122 V18.3.0. In particular, the one or more device-related cellular network parameters may be: the value of periodic Tracking Area Update (pTAU) timer, and / or the length of an extended idle-mode Discontinuous Reception (eDRX) timer.

[0008] The loT server may also trigger a User Equipment (UE) using a Device Triggering Procedure, such as defined in 3GPP TS 29.122 V18.3.0. The Device Triggering Procedure of 3GPP TS 29.122 V18.3.0 is defined as a Short Message Service (SMS)- based mechanism which uses a T4 interface and an SMS-Service Center (SMS-SC) for:

[0009] Delivering an application trigger to the UE embedded in an SMS message; and Reporting back a successful SMS delivery to the loT server.

[0010] The UE device establishes a Public Data Network (PDN) connection to the loT server based on an address information in a payload of the SMS message received by the UE.

[0011] SUMMARY

[0012] One of the disadvantages of the prior approaches is that the Device Triggering Procedure is performed for an individual UE. However, it is not applicable to a group of loT devices.

[0013] Another disadvantage of the prior approaches is that an loT device reachability can be controlled with limited accuracy. Indeed, in prior approaches there are two Non Access Stratum (NAS) timers which can wake up an loT device from sleep mode: a periodic TAU (pTAU) timer or an extended periodic TAU (T3412) timer, and an extended idle-mode DRX (eDRX) timer. When the UE transits from a CONNECTED mode to an IDLE mode, the NAS timers restart to the NAS time initial value. Thus, it is difficult to make the loT device reachable at a particular time since the loT device originated session restarts the two NAS timers. Hence, the two NAS timers do not wake up the loT device in the particular time wanted by the loT server.

[0014] Another disadvantage with prior approaches relates to scheduling of actions of the loT server. If an loT server wants to schedule an action for a predefined time range, then the loT server requires a complicated set of preparations to ensure that the loT device is reachable during the predetermined time range the action will occur. The loT server must monitor whether the loT device is reachable. Eventually, the loT server may change a pTAU or eDRX configuration, so as to have the loT device reachable for the predetermined time range during which the action will occur.

[0015] Another disadvantage with prior approaches relates to schedule of an action performed by a group of loT devices. If an loT server wants to schedule an action to be performed by a group of loT devices, and the loT server wants to distribute the action among the impacted loT devices within a time rage, then the loT server shall schedule individually with each individual loT device of the group of loT devices, as a reachability period of each individual loT device is not synchronized with the other loT devices in the group of loT devices, even if they might all have the same pTAll period length. Furthermore, a distribution of a new potential reachable occasion within the time range must be performed by the loT server.

[0016] Another disadvantage with the prior approaches relates to inapplicability of Device Triggering Procedure, as defined in 3GPP TS 29.122 V 18.3.0, for scheduling an action to be performed by an loT device. Indeed, the Device Triggering Procedure allows to make the loT device reachable during a timespan. However, there is a lack of knowledge of time period within which the loT device is reachable. Furthermore, the Device Triggering Procedure is a UE-level function which does not support triggering a group of UEs.

[0017] An object of the invention is to enable improved reachability of loT devices connected to a cellular network.

[0018] According to a first aspect of the invention, a first network device in a cellular network is provided. The first network device is for scheduling an appointment window for a communication session between an Internet-of-Things, loT, server device, and one or more loT devices. The first network device is configured to receive a booking request from the loT server device for the communication session. The first network device is configured to create a booking identifier associated with the booking request, and the appointment window based on the booking request, if the loT server device is authorized to perform the booking request. The first network device is configured to send a booking response to the loT server device. Hereby is achieved that an appointment window for the communication session between the loT server device and the one or more loT devices is scheduled based on the booking request sent by the loT server.

[0019] According to an embodiment of the first aspect, the booking request comprises one or more of: an identifier of the one or more loT devices; an identifier of the loT server device; a value corresponding to a Quality of Service, QoS, requirement for the communication session; an event type of which the loT server device shall be notified; a time interval indicating when the event type is to be performed; and a schedule type of the appointment window.

[0020] According to an embodiment of the first aspect, the value corresponding to the QoS requirement is related to one or more of: maximum allowed packet loss rate; minimum bit rate; minimum bandwidth; maximum transmission delay; maximum allowed jitter; maximum size of transferred data in the communication session; session length; and a maximum value of parallel booked session per cell.

[0021] According to an embodiment of the first aspect, the event type comprises one or more of: a reachability of the one or more loT devices being a Monitoring Event of ReachabilityType “SMS”, and with an Idle Status Indication; and a reachability of the one or more loT devices being a Monitoring Event of ReachabilityType “data”, and with an Idle Status Indication.

[0022] According to an embodiment of the first aspect, the time interval comprises one or more of: a single time interval specified by a starting point timestamp, and an ending point timestamp; an interval list comprising one or more single time intervals; and a periodic time interval.

[0023] According to an embodiment of the first aspect, the schedule type of the appointment window indicates one or more of: an individual schedule of the one or more loT devices; and a distributed schedule of the one or more loT devices.

[0024] According to an embodiment of the first aspect, the first network device is configured to send an authorization booking request to a second network device. The first network device is in this embodiment configured to receive an authorization booking response from the second network device.

[0025] According to an embodiment of the first aspect, the authorization booking request comprises one or more of: the identifier of the one or more loT devices; the identifier of the loT server device; the event type; the value corresponding to the QoS requirement.

[0026] According to an embodiment of the first aspect, the authorization booking response comprises: an indication notifying that the loT server device is authorized to perform the booking request; or a booking error response notifying that the loT server device is not authorized to perform the booking request.

[0027] According to an embodiment of the first aspect, the first network device comprises one or more of: a booking registry which comprises a booking entry associated with information related to the booking request; a booking calendar which comprises a calendar entry for each of the one or more loT devices, and a first list of one or more booking identifiers that comprises the created booking identifier, each booking identifier of the first list is associated with a list of booking notifications; a QoS monitor, which comprises one or more QoS statistics related to the cellular network; and a notification monitor, which comprises a notification record for each of the one or more loT devices, and a list of one or more Monitoring Event type records, each of the one or more Monitoring Event type records comprises a second list of one or more booking identifiers, which second list comprises the created booking identifier.

[0028] According to an embodiment of the first aspect, create the appointment window comprises creating a booking entry in the booking register and / or a calendar entry in the booking calendar for each of the one or more loT devices.

[0029] According to an embodiment of the first aspect, the information related to the booking request comprises one or more of: the booking identifier; the identifier of the one or more loT devices; the identifier of the loT server device; the value corresponding to the QoS requirement for the communication session; the event type of which the loT server device shall be notified; the time interval indicating when the event type is to be performed; and the schedule type of the appointment window.

[0030] According to an embodiment of the first aspect, the booking response comprises one or more of: the booking identifier; and an indication that the appointment window is created based on the booking request, or an indication that the appointment window is created based on an alternative time interval.

[0031] According to an embodiment of the first aspect, the first network device is configured to update the notification monitor. The first network device is configured to update the booking calendar.

[0032] According to an embodiment of the first aspect, updating the notification monitor comprises: sending, to a third network device, a Monitoring Event Configuration Request, wherein the Monitoring Event Configuration Request comprises the identifier of the one or more loT devices, and the event type; and receiving, from the third network device, a Monitoring Event Configuration Response, wherein the Monitoring Event Configuration Response comprises a monitoring identifier for each of the one or more loT devices.

[0033] According to an embodiment of the first aspect, updating the booking calendar comprises adding the booking identifier to the calendar entry for each of the one or more loT devices.

[0034] According to an embodiment of the first aspect, the first network device is configured to: receive, at a first time instance, a Monitoring Event notification related to the one or more loT devices from the third network device, the Monitoring Event notification comprises the event type to be notified of, and the identifier of the one or more loT devices. The first network device is configured to determine one or more booking identifiers associated with the one or more loT devices, each of the time interval of the determined one or more booking identifiers comprises the first time instance; and each of the one or more booking identifiers is associated with the event type comprised in the Monitoring Event notification. The first network device is configured to send a booking appointment notification to the loT server device, the booking appointment notification comprises the identifier of the one or more loT devices associated with the determined one or more booking identifiers. The first network device is configured to receive a booking appointment acknowledgment from the loT server device. According to an embodiment of the first aspect, the first network device is configured to update the QoS monitor by adding an action-started indication in relation to the one or more loT devices associated with the determined one or more booking identifiers.

[0035] According to an embodiment of the first aspect, the first network device is configured to receive a booked action report from the loT server device, the booked action report comprises the identifier of the one or more loT devices, the booking identifier, and a success indication. The first network device is configured to update the booking calendar. The first network device is configured to update the notification monitor. The first network device is configured to update the QoS monitor by adding an action-finished indication in relation to the one or more loT devices identified in the received booked action report.

[0036] According to an embodiment of the first aspect, the first network device is configured to send an appointment error notification to the loT server device, if one or more conditions are not met. The first network device is configured to subsequently receive an appointment error acknowledgment from the loT server device.

[0037] According to an embodiment of the first aspect, the appointment error notification comprises one or more of: the booking identifier; the identifier of the one or more loT devices; and an error indication.

[0038] According to an embodiment of the first aspect, the first network device is configured to receive, at a second time instance, a booking list query request from the loT server device, the booking list query request comprises the identifier of the loT server device. The first network device is configured to determine, if the loT server device is authorized, one or more booking identifiers associated with the identifier of the loT server device, each of the time interval of the determined one or more booking identifiers comprise the second time instance, and each of the one or more booking identifiers is associated with the identifier of the loT server device comprised in the booking list query request. The first network device is configured to send, if the loT server device is authorized, a booking list query response, the booking list query response comprises the determined one or more booking identifiers. According to an embodiment of the first aspect, the first network device is configured to send an authorization booking list query request to the second network device. The first network device is configured to receive an authorization booking list query response from the second network device.

[0039] According to an embodiment of the first aspect, the authorization booking list query request comprises the identifier of the loT server device.

[0040] According to an embodiment of the first aspect, the authorization booking list query response comprises an indication notifying that the loT server device is authorized to perform the booking list query request; or a booking query list error response notifying that the loT server device is not authorized to perform the booking list query request.

[0041] According to an embodiment of the first aspect, the first network device is configured to receive a booking query request from the loT server device, the booking query request comprises the booking identifier. The first network device is configured to send, if the loT server device is authorized to receive information related to the booking identifier, a booking query response to the loT server device, wherein the booking query response comprises information related to the booking identifier.

[0042] According to an embodiment of the first aspect, the information related to the booking identifier comprises one or more of: the identifier of the one or more loT devices; the identifier of the loT server device; the value corresponding to the QoS requirement for the communication session; the event type of which the loT server device shall be notified; the time interval indicating when the event type is to be performed; and the schedule type of the appointment window.

[0043] According to an embodiment of the first aspect, the first network device is configured to send an authorization booking query request to the second network device. The first network device is configured to receive an authorization booking query response from the second network device. According to an embodiment of the first aspect, the authorization booking query request comprises one or more of: the booking identifier; and the identifier of the loT server device.

[0044] According to an embodiment of the first aspect, the authorization booking query response comprises an indication notifying that the loT server device is authorized to perform the booking query request; or a booking query error response notifying that the loT server device is not authorized to perform the booking query request.

[0045] According to an embodiment of the first aspect, the first network device is configured to receive a booking cancellation request from the loT server device, the booking cancellation request comprises the booking identifier. The first network device is configured to delete the booking entry associated with the booking identifier, if the loT server device is authorized to request the booking cancellation request. The first network device is configured to send a booking cancellation response to the loT server device, if the loT server device is authorized to request the booking cancellation request.

[0046] According to an embodiment of the first aspect, the first network device is configured to send an authorization booking cancellation request to the second network device. The first network device is configured to receive an authorization booking cancellation response from the second network device.

[0047] According to an embodiment of the first aspect, the authorization booking cancellation request comprises one or more of: the booking identifier; and the identifier of the loT server device.

[0048] According to an embodiment of the first aspect, the authorization booking cancellation response comprises: an indication notifying that the loT server device is authorized to perform the booking cancellation request; or a booking cancellation error response notifying that the loT server device is not authorized to perform the booking cancellation request. According to an embodiment of the first aspect, the first network device is configured to send, to the loT server device, a booking removal indication, the booking removal indication comprises the booking identifier, and a cause indication for a removal of a booking request associated with the booking identifier. The first network device is configured to receive a booking removal acknowledgement from the loT server device.

[0049] According to an embodiment of the first aspect, the booking identifier is a uniform resource identifier.

[0050] According to an embodiment of the first aspect, the second network device comprises at least one of: a Home Subscriber Server, HSS, associated with the one or more loT devices; and a unified Data Management, UDM, associated with the one or more loT devices.

[0051] According to an embodiment of the first aspect, the third network device is a Service Capability Exposure Function, SCEF, device.

[0052] According to a second aspect of the invention an Internet of Things, loT, server device is provided. The loT server device is for scheduling an appointment window for a communication session between the loT server device, and one or more loT devices. The loT server device is configured to send a booking request to a first network device. The loT server device is configured to receive a booking response from the first network device.

[0053] According to an embodiment of the second aspect, the booking request comprises one or more of: an identifier of the one or more loT devices; an identifier of the loT server device; a value corresponding to a Quality of Service, QoS, requirement for the communication session; an event type of which the loT server device shall be notified; a time interval indicating when the event type is to be performed; and a schedule type of the appointment window.

[0054] According to an embodiment of the second aspect, the value corresponding to the QoS requirement relates to or more of: maximum allowed packet loss rate; minimum bit rate; minimum bandwidth; maximum transmission delay; maximum allowed jitter; maximum size of transferred data in the communication session; session length; and a maximum value of parallel booked session per cell.

[0055] According to an embodiment of the second aspect, the event type comprises one or more of: a reachability of the one or more loT devices being a Monitoring Event ReachabilityType “SMS”, and with an Idle Status Indication; and a reachability of the one or more loT devices being a Monitoring Event ReachabilityType “data”, and with an Idle Status Indication.

[0056] According to an embodiment of the second aspect, the time interval comprises one or more of: a single time interval specified by a starting point timestamp, and an ending point timestamp; an interval list comprising one or more single time intervals; and a periodic time interval.

[0057] According to an embodiment of the second aspect, the schedule type of appointment window indicates one or more of: an individual schedule of the one or more loT devices; and a distributed schedule of the one or more loT devices.

[0058] According to an embodiment of the second aspect, the booking response comprises one or more of: the booking identifier; and an indication that the appointment window is created according to the booking request, or an indication that the appointment window is created according to an alternative time.

[0059] According to an embodiment of the second aspect, the loT server device is configured to receive a booking appointment notification from the first network device, the booking appointment notification comprises the identifier of the one or more loT devices, the one or more loT devices are ready to be booked. The loT server device is configured to send a booking appointment acknowledgment to the first network device.

[0060] According to an embodiment of the second aspect, the loT server device is configured to send a booked action report to the first network device, the booked action report comprises the identifier of the one or more loT devices, the booking identifier, and a success indication.

[0061] According to an embodiment of the second aspect, the loT server device is configured to receive an appointment error notification from the first network device, if one or more conditions are not met. The loT server device is configured to subsequently send an appointment error acknowledgement to the first network device.

[0062] According to an embodiment of the second aspect, the appointment error notification comprises one or more of: the booking identifier; the identifier of the one or more loT device; and an error indication.

[0063] According to an embodiment of the second aspect, the loT server device is configured to send, at a second time instance, a booking list query request to the first network device, the booking list query request comprises the identifier of the loT server device. The loT server device is configured to receive a booking list query response, the booking list query response comprises one or more booking identifiers associated to the identifier of the loT server device.

[0064] According to an embodiment of the second aspect, the loT server device is configured to send a booking query request to the first network device, the booking query request comprises the booking identifier. The loT server device is configured to receive, if the loT server device is authorized to receive information related to the booking identifier, a booking query response from the first network device, wherein the booking query response comprises the information related to the booking identifier.

[0065] According to an embodiment of the second aspect, the information related to the booking identifier comprises one or more of: the identifier of the one or more loT devices; the identifier of the loT server device; the value corresponding to the QoS requirement for the communication session; the event type of which the loT server device shall be notified; the time interval indicating when the event type is to be performed; and the schedule type of the appointment window. According to an embodiment of the second aspect, the loT server device is configured to send a booking cancellation request to the first network device, the booking cancellation request comprises the booking identifier. The loT server device is configured to receive a booking cancellation response from the first network device, if the loT server device is authorized to request the booking cancellation request.

[0066] According to an embodiment of the second aspect, the loT server device is configured to receive, from the first network device, a booking removal indication the booking removal indication comprises the booking identifier, and a cause indication for a removal of a booking request associated with the booking identifier. The loT server device is configured to send a booking removal acknowledgment to the first network device.

[0067] According to an embodiment of the second aspect, the booking identifier is a uniform resource identifier.

[0068] According to a third aspect of the invention a method is provided. The method is performed by a first network device in a cellular network. The method is for scheduling an appointment window for a communication session between an Internet-of-Things, loT, server device, and one or more loT devices. The method comprises receiving a booking request from the loT server device and creating a booking identifier associated with the booking request. An appointment window is created based on the booking request, if the loT server device is authorized to perform the booking request. The method furthermore comprises sending a booking response to the loT server device.

[0069] According to an embodiment of the third aspect, the booking request comprises one or more of: an identifier of the one or more loT devices; an identifier of the loT server device; a value corresponding to a Quality of Service, QoS, requirement for the communication session; an event type of which the loT server device shall be notified; a time interval indicating when the event type is to be performed; and a schedule type of the appointment window. According to an embodiment of the third aspect, the value corresponding to the QoS requirement is related to one or more of: maximum allowed packet loss rate; minimum bit rate; minimum bandwidth; maximum transmission delay; maximum allowed jitter; maximum size of transferred data in the communication session; session length; and a maximum value of parallel booked session per cell.

[0070] According to an embodiment of the third aspect, the event type comprises one or more of: a reachability of the one or more loT devices being a Monitoring Event ReachabilityType “SMS”, and with an Idle Status Indication; and a reachability of the one or more loT devices being a Monitoring Event ReachabilityType “data”, and with an Idle Status Indication.

[0071] According to an embodiment of the third aspect, the time interval comprises one or more of: a single time interval specified by a starting point timestamp, and an ending point timestamp; an interval list comprising one or more single time intervals; and a periodic time interval.

[0072] According to an embodiment of the third aspect, the schedule type of the appointment window indicates one or more of: an individual schedule of the one or more loT devices; and a distributed schedule of the one or more loT devices.

[0073] According to an embodiment of the third aspect, the method comprises sending an authorization booking request to a second network device. The method comprises receiving an authorization booking response from the second network device.

[0074] According to an embodiment of the third aspect, the authorization booking request comprises one or more of: the identifier of the one or more loT devices; the identifier of the loT server device; the event type; the value corresponding to the QoS requirement.

[0075] According to an embodiment of the third aspect, the authorization booking response comprises: an indication notifying that the loT server device is authorized to perform the booking request; or a booking error response notifying that the loT server device is not authorized to perform the booking request.

[0076] According to an embodiment of the third aspect, the first network device comprises one or more of: a booking registry, which comprises a booking entry associated with information related to the booking request. The first network device comprises one or more of a booking calendar, which comprises a calendar entry for each of the one or more loT devices, and a first list of one or more booking identifiers, which first list comprises the created booking identifier, each booking identifier of the first list is associated with a list of booking notifications. The first network device comprises one or more of a QoS monitor, which comprises one or more QoS statistics related to the cellular network. The first network device comprises one or more of a notification monitor, which comprises a notification record for each of the one or more loT devices, and a list of one or more Monitoring Event type records. Each of the one or more Monitoring Event type records comprises a second list of one or more booking identifiers, which second list comprises the created booking identifier.

[0077] According to an embodiment of the third aspect, creating the appointment window comprises creating a booking entry in the booking register and / or a calendar entry in the booking calendar for each of the one or more loT devices.

[0078] According to an embodiment of the third aspect, the information related to the booking request comprises one or more of: the booking identifier; the identifier of the one or more loT devices; the identifier of the loT server device; the value corresponding to QoS requirement for the communication session; the event type of which the loT server device shall be notified; the time interval indicating when the event type is to be performed; and the schedule type of the appointment window.

[0079] According to an embodiment of the third aspect, the booking response comprises one or more of: the booking identifier; and an indication that the appointment window is created based on the booking request, or an indication that the appointment window is created based on an alternative time interval. According to an embodiment of the third aspect, the method comprises updating the notification monitor; and updating the booking calendar.

[0080] According to an embodiment of the third aspect, updating the notification monitor comprises: sending, to a third network device, a Monitoring Event Configuration Request, the Monitoring Event Configuration Request comprises the identifier of the one or more loT devices, and the event type; and receiving, from the third network device, a Monitoring Event Configuration Response, wherein the Monitoring Event Configuration Response comprises a monitoring identifier for each of the one or more loT devices.

[0081] According to an embodiment of the third aspect, updating the booking calendar comprises: adding the booking identifier to the calendar entry for each of the one or more loT devices.

[0082] According to an embodiment of the third aspect, the method comprises receiving, at a first time instance, a Monitoring Event notification related to the one or more loT devices from the third network device, the Monitoring Event notification comprises the event type to be notified of, and the identifier of the one or more loT devices. The method comprises determining one or more booking identifiers associated with the one or more loT devices, each of the time interval of the determined one or more booking identifiers comprises the first time instance; and each of the one or more booking identifiers is associated with the event type comprised in the Monitoring Event notification. The method comprises sending a booking appointment notification to the loT server device, wherein the booking appointment notification comprises the identifier of the one or more loT devices associated with the determined one or more booking identifiers. The method comprises receiving a booking appointment acknowledgment from the loT server device.

[0083] According to an embodiment of the third aspect, the method comprises updating the QoS monitor by adding an action-started indication in relation to the one or more loT devices associated with the determined one or more booking identifiers. According to an embodiment of the third aspect, the method comprises receiving a booked action report from the loT server device, the booked action report comprises the identifier of the one or more loT devices, the booking identifier, and a success indication. The method comprises updating the booking calendar. The method comprises updating the notification monitor. The method comprises updating the QoS monitor by adding an action-finished indication in relation to the one or more loT devices identified in the received booked action report.

[0084] According to an embodiment of the third aspect, the method comprises sending an appointment error notification to the loT server device, if one or more conditions are not met; and subsequently receiving an appointment error acknowledgment from the loT server device.

[0085] According to an embodiment of the third aspect, the appointment error notification comprises one or more of: the booking identifier; the identifier of the one or more loT devices; and an error indication.

[0086] According to an embodiment of the third aspect, the method comprises receiving, at a second time instance, a booking list query request from the loT server device, the booking list query request comprises the identifier of the loT server device. The method comprises determining, if the loT server device is authorized, one or more booking identifiers associated with the identifier of the loT server device, each of the time interval of the determined one or more booking identifiers comprise the second time instance; and each of the one or more booking identifiers is associated with the identifier of the loT server device comprised in the booking list query request. The method comprises sending, if the loT server device is authorized, a booking list query response, the booking list query response comprises the determined one or more booking identifiers.

[0087] According to an embodiment of the third aspect, the method comprises sending an authorization booking list query request to the second network device; and receiving an authorization booking list query response from the second network device. According to an embodiment of the third aspect, the authorization booking list query request comprises the identifier of the loT server device.

[0088] According to an embodiment of the third aspect, the authorization booking list query response comprises: an indication notifying that the loT server device is authorized to perform the booking list query request; or a booking query list error response notifying that the loT server device is not authorized to perform the booking list query request.

[0089] According to an embodiment of the third aspect, the method comprises receiving a booking query request from the loT server device, the booking query request comprises the booking identifier. The method comprises sending, if the loT server device is authorized to receive information related to the booking identifier, a booking query response to the loT server device, the booking query response comprises information related to the booking identifier.

[0090] According to an embodiment of the third aspect, the information related to the booking identifier comprises one or more of: the identifier of the one or more loT devices; the identifier of the loT server device; the value corresponding to the QoS requirement for the communication session; the event type of which the loT server device shall be notified; the time interval indicating when the event type is to be performed; and the schedule type of the appointment window.

[0091] According to an embodiment of the third aspect, the method comprises sending an authorization booking query request to the second network device. The method comprises receiving an authorization booking query response from the second network device.

[0092] According to an embodiment of the third aspect, the authorization booking query request comprises one or more of: the booking identifier; and the identifier of the loT server device.

[0093] According to an embodiment of the third aspect, the authorization booking query response comprises: an indication notifying that the loT server device is authorized to perform the booking query request; or a booking query error response notifying that the loT server device is not authorized to perform the booking query request.

[0094] According to an embodiment of the third aspect, the method comprises receiving a booking cancellation request from the loT server device, the booking cancellation request comprises the booking identifier. The method comprises deleting the booking entry associated with the booking identifier, if the loT server device is authorized to request the booking cancellation request. The method comprises sending a booking cancellation response to the loT server device, if the loT server device is authorized to request the booking cancellation request.

[0095] According to an embodiment of the third aspect, the method comprises sending an authorization booking cancellation request to the second network device. The method comprises receiving an authorization booking cancellation response from the second network device.

[0096] According to an embodiment of the third aspect, the authorization booking cancellation request comprises one or more of: the booking identifier; and the identifier of the loT server device.

[0097] According to an embodiment of the third aspect, the authorization booking cancellation response comprises: an indication notifying that the loT server device is authorized to perform the booking cancellation request; or a booking cancellation error response notifying that the loT server device is not authorized to perform the booking cancellation request.

[0098] According to an embodiment of the third aspect, the method comprises sending, to the loT server device, a booking removal indication, wherein the booking removal indication comprises the booking identifier, and a cause indication for a removal of a booking request associated with the booking identifier. The method comprises receiving a booking removal acknowledgement from the loT server device.

[0099] According to an embodiment of the third aspect, the booking identifier is a uniform resource identifier. According to an embodiment of the third aspect, the second network device comprises at least one of: a Home Subscriber Server, HSS, associated with the one or more loT devices; and a unified Data Management, UDM, associated with the one or more loT devices.

[0100] According to an embodiment of the third aspect, the third network device is a Service Capability Exposure Function, SCEF, device.

[0101] According to a fourth aspect of the invention, a method is provided. The method is performed by an Internet of Things, loT, server device. The method is for scheduling an appointment window for a communication session between the loT server device, and one or more loT devices. The method comprises sending a booking request to a first network device. The method comprises receiving a booking response from the first network device.

[0102] According to an embodiment of the fourth aspect, the booking request comprises one or more of: an identifier of the one or more loT devices; an identifier of the loT server device; a value corresponding to a Quality of Service, QoS, requirement for the communication session; an event type of which the loT server device shall be notified; a time interval indicating when the event type is to be performed; and a schedule type of the appointment window.

[0103] According to an embodiment of the fourth aspect, the value corresponding to the QoS requirement is related to one or more of: maximum allowed packet loss rate; minimum bit rate; minimum bandwidth; maximum transmission delay; maximum allowed jitter; maximum size of transferred data in the communication session; session length; and a maximum value of parallel booked session per cell.

[0104] According to an embodiment of the fourth aspect, the event type comprises one or more of: a reachability of the one or more loT devices being a Monitoring Event ReachabilityType “SMS”, and with an Idle Status Indication; and a reachability of the one or more loT devices being a Monitoring Event ReachabilityType “data”, and with an Idle Status Indication. According to an embodiment of the fourth aspect, the time interval comprises one or more of: a single time interval specified by a starting point timestamp, and an ending point timestamp; an interval list comprising one or more single time intervals; and a periodic time interval.

[0105] According to an embodiment of the fourth aspect, the schedule type of the appointment window indicates one or more of: an individual schedule of the one or more loT devices; and a distributed schedule of the one or more loT devices.

[0106] According to an embodiment of the fourth aspect, the booking response comprises one or more of: the booking identifier; and an indication that the appointment window is created according to the booking request, or an indication that the appointment window is created according to an alternative time.

[0107] According to an embodiment of the fourth aspect, the method comprises receiving a booking appointment notification from the first network device, the booking appointment notification comprises the identifier of the one or more loT devices, the one or more loT devices are ready to be booked. The method comprises sending a booking appointment acknowledgment to the first network device.

[0108] According to an embodiment of the fourth aspect, the method comprises sending a booked action report to the first network device, the booked action report comprises the identifier of the one or more loT devices, the booking identifier, and a success indication.

[0109] According to an embodiment of the fourth aspect, the method comprises receiving an appointment error notification from the first network device, if one or more conditions are not met; and subsequently sending an appointment error acknowledgement to the first network device.

[0110] According to an embodiment of the fourth aspect, the appointment error notification comprises one or more of: the booking identifier; the identifier of the one or more loT device; and an error indication. According to an embodiment of the fourth aspect, the method comprises sending, at a second time instance, a booking list query request to the first network device, the booking list query request comprises the identifier of the loT server device. The method comprises receiving a booking list query response, the booking list query response comprises one or more booking identifiers associated to the identifier of the loT server device.

[0111] According to an embodiment of the fourth aspect, the method comprises sending a booking query request to the first network device, the booking query request comprises the booking identifier. The method comprises receiving, if the loT server device is authorized to receive information related to the booking identifier, a booking query response from the first network device, the booking query response comprises the information related to the booking identifier.

[0112] According to an embodiment of the fourth aspect, the information related to the booking identifier comprises one or more of: the identifier of the one or more loT devices; the identifier of the loT server device; the value corresponding to the QoS requirement for the communication session; the event type of which the loT server device shall be notified; the time interval indicating when the event type is to be performed; and the schedule type of the appointment window.

[0113] According to an embodiment of the fourth aspect, the method comprises sending a booking cancellation request to the first network device, the booking cancellation request comprises the booking identifier. The method comprises receiving a booking cancellation response from the first network device, if the loT server device is authorized to request the booking cancellation request.

[0114] According to an embodiment of the fourth aspect, the method comprises receiving, from the first network device, a booking removal indication, the booking removal indication comprises the booking identifier, and a cause indication for a removal of a booking request associated with the booking identifier. The method comprises sending a booking removal acknowledgment to the first network device. According to an embodiment of the fourth aspect, the booking identifier is a uniform resource identifier.

[0115] According to a fifth aspect of the invention, a computer program is provided. The computer program comprises instructions, which when executed on a first network device, causes the first network device to perform the method according to any one of the embodiments of the third aspect of the invention.

[0116] According to a sixth aspect of the invention, a computer program is provided. The computer program comprises instructions, which when executed on an loT server device, causes the loT server device to perform the method according to any one of the embodiments of the fourth aspect of the invention.

[0117] According to a seventh aspect of the invention, a computer readable storage medium comprising a computer program according to the fifth aspect of the invention, and / or the sixth aspect of the invention.

[0118] At least one or more embodiments advantageously allows to have an overview of potential traffic in a cell.

[0119] At least one or more embodiments enable for the loT server to schedule an action during periods of time when the loT device and / or group of loT devices are reachable. Furthermore, the loT server considers the Quality of Service requirements needed by the action, thus success rate of the communication between the loT server and the loT device and / or group of loT device is increased. Furthermore, the invention allows to minimize the number of retransmission and buffering of not delivered downlink data between the loT server and the loT device and / or group of loT devices. Thus, one or more embodiments improve application and network resources utilization.

[0120] At least one or more embodiments allows to decrease the number of connections in UE-level which alleviates the load of the network and cell level as well as reducing energy consumption of the loT device. At least one or more embodiments allow to increase the success rate of communication between the loT device and / or group of loT devices, and the loT server. Indeed, a distribution of connections of a group of loT devices allows to make the sessions shorter since the cell bandwidth capacity is divided into fewer parts. Shorter sessions increase the success rate of the communication and reduces energy consumption of the loT device(s).

[0121] At least one or more embodiments provides a generic, reusable mechanism which can be utilized by Over-The-Top (OTT) procedures, such as network aware loT device Triggering or Firmware Update Over The Air (FOTA) of a group of loT devices.

[0122] At least one or more embodiments reduce energy consumption of loT devices.

[0123] Further objectives of, features of, and advantages with, the invention will become apparent when studying the following detailed disclosure, the drawings, and the appended claims. Those skilled in the art realize that different features of the invention can be combined to create embodiments other than those described in the following disclosure.

[0124] BRIEF DESCRIPTION OF THE DRAWINGS

[0125] The above, as well as additional objects, features and advantages of the invention, will further be understood through the following illustrative and non-limiting detailed description of embodiments of the inventions, with reference to the appended drawings, in which:

[0126] Figures 1 a and 1 b show a method performed by a first network device.

[0127] Figure 2 shows an embodiment of a communication architecture.

[0128] Figure 3 shows an embodiment of the booking request.

[0129] Figure 4 shows an embodiment of a method. Figure 5 shows an embodiment of a first network device.

[0130] Figure 6 shows an embodiment of a booking registry.

[0131] Figure 7 shows an embodiment of a booking calendar.

[0132] Figure 8 shows an embodiment of a notification monitor.

[0133] Figure 9 shows an embodiment of a booking response.

[0134] Figure 10 shows an embodiment of the method.

[0135] Figure 11 shows an embodiment of the method.

[0136] Figure 12 shows an embodiment of the method.

[0137] Figure 13 shows an embodiment of a booked action report.

[0138] Figure 14 shows an embodiment of the method.

[0139] Figure 15 shows an embodiment of an appointment error notification.

[0140] Figure 16 shows an embodiment of the method.

[0141] Figure 17 shows an embodiment of the method.

[0142] Figure 18 shows an embodiment of the method.

[0143] Figure 19 shows an embodiment of the method.

[0144] Figure 20 shows an embodiment of the method.

[0145] Figure 21 shows an embodiment of the method. Figure 22 shows an embodiment of the method.

[0146] Figure 23 shows a method performed by an loT server device.

[0147] Figure 24 shows an illustrative example of messages exchanges between a first network device, an loT server device, a second network device, and a third network device.

[0148] Figure 25 shows a first block diagram of a first network device.

[0149] Figure 26 shows a first block diagram of an loT server device.

[0150] Figure 27 shows a second block diagram of a first network device.

[0151] Figure 28 shows a second block diagram of an loT server device.

[0152] All figures are schematic, and generally only show parts which are necessary in order to elucidate the invention, wherein other parts may be omitted or merely suggested.

[0153] DETAILED DESCRIPTION

[0154] The invention will now be described more fully herein with reference to the accompanying drawings, in which certain embodiments are shown. This invention may, however, be embodiment in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0155] To overcome, the above-mentioned disadvantages of the prior art, the solution to be disclosed, in its aspects and embodiments, provides a first network device in a cellular network. The first network device is for scheduling a communication session between an loT server device, and one or more loT devices. The first network device is configured to receive a booking request from the loT server device. The first network device is also configured to create a booking identifier associated to the booking request, and an appointment window based on the booking request, if the loT server device is authorized to perform the booking request. The first network device is configured to send a booking response to the loT server device.

[0156] The present invention in its aspects and embodiments may be used for scheduling an appointment window for a communication session between the loT server device and the one or more loT devices. In particular, the invention allows to enable reachability of the one or more loT devices by creating an appointment window based on a booking request. The booking request may comprise requirements that needs to be fulfilled so as to allow the communication session between the loT server device and the one or more loT devices to be more efficient.

[0157] In Figure 1 , a flowchart depicting an embodiment of a method 100 is provided. The method 100 is performed by a first network device 200. The first network device 200 is part of a cellular network 210, as illustrated in Figure 2. The cellular network may be a Third Generation Partnership Project (3GPP) cellular network, such as a third generation (3G) cellular network, a fourth generation (4G) cellular network, fifth generation (5G) cellular network, or any future generation cellular network, such as a 3GPP sixth generation (6G) cellular network. The first network device 200 is for scheduling appointment window for a communication session between an Internet-of- Things (loT) server device 220, and one or more loT devices 230, 231 , 232. The communication session between the loT server device 220 and the one or more loT devices 230, 231 , 232 may comprise a Packet Data Network (PDN) session.

[0158] The loT server device 200 hosts a server software.

[0159] The one or more loT devices 230, 231 , 232 are connected to the cellular network 210. The one or more loT devices 230, 231 , 232 may each be a device for use in one or more application domains, these domains comprising, but not limited to, home, city, wearable technology, extended reality, industrial application, and healthcare.

[0160] By way of example, the loT device may be for a home, an office, a building or an infrastructure may be a baking scale, a coffee machine, a grill, a fridge, a refrigerator, a freezer, a microwave oven, an oven, a toaster, a water tap, a water heater, a water geyser, a sauna, a vacuum cleaner, a washer, a dryer, a dishwasher, a door, a window, a curtain, a blind, a furniture, a light bulb, a fan, an air-conditioner, a cooler, an air purifier, a humidifier, a speaker, a television, a laptop, a personal computer, a gaming console, a remote control, a vent, an iron, a steamer, a pressure cooker, a stove, an electric stove, a hair dryer, a hair styler, a mirror, a printer, a scanner, a photocopier, a projector, a hologram projector, a 3D printer, a drill, a hand-dryer, an alarm clock, a clock, a security camera, a smoke alarm, a fire alarm, a connected doorbell, an electronic door lock, a lawnmower, a thermostat, a plug, an irrigation control device, a flood sensor, a moisture sensor, a motion detector, a weather station, an electricity meter, a water meter, and a gas meter.

[0161] By further ways of example, the loT device may be for use in a city, urban, or rural areas may be connected street lighting, a connected traffic light, a traffic camera, a connected road sign, an air control / monitor, a noise level detector, a transport congestion monitoring device, a transport controlling device, an automated toll payment device, a parking payment device, a sensor for monitoring parking usage, a traffic management device, a digital kiosk, a bin, an air quality monitoring sensor, a bridge condition monitoring sensor, a fire hydrant, a manhole sensor, a tarmac sensor, a water fountain sensor, a connected closed circuit television, a scooter, a hoverboard, a ticketing machine, a ticket barrier, a metro rail, a metro station device, a passenger information panel, an onboard camera, and other connected device on a public transport vehicle.

[0162] As further way of example, the loT device may be a wearable device, or a device related to extended reality, wherein the device related to extended reality may be a device related to augmented reality, virtual reality, merged reality, or mixed reality. Examples of such loT devices may be a smart-band, a tracker, a haptic glove, a haptic suit, a smartwatch, clothes, eyeglasses, a head mounted display, an ear pod, an activity monitor, a fitness monitor, a heart rate monitor, a ring, a key tracker, a blood glucose meter, and a pressure meter.

[0163] As further ways of example, the loT device may be an industrial application device wherein an industrial application device may be an industrial unmanned aerial vehicle, an intelligent industrial robot, a vehicle assembly robot, and an automated guided vehicle.

[0164] As further ways of example, the loT device may be a transportation vehicle, wherein a transportation vehicle may be a bicycle, a motor bike, a scooter, a moped, an auto rickshaw, a rail transport, a train, a tram, a bus, a car, a truck, an airplane, a boat, a ship, a ski board, a snowboard, a snow mobile, a hoverboard, a skateboard, roller- skates, a vehicle for freight transportation, a drone, a robot, a stratospheric aircraft, an aircraft, a helicopter and a hovercraft.

[0165] As further ways of example, the loT device may be a health or fitness device, wherein a health or fitness device may be a surgical robot, an implantable medical device, a non-invasive medical device, and a stationary medical device which may be: an in- vitro diagnostic device, a radiology device, a diagnostic imaging device, and an x-ray device.

[0166] The method 100 comprises receiving 110 a booking request 240 from the loT server device 220 for the communication session. In Figure 3, an embodiment of the booking request 240 is illustrated. The booking request 240 extends the 3GPP Monitoring Event procedure as defined, for example, in 3GPP TS 29 122 v18.3.0 section 4.4.2. In particular, the booking request 240, as disclosed herein, may be comprised in a HTTP request, such as a HTTP POST request message targeting a “Monitoring Event Subscriptions” resource.

[0167] The booking request 240 may comprise an identifier 310 of the one or more loT devices 230, 231 , 232.

[0168] In an embodiment, the identifier 310 is a single identifier for each one of the one or more loT devices 230, 231 , 232. The single identifier may be a mobile station international subscriber directory number MSISDN. The single identifier may be a 3GPP external device identifier as defined, for example, in 3GPP TS 29122 V18.3.0. In another embodiment, the identifier 310 is a group identifier identifying the one or more loT devices 230, 231 , 232. The group identifier may be an MSISDN range. The group identifier may be a 3GPP external group identifier as defined, for example, in 3GPP TS 29 122 V18.3.0. In another embodiment, the identifier 310 is a combination of one or more single identifiers and the group identifier.

[0169] The booking request 240 may comprise an identifier 320 of the loT server device 220. The identifier 320 of the loT server device 220 may be a callback Uniform Resource Identifier (URI) associated with the booking request 240. In an embodiment, the loT server device 220 performs, before step 110 of the method 100, a registration with the first network device 200. The registration may comprise the loT server device 220 sending a registration request. The registration request may comprise the callback URI associated with the booking request 240.

[0170] The booking request 240 may comprise a value corresponding to a Quality of Server (QoS) requirement 330 for the communication session. The value corresponding to the QoS requirement 330 enables to specify communication parameters. The value corresponding to the QoS requirement 330 may be related to one or more of: maximum allowed packet loss rate, minimum bit rate, minimum bandwidth, maximum transmission delay, maximum allowed jitter, maximum size of transferred data in the communication session, session length, and a maximum value of parallel booked session per cell.

[0171] For example, the maximum allowed packet loss rate is a maximum percentage of packets of data lost travelling between the one or more loT devices 230, 231 , 232, and the loT server device 220.

[0172] For example, the minimum bit rate may is a minimum number of bits that are to be processed by the loT server device 220, and / or the one or more loT devices 230, 231 , 232.

[0173] For example, the minimum bandwidth is a minimum rate of message delivery between the loT server device 220, and the one or more loT devices 230, 231 , 232.

[0174] For example, the maximum allowed jitter is a maximum allowed variation of delay between two packets.

[0175] For example, the maximum size of transferred data is a maximum size in bytes of messages transmitted between the loT server device 220 and the one or more loT devices 230, 231 , 232 over the communication session.

[0176] For example, the session length is a time duration of the communication session between the loT server device 220, and the one or more loT devices 230, 231 , 232.

[0177] For example, the maximum value of parallel booked session per cell is a number value of parallel booked session per cell which once reached and / or exceeded no further messages related to the booking request 240 are sent to the loT server device 220.

[0178] The booking request 240 may comprise an event type 340 of which the loT server device 220 shall be notified. The event type 340 enables to indicate an event type of which occurrence the loT server device 220 shall be notified. The event type 340 may be a Reachable for Data or Connected PDN Session, such as 3GPP Monitoring Event ReachabilityType- as defined, for example, in 3GPP TS 29.122 v18.3.0.

[0179] In an embodiment, the event type 340 comprises a reachability of the one or more loT devices 2301 , 231 , 232 being a Monitoring Event ReachabilityType “SMS”, and an Idle Status Indication. For example, the reachability Monitoring Event ReachabilityType “SMS”, with Idle Status Indication is a Monitoring Event ReachabilityType “SMS” as defined in 3GPP TS 29.122 v 18.3.0.

[0180] In an embodiment, the event type 340 comprises a reachability of the one or more loT devices 230, 231 , 232 being a Monitoring Event ReachabilityType “data”, and an Idle Status Indication. For example, the reachability Monitoring Event ReachabilityType “data” with an Idle Status Indication is a Monitoring Event ReachabilityType “Data” as defined in 3GPP TS 29.122 v18.3.0.

[0181] In an embodiment, the event type 340 comprises the reachability of the one or more loT devices 230, 231 , 232 being Monitoring Event ReachabilityType “SMS”, and an Idle Status Indication, and the reachability of the one or more loT devices 230, 231 , 232 Monitoring Event ReachabilityType “data”, with an Idle Status Indication.

[0182] The booking request 240 may comprise a time interval 350 indicating when the event type 340 is to be performed. The time interval 350 enables to specify one or more possible occurrences of the event type 340.

[0183] In an embodiment, the time interval 350 comprises one or more of a single time interval specified by a starting point timestamp, and an ending point timestamp. For example, the starting point timestamp corresponds to the beginning of the appointment window. For example, the ending point timestamp corresponds to the ending of the appointment window. The starting point timestamps and the ending point timestamp may be defined in seconds, minutes, hours, days, and / or any other time measure. For example, the single time interval corresponds to a single time interval specified by a starting point corresponding to 2021-03-10 20:00, and an ending point timestamp corresponding to 2021-03-11 08:00 - thus, the single time interval in this illustrative example, corresponds to 2021 -03-10 20:00; 2021 -03-11 08:00). In other words, the single time interval is, in this illustrative example, between March 10th, 2021 , at 8:00pm and March 11th, 2021 , at 8:00 am.

[0184] In an embodiment, the time interval 350 comprises an interval list comprising one or more single time intervals. For example, the interval list corresponds to a list comprising of a maximum size defined by a value d (e.g., d equals 32). The value d may be chosen by a telecommunication engineer. In the event, the interval list is superior to d, the list may be divided into separate booking requests.

[0185] In an embodiment, the time interval 350 comprises a periodic time interval. For example, the periodic time interval comprises a single time interval, a time value in seconds, an ending point timestamp. In an illustrative example, the periodic time interval corresponds to [(2021-03-10 08:00; 2021 -03-10 10:00); 43200; 2021 -03-15 10:00],

[0186] In an embodiment, the time interval 350 comprise the single time interval, the interval list, and / or the periodic time interval.

[0187] The booking request 240 may comprise a schedule type 360 of the appointment window 260. The schedule type 360 enables to specify whether the loT server device 220 shall be notified within the time interval 350 of an occurrence of the event type 340. The schedule type 360 may be used in the event the time interval 250 comprises: more than one single time interval, and / or the interval list comprising more than one single time intervals.

[0188] In an embodiment, the schedule type 360 indicates one or more of an individual schedule of the one or more loT devices 230, 231 , 232. For example, the individual schedule of an loT device of the one or more loT devices 230, 231 , 232 enables to overview the occurrence within which the loT device is already scheduled for the event type 340. In other words, the first network device 200 is able to consider other bookings of the loT device and the communication session length, so as to avoid too frequent booking occasions. The first network device 200 may be able to merge several bookings of the same loT device into one appointment window. The first network device 200 may consider, for an loT device, historical network load information and communication session length so as to book the loT device during an idle period or a less loaded period of the same loT device. The skilled person would understand that the merging and / or booking during idle or less loaded periods may be performed for each one of the one or more loT devices 230, 231 , 232.

[0189] In an embodiment, the schedule type 360 indicates one or more of a distributed schedule of the one or more loT devices 230, 231 , 232. For example, the distributed schedule of the one or more loT devices 230, 231 , 232 enables to perform more efficiently an application over a group of the one or more loT device 230, 231 , 232. The distributed schedule of the one or more loT devices 230, 231 , 232 may be based on each individual schedule of the one or more loT devices 230, 231 , 232. The distributed schedule of the one or more loT devices 230, 231 , 232 may be based on a location of each one loT devices in the group of the one or more loT devices 230, 231 , 232. Considering the location of each of the one or more loT devices 230, 231 , 232 in the group of the one or more of the loT devices 230, 231 , 232 may allow to minimize network load within a cell comprising the group of the one or more of the loT devices 230, 231 , 232. In particular, the distributed schedule may be useful when a same action is required on the group of one or more loT devices 230, 231 , 232. The action may be updating the one or more loT devices 230, 231 , 232, such as a firmware update over the air (FOTA).

[0190] In an embodiment, the method 100 comprises sending 111 an authorization booking request 410 to a second network device 400. In an embodiment, the method 100 comprises receiving 112 an authorization booking response 420 from the second network device 400. In Figure 4, an embodiment of the step 111 and the 112 of the method 100 is provided. The step 111 and the step 112 of the method 100 enable to verify whether the loT server device 220 is authorized to perform the booking request 240 for the one or more loT devices 230, 231 , 232.

[0191] In an embodiment, the authorization booking request 410 comprises the identifier 320 of the one or more loT devices 230, 231 , 232. In an embodiment, the authorization booking request 410 comprises the identifier 320 of the loT server device 220. In an embodiment, the authorization booking request 410 comprises one or more of the event type 340. In an embodiment, the authorization booking request 410 comprises one or more of the value corresponding to the QoS requirement 330. In an embodiment, the authorization booking request 410 comprises one or more of: the identifier 310 of the one or more loT devices 230, 231 ,232, the identifier 320 of the loT server device 220, the event type 340, the value corresponding to the QoS requirement 330.

[0192] In an embodiment, the authorization booking response 420 comprises an indication notifying that the loT server device 220 is authorized to perform the booking request 240. In an embodiment, the authorization booking response 420 comprises a booking error response notifying that the loT server device 220 is not authorized to perform the booking request 240. The method 100 comprises creating 113 a booking identifier 250 associated to the booking request 240, and an appointment window 260 based on the booking request 240, if the loT server device 220 is authorized to perform the booking request 240.

[0193] In Figure 5, an embodiment of the first network device 200 is provided. The first network device 200 comprises one or more of: a booking registry 510, a booking calendar 520, a QoS monitor 530, and a notification monitor 540.

[0194] The booking register 510 may comprise a booking entry 610. In Figure 6, and embodiment of the booking registry 510 is provided. The skilled person would understand that even if there is only one booking entry illustrated in Figure 6, it is possible to have only one booking entry, or a multitude of booking entries (e.g., more than one). The booking entry 610 is associated with information 620 related to the booking request 240. The information 620 related to the booking request 240 may comprise the booking identifier 250. The information 620 related to the booking request 240 may comprise the identifier 310 of the one or more loT devices 230, 231 , 232. The information 620 related to the booking request 240 may comprise the identifier 320 of the loT server device 220. The information 620 related to the booking request 240 may comprise the value corresponding to the QoS requirement 330 for the communication session. The information 620 related to the booking request 240 may comprise the event type 340 of which of the loT server device 220 shall be notified. The information 620 related to the booking request 240 may comprise the time interval 350 indicating when the event type 240 is to be performed. The information 620 related to the booking request 240 may comprise the schedule type 360. The information 620 related to the booking request 240 may comprise one or more of: the identifier 250, the identifier 310 of the one or more loT devices 230, 231 , 232, the identifier 320 of the loT server device 220, the value corresponding to the QoS requirement 330 for the communication session, the event type 340 of which the loT server device 220 shall be notified, the time interval 350 indicating when the event type 240 is to be performed, and the schedule type 360.

[0195] The skilled person would understand that if there are more than one booking requests, such as the booking request 240, the booking registry 510 may then comprise corresponding booking entries to the more than one booking entries. For example, the booking registry 510 comprises a lookup table. The lookup table is illustrated in Table 1. In an embodiment, the lookup table is stored in the first network device 200. The lookup table may comprise, for each of the booking entries, an entry for a booking identifier (e.g., the booking identifier 250), an entry for an identifier of the one or more loT devices (e.g., the identifier 310 of the one or more loT devices 230, 231 , 232), an entry for an identifier of an loT server device (e.g., the identifier 320 of the loT server device 220), an entry for a value corresponding to a QoS requirement (e.g., the value corresponding to the QoS requirement 330), an entry for an event type of which the loT server device wants to be notified (e.g., the event type 340), an entry for a time interval indicating when the event type is to be performed (e.g., the time interval 350), and an entry for a schedule type (e.g., the schedule type 360).

[0196] In an embodiment, the booking calendar 520 comprises a calendar entry (710, 711 , 712) for each of the one or more loT devices 230, 231 , 232. In Figure 7, an embodiment of the booking calendar 520 is provided.

[0197] The booking calendar 510 may comprises a calendar entry 710, 711 , 712 for each of the one or more loT devices 230, 231 , 232. For example, as illustrated in Figure 7, calendar entry 710 is associated to loT device 230, calendar entry 711 is associated to loT device 231 , and calendar entry 712 is associated to loT device 232. The skilled person would understand that even if there are only three calendar entries 710, 711 , 712, illustrated in Figure 7, it is possible to have only one calendar entry, or multiple calendar entries (e.g., more than one).

[0198] The calendar entry 710, 711 , 712 may comprise a first list 720, 721 , 722 of one or more booking identifiers. The first list 720, 721 , 722 of one or more booking identifiers may comprise the booking identifier 250 created in the step 120 of the method 100. For example, as illustrated in Figure 7, the list 720 comprises a booking identifier booking_id_1 , the list 721 comprises booking identifier booking_id_1 , and the list 722 comprises the booking identifier booking_id_1 and booking identifier booking_id_2. The booking identifier booking_id_1 may correspond to the booking identifier 250 created in the step 120 of the method 100. The booking identifier booking_identifier_2 may correspond to another booking identifier based on another booking request sent by either the loT server device 220 or another loT server device.

[0199] Each booking identifier of the first list 720, 721 , 722 of one or more booking identifiers may be associated with a list 730, 731 , 732 of booking notifications.

[0200] The QoS monitor 530 may comprise one or more QoS statistics related to the cellular network 210. The one or more QoS statistics may comprise one or more of: number of parallel sessions related to appointment window; available uplink bandwidth capacity in the cellular network 210; and available downlink bandwidth capacity in the cellular network 210.

[0201] The notification monitor 540 may comprise for each of the one or more loT devices

[0202] 230, 231 , 232 a list of one or more Monitoring Event type records. In Figure 8, an embodiment of the notification monitor 540 is provided. The notification calendar 540 may comprise a notification record 810, 811 , 812 for each of the one or more loT devices 230, 231 , 232. For example, as illustrated in Figure 8, notification record 810 is associated with loT device 230, notification record 811 is associated with loT device

[0203] 231 , and notification record 812 is associated with loT device 232. The skilled person would understand that even if there are only three notification records 810, 811 , 812, illustrated in figure 8, it is possible to have only one notification record, or multiple notification records (e.g., more than one).

[0204] The notification record 810, 811 , 812 may comprise a list 820, 821 , 822 of one or more Monitoring Event type records. The Monitoring Event type may correspond to the event type 340. For example, as illustrated in Figure 8, the list 820 comprises a Monitoring Event type record Monitoring Event_event_type_1 , the list 821 comprises a Monitoring Event type record Monitoring Event_event_type_1 , and the list 822 comprises a Monitoring Event type record Monitoring Event_event_type_1 and a Monitoring Event type record Monitoring Event_event_type_2. Each of the one or more Monitoring Event records may comprise a second list 830, 831 , 832 of one or more booking identifiers. The second list 830, 831 , 832 may comprise the booking identifier 250 created in the step 120 of the method 100. For example, as illustrated in Figure 8, the list 830 comprises booking identifier booking_id_ 1, the list 831 comprises booking identifier booking_id_1 , and the list 832 comprises the booking identifier booking_id_1 and booking identifier booking_id_2. The booking identifier booking_id_1 may correspond to the booking identifier 250 created in the step 120 of the method 100. The booking identifier booking_identifier_2 may correspond to another booking identifier based on another booking request sent by either the loT server device 220 or another loT server device.

[0205] In an embodiment, the step 113 of the method 100 comprises creating a booking entry 610 in the booking register 510, and / or a calendar entry 710, 711 , 712 in the booking calendar 520 for each of the one or more loT devices 230, 231 , 232.

[0206] The method 100 comprises sending 114 a booking response 270 to the loT server device 220. In Figure 9, an embodiment of the booking response 270 is provided. The booking response 270 may comprise the booking identifier 250 created in the step 120 of the method 100. The booking response may comprise an indication 910. The indication 910 may indicate that the appointment window 260 is create based on the booking request 240 received in the step 113 of the method 100. The indication 910 may indicate that the appointment window 260 is create based on an alternative time interval. The booking response 270 extends the 3GPP Monitoring Event procedure as defined, for example, in 3GPP TS 29 122 v 18.3.0 section 4.4.2. In particular, the booking response 270, as disclosed herein, may be comprised in a HTTP response as defined, for example, in 3GPP TS 29 122 v18.3.0 section 4.4.2, such as in a 201 Created response, a 207 Multi-Status response, a 403 Forbidden response, a 412 Precondition Failed response, and a 200 OK response.

[0207] In an embodiment, the method 100 comprises updating 115 the notification monitor 540. In Figure 10, an embodiment of the step 115 is provided. The step 115 of updating 115 the notification monitor 540 of the method 100 may comprise sending, to a third network device 1000, a Monitoring Event Configuration Request 1010. The Monitoring Event Configuration Request 1010 may correspond to a Monitoring Event Configuration Request as defined, for example, in 3GPP TS 29.122 v18.3.0. The Monitoring Event Configuration Request 1010 may comprise the identifier 310 of the one or more loT devices 230, 231 , 232. The Monitoring Event Configuration Request 1010 may comprise the event type 340. The Monitoring Event Configuration Request 1010 may comprise the identifier 210 of the one or more loT devices 230, 231 , 232, and the event type 340. The step 115 of updating 115 the notification monitor 540 of the method 100 may comprise receiving, from the third network device 1000, a Monitoring Event Configuration Response 1020. The Monitoring Event Configuration Response 1020 may correspond to a Monitoring Event Configuration as defined, for example, in 3GPP TS 29.122 v18.3.0. The Monitoring Event configuration Response 1020 may comprise a monitoring identifier for each of the one or more loT devices 230, 231 , 232. The step 115 of the method 100 may comprise sending to the third network device 1000 the Monitoring Event Configuration Request 1010, and receiving from the third network device 1000 the Monitoring Event Configuration Response 1020.

[0208] In an embodiment, the method 100 comprises updating 116 the booking calendar 520. The step 116 of updating the booking calendar 520 of the method 100 may comprise adding the booking identifier 250 to the calendar entry 710, 71 1 , 712 for each of the one or more loT devices 230, 231 , 232.

[0209] In an embodiment, the method 100 comprises receiving 120, at a first time instance, a Monitoring Event notification 1110 related to the one or more loT devices 230, 231 , 232, from the third network device 1000. The Monitoring Event notification 1110 may correspond to a Monitoring Event notification as defined, for example, in 3GPP TS 29.122 v18.3.0. The Monitoring Event notification 1110, illustrated in Figure 11 , may comprise the event type 340 to be notified of. The Monitoring Event notification may comprise the identifier 310 of the one or more loT devices 230, 231 , 232.

[0210] In an embodiment, the method 100 comprises determining 121 one or more booking identifiers 1120 associated to the one or more loT devices 230, 231 , 232. Each of the one or more booking identifiers 1120 may be associated with the time interval 350 which comprises the first time instance when the Monitoring Event notification 1110 has been received in the step 120 of the method 100. Furthermore, each of the one or more booking identifiers 1120 may be associated with the event type 340 comprised in the Monitoring Event notification 1110 received in the step 150 of the method 100. In an embodiment, the method 100 comprises sending 122 a booking appointment notification 1130 to the loT server device 220. The booking appointment notification 1130 may comprise the identifier 310 of the one or more loT devices 230, 231 , 232 associated with the one or more booking identifiers 1120 determined in the step 121 of the method 100.

[0211] In an embodiment, the method 100 comprises receiving 123 a booking appointment acknowledgment from the loT server device 220.

[0212] In an embodiment, the method 100 comprises updating 124 the QoS monitor 540 by adding an “action-started” indication in relation to the one or more loT devices 230, 231 , 232 associated with the one or more booking identifier 1120 determined in the step 121 of the method. This allows to keep track of parallel action in the cellular network 210.

[0213] In an embodiment, the method 100 comprises receiving 130 a booked action report 1210 from the loT server device 220. In Figure 12, an embodiment of the step 130 of the method 100 is provided. In Figure 13, an embodiment of the booked action report 1210 is provided. The booked action report 1210 may comprise the identifier 310 of the one or more loT devices 230, 231 , 232. The booked action report 1210 may comprise the booking identifier 250. The booked action report 1210 may comprise a success indication 1310. The success indication 1310 may indicate whether an action scheduled for the one or more loT devices 230, 231 , 232 based on whether the booking request 240 associated to the booking identifier 250 has been performed with success.

[0214] In an embodiment, the method 100 comprises updating 131 the booking calendar 520.

[0215] For example, the updating 131 the booking calendar 520 comprises:

[0216] - determining the calendar entry 710, 711 , 712 of the one or more loT devices 230, 231 , 232 identified in the received booked action report 1210 of the step 160 of the method 100;

[0217] - determining the first list 720, 721 , 722 of one or more booking identifiers associated to the one or more loT devices 230, 231 , 232; and deleting the booking identifier 250, identified in the received booked action report 1210 of the step 160 of the method 100, in each of the first list 720, 721 , 722.

[0218] In an embodiment, the method 100 comprises updating 132 the notification monitor 540. For example, updating 132 the notification monitor 540 comprises:

[0219] - determining the notification record 810, 811 , 812 of the one or more loT devices 230, 231 , 232 identified in the received booked action report 1210 of the step 160 of the method 100;

[0220] - determining the list 820, 821 , 822 of one or more Monitoring Event types records associated to the one or more loT devices 230, 231 , 232;

[0221] - deleting the booking identifier 250, identified in the received booked action report 1210 of the step 160 of the method 100, in each of the list 820, 821 , 822.

[0222] In an embodiment, the method 100 comprises updating 133 the QoS monitor 530. For example, updating 133 the QoS monitor 530 comprises adding an “action-finished” indication in relation to the one or more loT devices 230, 231 , 232 identified in the received booked action report 1210 of the step 130 of the method 100.

[0223] In an embodiment, the method 100 comprises sending 140 an appointment error notification 1410 to the loT server device 220, if one or more conditions are not met. The appointment error notification 1410 may notify that a created appointment window, such as the appointment window 260 created in the step 113 of the method 100, will not be performed according to the received booking request 240 received in the step 110 of the method 100. In Figure 14, an embodiment of the step 140 of the method 100 is provided. In Figure 15, an embodiment of the appointment error notification 1410 is provided. The appointment error notification 1410 may comprise the booking identifier 250. The appointment error notification 1410 may comprise an error indication 1510. The error indication 1510 may indicate the one or more conditions that are not met. The one or more conditions that are not met may comprise one or more of: the identifier 310 of the one or more loT devices 230, 231 , 232; the value corresponding to the QoS requirement 330; the event type 340, the time interval 350; the schedule type 360. For example, a Monitoring Event notification, such as the Monitoring Event notification 1110, may be sent to the first network device 200 outside of the time interval 350.

[0224] In an embodiment, the method 100 comprises subsequently receiving 141 an appointment error acknowledgment 1420 from the loT server device 220. The loT server device 220 may acknowledge receipt of the appointment error notification 1410 sent in the step 140 of the method 100.

[0225] In an embodiment, the method 100 comprises receiving 150, at a second time instance, a booking list query request 1610 from the loT server device 220. In Figure 16, an embodiment of the step 150 is provided. The booking list query request 1610 may comprise the identifier 320 of the loT server device 220.

[0226] In an embodiment, the method 100 comprises determining 151 , if the loT server device 220 is authorized, one or more booking identifiers 1820 associated with the identifier 320 of the loT server device 220. Each of the time interval 350 of the determined one or more booking identifiers 1620 may comprise the second time instance. Each of the one or more booking identifiers 1620 may be associated with the identifier 320 of the loT server device 220 comprised in the booking list query request 1610 received in the step 150 of the method 100.

[0227] In an embodiment, the method 100 comprises sending 152, if the loT server device 220 is authorized, a booking list query response 1630. The booking list query response 1630 may comprise the determined one or more booking identifiers 1620 in the step 151 of the method 100.

[0228] In an embodiment, the method 100 comprises sending 153 an authorization booking list query request 1710 to the second network device 400. In an embodiment, the method 100 comprises receiving 154 an authorization booking list query response 1720. In Figure 17, an embodiment of the step 153 of the method 100 and the step 154 of the method 100 are provided.

[0229] The step 153 and the step 154 of the method 100 enable to verify whether the loT server device 220 is authorized to perform the booking list query request 1610. In an embodiment, the authorization booking list query request 1710 comprises the identifier 320 of the loT server device 220.

[0230] In an embodiment, the authorization booking list query response 1720 comprises an indication notifying that the loT server device 220 is authorized to perform the booking list query request 1610. In another embodiment, the authorization booking list query response 1720 comprises a booking query list error response notifying that the loT server device 220 is not authorized to perform the booking list query request 1610.

[0231] In an embodiment, the method 100 comprises receiving 160 a booking query request 1810 from the loT server device 220. The booking query request 1810 may comprise the booking identifier 250.

[0232] In an embodiment, the method 100 comprises sending 161 , if the loT server device 220 is authorized to receive information related to the booking identifier 250, a booking query response 1820 to the loT server device 220. The booking query response 1820 may comprise information related to the booking identifier 250. In Figure 18, an embodiment of the step 161 of the method 100 is provided. The information related to the booking identifier 250 may comprise one or more of: the identifier 310 of the one or more loT devices 230, 231 , 232; the identifier 320 of the loT server device 220; the value corresponding to the QoS requirement 330; the event type 340; the time interval 350; and the schedule type 360.

[0233] In an embodiment, the method 100 comprises sending 162 an authorization booking query request to the second network device 400. In an embodiment, the method 100 comprises receiving 163 an authorization booking query response from the second network device 400. In Figure 19, an embodiment of the step 162 of the method 100 and the step 163 of the method 100 are provided.

[0234] The step 162 and the step 163 of the method 100 enable to verify whether the loT server device 220 is authorized to perform the booking query request 1810.

[0235] In an embodiment, the authorization booking query request 1910 comprises one or more of: the booking identifier 250, and / or the identifier 320 of the loT server device 220.

[0236] In an embodiment, the authorization booking query response 1920 comprises an indication notifying that the loT server device 220 is authorized to perform the booking query request 1810. In another embodiment, the authorization booking query response 1920 comprises a booking query error response notifying that the loT server device 220 is not authorized to perform the booking query request 1810.

[0237] In an embodiment, the method 100 comprises receiving 170 a booking cancellation request 2010. The booking cancellation request 2010 may comprise the booking identifier 250.

[0238] In an embodiment, the method 100 comprises deleting 171 a booking entry associated with the booking identifier 250, if the loT server device 220 is authorized to request the booking cancellation request 2010. For example, deleting 171 may comprise one or more of:

[0239] - deleting, from the booking register 510, the booking entry 610 associated to the booking identifier 250;

[0240] - deleting, from the booking calendar 520, the booking identifier 250 from the first list 720, 721 , 722 of the one or more booking identifiers, and deleting the list 730, 731 , 732 of booking notifications associated with the deleted booking identifier 250; and / or

[0241] - deleting, from the notification monitor 540, the booking identifier 250 from the second list 830, 831 , 832 of one or more booking identifiers.

[0242] In an embodiment, the method 100 comprises sending 172 a booking cancellation response 2020 to the loT server device 220, if the loT server device 220 is authorized to request the booking cancellation request 2010 received in the step 170 of the method 100.

[0243] In Figure 20, an embodiment of the step 170, the step 171 , and the step 172 of the method 100 is provided.

[0244] In an embodiment, the method 100 comprises sending 173 an authorization booking cancellation request 2110 to the second network device 400. In an embodiment, the method 100 comprises receiving 174 an authorization booking cancellation response 2120 from the second network device 400. In Figure 21 , an embodiment of the step 173 of the method 100 and the step 174 of the method 100 are provided.

[0245] The step 173 and the step 174 of the method 100 enable to verify whether the loT server device 220 is authorized to perform the booking cancellation request 2010. In an embodiment, the authorization booking cancellation request 2110 comprises one or more of: the booking identifier 250, and / or the identifier 320 of the loT server device 220.

[0246] In an embodiment, the authorization booking cancellation response 2120 comprises an indication notifying that the loT server device 220 is authorized to perform the booking cancellation request 2010. In another embodiment, the authorization booking cancellation response 2120 comprises a booking cancellation error response notifying that the loT server device 220 is not authorized to perform the booking cancellation request 2010.

[0247] In an embodiment, the method 100 comprises sending 180 to the loT server device 220, a booking removal indication 2210. The booking removal indication 2210 may comprise the booking identifier 250, and a cause indication for a removal of a booking request associated with the booking identifier 250. For example, the booking identifier 250 may be removed from the booking register 510, the booking calendar 520, and / or the notification monitor 540, in the event the ending point timestamp of the time interval 350 has already been reached. In an embodiment, the method 100 comprises receiving 181 a booking removal acknowledgement 2220 from the loT server device 220. In Figure 22, an embodiment of the step 180 and the step 181 of the method 100 is provided.

[0248] In an embodiment, the booking identifier 250 is a uniform resource identifier.

[0249] In an embodiment, the second network device 400 comprises at least one of: a Home Subscriber Server (HSS) associated with the one or more loT devices 230, 231 , 232; and a Unified Data Management (UDM) associated with the one or more loT devices 230, 231 , 232.

[0250] In an embodiment, the third network device 1000 is a Service Capabilities Exposure Function (SCEF) device. In an alternative embodiment, the third network device 1000 is a 3GPP Network Exposure Function (NEF) device.

[0251] In an embodiment, the step 113 of the method 100 is performed simultaneously to the step 114 of the method 100. In an embodiment, the step 113 of the method 100 is performed before the step 114 of the method 100. In an embodiment, the step 113 of the method 100 is performed after the step 114 of the method 100.

[0252] In an embodiment, the step 113, the step 114, the step 115, the step 116 of the method 100 are performed simultaneously. In an embodiment, the step 113, the step 114, the step 115, the step 116 of the method 100 are performed in varying order, e.g., the step 115 before the step 116, or the step 115 after the step 116.

[0253] In an embodiment, the step 121 of the method 100 is performed simultaneously to the step 122 of the method 100. In an embodiment, the step 121 of the method 100 is performed before the step 122 of the method 100. In an embodiment, the step 121 of the method 100 is performed after the step 122 of the method 100.

[0254] In an embodiment, the step 121 , the step 122, the step 123, the step 124 of the method 100 are performed simultaneously. In an embodiment, the step 122, the step 123, the step 124 of the method 100 are performed in varying order, e.g., the step 123 before the step 124, or the step 123 after the step 124.

[0255] In an embodiment, the step 131 , the step 132, and the step 133 of the method 100 are performed simultaneously. In an embodiment, the step 131 , the step 132, the step 133 of the method 100 are performed in various order, e.g., the step 131 before the step 132, or the step 131 after the step 132.

[0256] In an embodiment, the steps 153 and 154 are performed before the step 151 of the method 100.

[0257] In an embodiment, the steps 162 and 163 are performed before the step 161 of the method 100.

[0258] In an embodiment, the step 171 and the step 172 of the method 100 are performed simultaneously. In an embodiment, the step 171 of the method 100 is performed before the step 172 of the method 100. In an embodiment, the step 171 of the method 100 is performed after the step 172 of the method 100. In an embodiment, the steps 173 and 174 of the method 100 are performed before the step 171 of the method 100.

[0259] In an embodiment, the steps 110-116 of the method 100 are performed before the steps 120-124 of the method 100. In an embodiment, the steps 110-116 of the method 100 are performed before the steps 130-133 of the method 100. In an embodiment, the steps 110-116 of the method 100 are performed before the steps 140-141 of the method 100. In an embodiment, the steps 110-116 of the method 100 are performed before the steps 150-154 of the method 100. In an embodiment, the steps 110-116 of the method 100 are performed before the steps 160-163 of the method 100. In an embodiment, the steps 110-116 of the method 100 are performed before the steps 170-174 of the method 100. In an embodiment, the steps 110-116 of the method 100 are performed before the steps 180-181 of the method 100.

[0260] In an embodiment, the steps 120-124 of the method 100 are performed before the steps130-133 of the method 100. In an embodiment, the steps 120-124 of the method 100 are performed before the steps 140-141 of the method 100. In an embodiment, the steps 120-124 of the method 100 are performed before the steps 150-154 of the method 100. In an embodiment, the steps 120-124 of the method 100 are performed before the steps 160-163 of the method 100. In an embodiment, the steps 120-124 of the method 100 are performed before the steps 170-174 of the method 100. In an embodiment, the steps 120-124 of the method 100 are performed before the steps 180-181 of the method 100.

[0261] In an embodiment, the steps 130-133 of the method 100 are performed before the steps 120-124 of the method 100. In an embodiment, the steps 130-133 of the method 100 are performed before the steps 140-141 of the method 100. In an embodiment, the steps 130-133 of the method 100 are performed before the steps 150-154 of the method 100. In an embodiment, the steps 130-133 of the method 100 are performed before the steps 160-163 of the method 100. In an embodiment, the steps 130-133 of the method 100 are performed before the steps 170-174 of the method 100. In an embodiment, the steps 130-133 of the method 100 are performed before the steps 180-181 of the method 100. In an embodiment, the steps 140-141 of the method 100 are performed before the steps 120-124 of the method 100. In an embodiment, the steps 140-141 of the method 100 are performed before the steps 130-133 of the method 100. In an embodiment, the steps 140-141 of the method 100 are performed before the steps 150-154 of the method 100. In an embodiment, the steps 140-141 of the method 100 are performed before the steps 160-163 of the method 100. In an embodiment, the steps 140-141 of the method 100 are performed before the steps 170-174 of the method 100. In an embodiment, the steps 140-141 of the method 100 are performed before the steps 180-181 of the method 100.

[0262] In an embodiment, the steps 150-154 of the method 100 are performed before the steps 120-124 of the method 100. In an embodiment, the steps 150-154 of the method 100 are performed before the steps 130-133 of the method 100. In an embodiment, the steps 150-154 of the method 100 are performed before the steps 140-141 of the method 100. In an embodiment, the steps 150-154 of the method 100 are performed before the steps 160-163 of the method 100. In an embodiment, the steps 150-154 of the method 100 are performed before the steps 170-174 of the method 100. In an embodiment, the steps 150-154 of the method 100 are performed before the steps 180-181 of the method 100.

[0263] In an embodiment, the steps 160-163 of the method 100 are performed before the steps 120-124 of the method 100. In an embodiment, the steps 160-163 of the method 100 are performed before the steps 130-133 of the method 100. In an embodiment, the steps 160-163 of the method 100 are performed before the steps 140-141 of the method 100. In an embodiment, the steps 160-163 of the method 100 are performed before the steps 150-154 of the method 100. In an embodiment, the steps 160-163 of the method 100 are performed before the steps 170-174 of the method 100. In an embodiment, the steps 160-163 of the method 100 are performed before the steps 180-181 of the method 100.

[0264] In an embodiment, the steps 170-174 of the method 100 are performed before the steps 120-124 of the method 100. In an embodiment, the steps 170-174 of the method 100 are performed before the steps 130-133 of the method 100. In an embodiment, the steps 170-174 of the method 100 are performed before the steps 140-141 of the method 100. In an embodiment, the steps 170-174 of the method 100 are performed before the steps 150-154 of the method 100. In an embodiment, the steps 170-174 of the method 100 are performed before the steps 160-163 of the method 100. In an embodiment, the steps 170-174 of the method 100 are performed before the steps 180-181 of the method 100.

[0265] In an embodiment, the steps 180-181 of the method 100 are performed before the steps 120-124 of the method 100. In an embodiment, the steps 180-181 of the method 100 are performed before the steps 130-133 of the method 100. In an embodiment, the steps 180-181 of the method 100 are performed before the steps 140-141 of the method 100. In an embodiment, the steps 180-181 of the method 100 are performed before the steps 150-154 of the method 100. In an embodiment, the steps 180-181 of the method 100 are performed before the steps 160-163 of the method 100. In an embodiment, the steps 180-181 of the method 100 are performed before the steps 170-174 of the method 100.

[0266] In Figure 23, a flowchart depicting an embodiment of a method 2300 is provided. The method 2300 is performed by the loT server device 220. The method 2300 is for scheduling the appointment window for the communication session between the loT server device 220 and the one or more loT devices 230, 231 , 232.

[0267] The method 2300 comprises sending 2310 the booking request 240 to the first network device 200. The booking request 240 of the method 2300 corresponds to the booking request 240 of the step 110 of the method 100, as described herein.

[0268] The method 2300 comprises receiving 2311 a booking response 270 from the first network device 200. The booking response 270 of the step 2311 of the method 2300 corresponds to the booking response 270 of the step 114 of the method 100, as described herein.

[0269] In an embodiment, the method 2300 comprises receiving 2320 the booking appointment notification 1130 from the first network device 200. The booking appointment notification 1130 of the step 2320 corresponds to the booking appointment notification 1130 of the step 122 of the method 100, described herein. In an embodiment, the method 2300 comprises sending 2321 the booking appointment acknowledgment 1135 to the first network device 200. The booking appointment acknowledgment 1135 of the step 2321 corresponds to the booking appointment acknowledgment 1135 of the step 123 of the method 100, as described herein.

[0270] In an embodiment, the method 2300 comprises sending 2330 the booked action report 1210 to the first network device 200. The booked action report 1210 of the step 2330 corresponds to the booked action report 1210 of the step 130 of the method 100, as described herein.

[0271] In an embodiment, the method 2300 comprises receiving 2340 the appointment error notification 1410 from the first network device 200, if one or more conditions are not met. The appointment error notification 1410 of the step 2340 corresponds to the appointment error notification 1410 of the step 140 of the method 100, as described herein.

[0272] In an embodiment, the method 2300 comprises sending 2341 the appointment error acknowledgment 1420 to the first network device 200. The appointment error acknowledgment 1420 of the step 2341 corresponds to the appointment error acknowledgment 1420 of the step 141 of the method 100, as described herein.

[0273] In an embodiment, the method 2300 comprises sending 2350 the booking list query request 1610 to the first network device 200. The booking list query request 1610 of the step 2350 corresponds to the booking list query request 1610 of the step 150 of the method 100, as described herein.

[0274] In an embodiment, the method 2300 comprises receiving 2351 the booking list query response 1630. The booking list query response 1630 of the step 2351 corresponds to the booking list query response 1630 of the step 152 of the method 100, as described herein. In an embodiment, the method 2300 comprises sending 2360 the booking query request 1810 to the first network device 200. The booking query request 1810 of the step 2360 corresponds to the booking query request 1810 of the step 160 of the method 100, as described herein.

[0275] In an embodiment, the method 2300 comprises receiving 2361 the booking query response 1820 from the first network device. The booking query response 1820 of the step 2361 corresponds to the booking query response 1820 of the step 161 of the method 100, as described herein.

[0276] In an embodiment, the method 2300 comprises sending 2370 the booking cancellation request 2010 to the first network device 200. The booking cancellation request 2010 of the step 2370 corresponds to the booking cancellation request 2010 of the step 170 of the method 100, as described herein.

[0277] In an embodiment, the method 2300 comprises receiving 2371 the booking cancellation response 2020 from the first network device 200. The booking cancellation response 2020 of the step 2371 corresponds to the booking cancellation response 2020 from the step 172 of the method 100, as described herein.

[0278] In an embodiment, the method 2300 comprises receiving 2380, from the first network device 200, the booking removal indication 2210. The booking removal indication 2210 of the step 2380 corresponds to the booking removal indication 2210 of the step 180 of the method 100, as described herein.

[0279] In an embodiment, the method 2300 comprises sending 2381 the booking removal acknowledgment 2220 to the first network device 200. The booking removal acknowledgment 2220 of the step 2381 corresponds to the booking removal acknowledgment 2220 of the step 181 of the method 100, as described herein.

[0280] In an embodiment, the step 2310 of the method 2300 is performed before the step 2311 of the method 2300. In an embodiment, the step 2320 of the method 2300 is performed before the step 2321 of the method 2300.

[0281] In an embodiment, the step 2340 of the method 2300 is performed before the step 2341 of the method 2300.

[0282] In an embodiment, the step 2350 of the method 2300 is performed before the step 2351 of the method 2300.

[0283] In an embodiment, the step 2360 of the method 2300 is performed before the step 2361 of the method 2300.

[0284] In an embodiment, the step 2370 of the method 2300 is performed before the step 2371 of the method 2300.

[0285] In an embodiment, the step 2380 of the method 2300 is performed before the step 2381 of the method 2300.

[0286] In an embodiment, the steps 2310-2311 of the method 2300 are performed before the steps 2320-2321 of the method 2300. In an embodiment, the steps 2310-2311 of the method 2300 are performed before the step 2330 of the method 2300. In an embodiment, the steps 2310-2311 of the method 2300 are performed before the steps 2340-2341 of the method 2300. In an embodiment, the steps 2310-2311 of the method 2300 are performed before the steps 2350-2351 of the method 2300. In an embodiment, the steps 2310-2311 of the method 2300 are performed before the steps 2360-2361 of the method 2300. In an embodiment, the steps 2310-2311 of the method 2300 are performed before the steps 2370-2371 of the method 2300. In an embodiment, the steps 2310-2311 of the method 2300 are performed before the steps 2380-2381 of the method 2300.

[0287] In an embodiment, the steps 2320-2321 of the method 2300 are performed before the step 2330 of the method 2300. In an embodiment, the steps 2320-2321 of the method 2300 are performed before the steps 2340-2341 of the method 2300. In an embodiment, the steps 2320-2321 of the method 2300 are performed before the steps 2350-2351 of the method 2300. In an embodiment, the steps 2320-2321 of the method 2300 are performed before the steps 2360-2361 of the method 2300. In an embodiment, the steps 2320-2321 of the method 2300 are performed before the steps 2370-2371 of the method 2300. In an embodiment, the steps 2320-2321 of the method 2300 are performed before the steps 2380-2381 of the method 2300.

[0288] In an embodiment, the step 2330 of the method 2300 are performed before the steps 2320-2321 of the method 2300. In an embodiment, the step 2330 of the method 2300 are performed before the steps 2340-2341 of the method 2300. In an embodiment, the step 2330 of the method 2300 are performed before the steps 2350-2351 of the method 2300. In an embodiment, the step 2330 of the method 2300 are performed before the steps 2360-2361 of the method 2300. In an embodiment, the step 2330 of the method 2300 are performed before the steps 2370-2371 of the method 2300. In an embodiment, the step 2330 of the method 2300 are performed before the steps 2380-2381 of the method 2300.

[0289] In an embodiment, the steps 2340-2341 of the method 2300 are performed before the steps 2320-2321 of the method 2300. In an embodiment, the steps 2340-2341 of the method 2300 are performed before the step 2330 of the method 2300. In an embodiment, the step 2340 of the method 2300 are performed before the steps 2350- 2351 of the method 2300. In an embodiment, the step 2340 of the method 2300 are performed before the steps 2360-2361 of the method 2300. In an embodiment, the step 2340 of the method 2300 are performed before the steps 2370-2371 of the method 2300. In an embodiment, the step 2340 the method 2300 are performed before the steps 2380-2381 of the method 2300.

[0290] In an embodiment, the steps 2350-2351 of the method 2300 are performed before the steps 2320-2321 of the method 2300. In an embodiment, the steps 2350-2351 of the method 2300 are performed before the steps 2340-2341 of the method 2300. In an embodiment, the steps 2350-2351 of the method 2300 are performed before the step 2330 of the method 2300. In an embodiment, the steps 2350-2351 of the method 2300 are performed before the steps 2360-2361 of the method 2300. In an embodiment, the steps 2350-2351 of the method 2300 are performed before the steps 2370-2371 of the method 2300. In an embodiment, the steps 2350-2351 of the method 2300 are performed before the steps 2380-2381 of the method 2300.

[0291] In an embodiment, the steps 2360-2361 of the method 2300 are performed before the steps 2320-2321 of the method 2300. In an embodiment, the steps 2360-2361 of the method 2300 are performed before the step 2330 of the method 2300. In an embodiment, the steps 2360-2361 of the method 2300 are performed before the steps 2340-2341 of the method 2300. In an embodiment, the steps 2360-2361 of the method 2300 are performed before the steps 2350-2351 of the method 2300. In an embodiment, the steps 2360-2361 of the method 2300 are performed before the steps 2370-2371 of the method 2300. In an embodiment, the steps 2360-2361 of the method 2300 are performed before the steps 2380-2381 of the method 2300.

[0292] In an embodiment, the steps 2370-2371 of the method 2300 are performed before the steps 2320-2321 of the method 2300. In an embodiment, the steps 2370-2371 of the method 2300 are performed before the step 2330 of the method 2300. In an embodiment, the steps 2370-2371 of the method 2300 are performed before the steps 2340-2341 of the method 2300. In an embodiment, the steps 2370-2371 of the method 2300 are performed before the steps 2350-2351 of the method 2300. In an embodiment, the steps 2370-2371 of the method 2300 are performed before the steps 2360-2361 of the method 2300. In an embodiment, the steps 2370-2371 of the method 2300 are performed before the steps 2380-2381 of the method 2300.

[0293] In an embodiment, the steps 2380-2381 are performed of the method 2300 are performed before the steps 2320-2321 of the method 2300. In an embodiment, the steps 2380-2381 are performed of the method 2300 are performed before the step 2330 of the method 2300. In an embodiment, the steps 2380-2381 are performed of the method 2300 are performed before the steps 2340-2341 of the method 2300. In an embodiment, the steps 2380-2381 are performed of the method 2300 are performed before the steps 2350-2351 of the method 2300. In an embodiment, the steps 2380-2381 are performed of the method 2300 are performed before the steps 2360-2361 of the method 2300. In an embodiment, the steps 2380-2381 are performed of the method 2300 are performed before the steps 2370-2371 of the method 2300. In Figure 24, an illustrative example of messages exchanges between the first network device 200, the loT server device 220, the second network device 400, and the third network device 1000 according to embodiments, is provided.

[0294] The first network device 200 is configured to receive a booking request 2410. In an embodiment, the booking request 2410 corresponds to the booking request 240 of the step 110 of the method 100, as described herein. In an embodiment, the booking request 2410 corresponds to the booking request 240 of the step 2310 of the method 2300, as described herein.

[0295] The first network device 200 is configured to send an authorization booking request 2411 . In an embodiment, the authorization booking request 2411 corresponds to the authorization booking request 410 of the step 111 of the method 100, as described herein.

[0296] The first network device 200 is configured to send a booking response 2413. In an embodiment, the booking response 2413 corresponds to the booking response 270 of the step 114 of the method 100, as described herein. In an embodiment, the booking response 2413 corresponds to the booking response 270 of the step 2311 of the method 2300, as described herein.

[0297] The first network device 200 is configured to receive an authorization booking response 2412. In an embodiment, the authorization booking response 2412 corresponds to the authorization booking response 420 of the step 112 of the method 100, as described herein.

[0298] The first network device 200 is configured to receive a Monitoring Event notification 2420. In an embodiment, the Monitoring Event notification 2420 corresponds to the Monitoring Event notification 1010 of the step 120 of the method 100, as described herein.

[0299] The first network device 200 is configured to send a booking appointment notification

[0300] 2421. In an embodiment, the booking appointment notification 2421 corresponds to the booking appointment notification 1130 of the step 122 of the method 100, as described herein. In an embodiment, the booking appointment notification 2421 corresponds to the booking appointment notification 1130 of the step 2320 of the method 2300, as described herein.

[0301] The first network device 200 is configured to receive a booking appointment acknowledgment 2422. In an embodiment, the booking appointment acknowledgment 2422 corresponds to the booking appointment acknowledgment 1135 of the step 123 of the method 100, as described herein. In an embodiment, the booking appointment acknowledgment 2422 corresponds to the booking appointment acknowledgment 1135 of the step 2321 of the method 2300, as described herein.

[0302] The first network device 200 is configured to receive a booked action report 2430. In an embodiment, the booked action report 2430 corresponds to the booked action report 1210 of the step 130 of the method 100, as described herein. In an embodiment, the booked action report 2430 correspond to the booked action report 1210 of the step 2330 of the method 2300, as described herein.

[0303] The first network device 200 is configured to send an appointment error notification 2440. In an embodiment, the appointment error notification 2440 corresponds to the appointment error notification 1410 of the step 140 of the method 100, as described herein. In an embodiment, the appointment error notification 2440 corresponds to the appointment error notification 1410 of the step 2340 of the method 2300, as described herein.

[0304] The first network device 200 is configured to receive an appointment error acknowledgment 2441. In an embodiment, the appointment error acknowledgment 2441 corresponds to the appointment error acknowledgment 1420 of the step 141 of the method 100, as described herein. In an embodiment, the appointment error acknowledgment 2441 corresponds to the appointment error acknowledgment 1420 of the step 2341 of the method 2300, as described herein.

[0305] The first network device 200 is configured to receive a booking list query request 2450. In an embodiment, the booking list query request 2450 corresponds to the booking list query request 1610 of the step 150 of the method 100, as described herein. In an embodiment, the booking list query request 2450 corresponds to the booking list query request 1610 of the step 2350 of the method 2300, as described herein.

[0306] The first network device 200 is configured to send an authorization booking list query request 2451 . In an embodiment, the authorization booking list query request 2451 corresponds to the authorization booking list query request 1710 of the step 151 of the method 100, as described herein.

[0307] The first network device 200 is configured to receive an authorization booking list query response 2452. In an embodiment, the authorization booking list query response 2452 corresponds to the authorization booking list query response 1720 of the step 152 of the method 100, as described herein.

[0308] The first network device 200 is configured to send a booking list query response 2453. In an embodiment, the booking list query response 2453 correspond to the booking list query response 1630 of the step 153 of the method 100, as described herein. In an embodiment, the booking list query response 2453 correspond to the booking list query response 1630 of the step 2351 of the method 2300, as described herein.

[0309] The first network device 200 is configured to receive a booking query request 2460. In an embodiment, the booking query request 2460 correspond to the booking query request 1810 of the step 160 of the method 100, as described herein. In an embodiment, the booking query request 2460 correspond to the booking query request 1810 of the step 2360 of the method 2300, as described herein.

[0310] The first network device 200 is configured to send an authorization booking query request 2461. In an embodiment, the authorization booking query request 2461 correspond to the authorization booking query request 1910 of the step 162 of the method 100, as described herein.

[0311] The first network device 200 is configured to receive an authorization booking query response 2462. In an embodiment, the authorization booking query response 2462 corresponds to the authorization booking query response 1920 of the step 163 of the method 100, as described herein.

[0312] The first network device 200 is configured to send a booking query response 2463. In an embodiment, the booking query response 2463 corresponds to the booking query response 1820 of the step 161 of the method 100, as described herein. In an embodiment, the booking query response 2463 corresponds to the booking query response 2463 of the step 2361 of the method 2300 as described herein.

[0313] The first network device 200 is configured to receive a booking cancellation request 2470. In an embodiment, the booking cancellation request 2470 corresponds to the booking cancellation request 2010 of the step 170 of the method 100, as described herein. In an embodiment, the booking cancellation request 2470 corresponds to the booking cancellation request 2010 of the step 2370 of the method 2300, as described herein.

[0314] The first network device 200 is configured to send an authorization cancellation request 2471. In an embodiment, the authorization cancellation request 2471 corresponds to the authorization cancellation request 2110 of the step 173 of the method 100, as described herein.

[0315] The first network device 200 is configured to receive an authorization cancellation response 2472. In an embodiment, the authorization cancellation response 2472 corresponds to the authorization cancellation request 2120 of the step 174 of the method 100, as described herein.

[0316] The first network device 200 is configured to send a booking cancellation response 2473. In an embodiment, the booking cancellation response 2473 corresponds to the booking cancellation response 2020 of the step 172 of the method 100, as described herein. In an embodiment, the booking cancellation response 2473 corresponds to the booking cancellation response 2020 of the step 2371 of the method 2300, as described herein. The first network device 200 is configured to send a booking removal indication 2480. In an embodiment, the booking removal indication 2480 corresponds to the booking removal indication 2210 of the step 180 of the method 100, as described herein. In an embodiment, the booking removal indication 2480 corresponds to the booking removal 2210 of the step 2380 of the method 2300, as described herein.

[0317] The first network device 200 is configured to receive a booking removal acknowledgment 2481. In an embodiment, the booking removal acknowledgment 2481 corresponds to the booking removal acknowledgment 2220 of the step 181 of the method 100, as described herein. In an embodiment, the booking removal acknowledgment 2481 corresponds to the booking removal acknowledgment 2220 of the step 2381 of the method 2300, as described herein.

[0318] In Figure 25, a first block diagram of the first network device 200 is provided. The first network device 100 comprise a first receiving unit 2501 . The first network device 200 comprises a creating unit 2520. The first network device 200 comprises a first sending unit 2530.

[0319] The first receiving unit 2501 is configured to cause the first network device 200 to perform the step 110 of the method 100, as described herein.

[0320] The creating unit 2520 is configured to cause the first network device 200 to perform the step 113 of the method 100, as described herein.

[0321] The first sending unit 2530 is configured to cause the first network device 200 to perform the step 114 of the method 100, as described herein.

[0322] In an embodiment, the first network device 200 comprises a second sending unit 2531 . The second sending unit 2531 is configured to cause the first network device 200 to perform the step 111 of the method 100, as described herein.

[0323] In an embodiment, the first network device 200 comprises a second receiving unit 2502. The second receiving unit 2502 is configured to cause the first network device 200 to perform the step 112 of the method 100, as described herein. In an embodiment, the first network device 200 comprises a first updating unit 2541 . The first updating unit 2541 is configured to cause the first network device 200 to perform the step 115 of the method 100, as described herein.

[0324] In an embodiment, the first network device 200 comprises a second updating unit 2542. The second updating unit 2542 is configured to cause the first network device 200 to perform the step 116 of the method 100, as described herein.

[0325] In an embodiment, the first network device 200 comprises a third receiving unit 2503. the third receiving unit 2503 is configured to cause the first network device 200 to perform the step 120 of the method 100, as described herein.

[0326] In an embodiment, the first network device 200 comprises a first determining unit 2551 . The first determining unit 2551 is configured to cause the first network device 200 to perform the step 121 of the method 100, as described herein.

[0327] In an embodiment, the first network device 200 comprises a third sending unit 2532. The third sending unit 2532 is configured to cause the first network device 200 to perform the step 122 of the method 100, as described herein.

[0328] In an embodiment, the first network device 200 comprises a fourth receiving unit 2504. The fourth receiving unit 2504 is configured to cause the first network device 200 to perform the step 123 of the method 100m as described herein.

[0329] In an embodiment, the first network device 200 comprises a third updating unit 2552. The third updating unit 2552 is configured to cause the first network device 200 to perform the step 124 of the method 100, as described herein.

[0330] In an embodiment, the first network device 200 comprises a fifth receiving unit 2505. The fifth receiving unit 2505 is configured to cause the first network device 200 to perform the step 130 of the method 100, as described herein. In an embodiment, the first network device 200 comprises a fourth updating unit 2553. The fourth updating unit 2553 is configured to cause the first network device 200 to perform the step 131 of the method 100, as described herein.

[0331] In an embodiment, the first network device 200 comprises a fifth updating unit 2554. The fifth updating unit 2554 is configured to cause the first network device 200 to perform the step 132 of the method 100, as described herein.

[0332] In an embodiment, the first network device 200 comprises a sixth updating unit 2555. The sixth updating unit 2555 is configured to cause the first network device 200 to perform the step 133 of the method 100, as described herein.

[0333] In an embodiment, the first network device 200 comprises a fourth sending unit 2533. The fourth sending unit 2533 is configured to cause the first network device 200 to perform the step 140 of the method 100, as described herein.

[0334] In an embodiment, the first network device 200 comprises a sixth receiving unit 2506. The sixth receiving unit 2506 is configured to cause the first network device 200 to perform the step 141 of the method 100, as described herein.

[0335] In an embodiment, the first network device 200 comprises a seventh receiving unit 2507. The seventh receiving unit 2507 is configured to cause the first network device 200 to perform the step 150 of the method 100, as described herein.

[0336] In an embodiment, the first network device 200 comprises a second determining unit 2552. The second determining unit 2552 is configured to cause the first network device 200 to perform the step 151 of the method 100, as described herein.

[0337] In an embodiment, the first network device 200 comprises a fifth sending unit 2534. The fifth sending unit 2534 is configured to cause the first network device 200 to perform the step 152 of the method 100, as described herein. In an embodiment, the first network device 200 comprises a sixth sending unit 2535. The sixth sending unit 2535 is configured to cause the first network device 200 to perform the step 153 of the method 100, as described herein.

[0338] In an embodiment, the first network device 200 comprises an eighth receiving unit 2508. The eighth receiving unit 2508 is configured to cause the first network device 200 to perform he step 154 of the method 100, as described herein.

[0339] In an embodiment, the first network device 200 comprises a ninth receiving unit 2509. The ninth receiving unit 2509 is configured to cause the first network device 200 to perform the step 160 of the method 100, as described herein.

[0340] In an embodiment, the first network device 200 comprises a seventh sending unit 2536. The seventh sending unit 2536 is configured to cause the first network device 200 to perform the step 161 of the method 100, as described herein.

[0341] In an embodiment, the first network device 200 comprises an eighth sending unit 2537. The eighth sending unit 2537 is configured to cause the first network device 200 to perform the step 162 of the method 100, as described herein.

[0342] In an embodiment, the first network device 200 comprises a tenth receiving unit 2510. The tenth receiving unit 2510 is configured to cause the first network device 200 to perform the step 163 of the method 100, as described herein.

[0343] In an embodiment, the first network device 200 comprises an eleventh receiving unit 2511 . The eleventh receiving unit 2511 is configured to cause the first network device 200 to perform the step 170 of the method 100, as described herein.

[0344] In an embodiment, the first network device 200 comprises a deleting unit 2560. The deleting unit 2560 is configured to cause the first network device 200 to perform the step 171 of the method 200, as described herein. In an embodiment, the first network device 200 comprises a ninth sending unit 2538. The ninth sending unit 2538 is configured to cause the first network device 200 to perform the step 172 of the method 100, as described herein.

[0345] In an embodiment, the first network device 200 comprises a tenth sending unit 2539. The tenth sending unit is configured to cause the first network device 200 to perform the step 173 of the method 100, as described herein.

[0346] In an embodiment, the first network device 200 comprises a twelfth receiving unit

[0347] 2512. The twelfth receiving unit 2512 is configured to cause the first network device 200 to perform the step 174 of the method 100, as described herein.

[0348] In an embodiment, the first network device 200 comprises an eleventh sending unit 2540. The eleventh sending unit 2540 is configured to cause the first network device 200 to perform the step 180 of the method 100, as described herein.

[0349] In an embodiment, the first network device 200 comprises a thirteenth receiving unit

[0350] 2513. The thirteenth receiving unit 2513 is configured to cause the first network device 200 to perform the step 181 of the method 100, as described herein.

[0351] In an embodiment, the first receiving unit 2501 , the second receiving unit 2502, the third receiving unit 2503, the fourth receiving unit 2504, the fifth receiving unit 2505, the sixth receiving unit 2506, the seventh receiving unit 2507, the eighth receiving unit 2508, the ninth receiving unit 2509, the tenth receiving unit 2510, the eleventh receiving unit 2511 , the twelfth receiving unit 2512, and the thirteenth receiving unit 2513 are a same unit, such as receiving unit 2570.

[0352] In an embodiment, the first sending unit 2530, the second sending unit 2531 , the third sending unit 2532, the fourth sending unit 2533, the fifth sending unit 2534, the sixth sending unit 2535, the seventh sending unit 2536, the eighth sending unit 2537, the ninth sending unit 2538, the tenth sending unit 2539, and the eleventh sending unit 2540 are a same unit, such as sending unit 2572. In an embodiment, the first receiving unit 2501 , the second receiving unit 2502, the third receiving unit 2503, the fourth receiving unit 2504, the fifth receiving unit 2505, the sixth receiving unit 2506, the seventh receiving unit 2507, the eighth receiving unit 2508, the ninth receiving unit 2509, the tenth receiving unit 2510, the eleventh receiving unit 2511 , the twelfth receiving unit 2512, the thirteenth receiving unit 2513, the first sending unit 2530, the second sending unit 2531 , the third sending unit 2532, the fourth sending unit 2533, the fifth sending unit 2534, the sixth sending unit 2535, the seventh sending unit 2536, the eighth sending unit 2537, the ninth sending unit 2538, the tenth sending unit 2539, and the eleventh sending unit 2540 are a same unit, such as transceiver unit 2573.

[0353] In an embodiment, the first updating unit 2541 , the second updating unit 2542, the third updating unit 2543, the fourth updating unit 2544, the fifth updating unit 2545, and the sixth updating unit 2546 are a same unit, such as updating unit 2575.

[0354] In an embodiment, the first determining unit 2551 , and the second determining unit 2552 are a same unit 2576.

[0355] In an embodiment, the creating unit 2520, the first updating unit 2541 , the second updating unit 2542, the third updating unit 2543, the fourth updating unit 2544, the fifth updating unit 2545, the sixth updating unit 2546, the first determining unit 2551 , the second determining unit 2552, and the deleting unit 2560 are a same unit.

[0356] The first receiving unit 2501 , the second receiving unit 2502, the third receiving unit 2503, the fourth receiving unit 2504, the fifth receiving unit 2505, the sixth receiving unit 2506, the seventh receiving unit 2507, the eighth receiving unit 2508, the ninth receiving unit 2509, the tenth receiving unit 2510, the eleventh receiving unit 2511 , the twelfth receiving unit 2512, the thirteenth receiving unit 2513, the first sending unit 2530, the second sending unit 2531 , the third sending unit 2532, the fourth sending unit 2533, the fifth sending unit 2534, the sixth sending unit 2535, the seventh sending unit 2536, the eighth sending unit 2537, the ninth sending unit 2538, the tenth sending unit 2539, the eleventh sending unit 2540, the creating unit 2520, the first updating unit 2541 , the second updating unit 2542, the third updating unit 2543, the fourth updating unit 2544, the fifth updating unit 2545, the sixth updating unit 2546, the first determining unit 2551 , the second determining unit 2552, and the deleting unit 2560, illustrated in Figure 25, may be implemented as a hardware solution or as a combination of software and hardware, e.g., by one or more: a processor or a microprocessor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the steps described above with regards to the method 100.

[0357] In Figure 26, a first block diagram of the loT server device 220 is provided. The loT server device 220 comprises a first sending unit 2611 . The loT server device 200 comprises a first receiving unit 2621 .

[0358] The first sending unit 2611 is configured to cause the loT server device 220 to perform the step 2310 of the method 2300, as described herein.

[0359] The first receiving unit 2621 is configured to cause the loT server device 220 to perform the step 2311 of the method 2300, as described herein.

[0360] In an embodiment, the loT server device 220 comprises a second receiving unit 2622. The second receiving unit 2622 is configured to cause the loT server device 220 to perform the step 2320 of the method 2300, as described herein.

[0361] In an embodiment, the loT server device 220 comprises a second sending unit 2612. The second sending unit 2612 is configured to cause the loT server device 220 to perform the step 2321 of the method 2300, as described herein.

[0362] In an embodiment, the loT server device 220 comprises a third sending unit 2613. The third sending unit 2613 is configured to cause the loT server device 220 to perform the step 2330 of the method 2300, as described herein.

[0363] In an embodiment, the loT server device 220 comprises a third receiving unit 2623. The third receiving unit 2623 is configured to cause the loT server device 220 to perform the step 2340 of the method 2300, as described herein. In an embodiment, the loT server device 220 comprises a fourth sending unit 2614. The fourth sending unit 2614 is configured to cause the loT server device 220 to perform the step 2341 of the method 2300, as described herein.

[0364] In an embodiment, the loT server device 220 comprises a fifth sending unit 2615. The fifth sending unit 2615 is configured to cause the loT server device 220 to perform the step 2350 of the method 2300, as described herein.

[0365] In an embodiment, the loT server device 220 comprises a fourth receiving unit 2624. The fourth receiving unit 2624 is configured to cause the loT server device 220 to perform the step 2351 of the method 2300, as described herein.

[0366] In an embodiment, the loT server device 220 comprises a sixth sending unit 2616. The sixth sending unit 2616 is configured to cause the loT server device 220 to perform the step 2360 of the method 2300, as described herein.

[0367] In an embodiment, the loT server device 220 comprises a fifth receiving unit 2625. The fifth receiving unit 2625 is configured to cause the loT server device 220 to perform the step 2361 of the method 2300, as described herein.

[0368] In an embodiment, the loT server device 220 comprises a seventh sending unit 2617. The seventh sending unit 2617 is configured to cause the loT server device 220 to perform the step 2370 of the method 2300, as described herein.

[0369] In an embodiment, the loT server device 220 comprises a sixth receiving unit 2626. The sixth receiving unit 2626 is configured to cause the loT server device 220 to perform the step 2371 of the method 2300, as described herein.

[0370] In an embodiment, the loT server device 220 comprises a seventh receiving unit 2627. The seventh receiving unit 2627 is configured to cause the loT server device 220 to perform the step 2380 of the method 2300, as described herein. In an embodiment, the loT server device 220 comprises an eighth sending unit 2618. The eighth sending unit 2618 is configured to cause the loT server device 220 to perform the step 2381 of the method 2300, as described herein.

[0371] In an embodiment, the first sending unit 2611 , the second sending unit 2612, the third sending unit 2613, the fourth sending unit 2614, the fifth sending unit 2615, the sixth sending unit 2616, the seventh sending unit 2617, and the eighth sending unit 2618 are a same unit, such as sending unit 2631 .

[0372] In an embodiment, the first receiving unit 2621 , the second receiving unit 2622, the third receiving unit 2623, the fourth receiving unit 2624, the fifth receiving unit 2625, the sixth receiving unit 2626, and the seventh receiving unit 2627 are a same unit, such as receiving unit 2632.

[0373] In an embodiment, the first sending unit 2611 , the second sending unit 2612, the third sending unit 2613, the fourth sending unit 2614, the fifth sending unit 2615, the sixth sending unit 2616, the seventh sending unit 2617, the eighth sending unit 2618, the first receiving unit 2621 , the second receiving unit 2622, the third receiving unit 2623, the fourth receiving unit 2624, the fifth receiving unit 2625, the sixth receiving unit 2626, and the seventh receiving unit 2627 are a same unit, such as a transceiver unit 2635.

[0374] The first sending unit 2611 , the second sending unit 2612, the third sending unit 2613, the fourth sending unit 2614, the fifth sending unit 2615, the sixth sending unit 2616, the seventh sending unit 2617, the eighth sending unit 2618, the first receiving unit 2621 , the second receiving unit 2622, the third receiving unit 2623, the fourth receiving unit 2624, the fifth receiving unit 2625, the sixth receiving unit 2626, and the seventh receiving unit 2627, illustrated in Figure 26, may be implemented as a hardware solution or as a combination of software and hardware, e.g., by one or more: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the steps described above with regards to the method 2300. In Figure 27, a second block diagram of the first network device 200 is provided. The first network device 200 comprises a processor 2710, and a computer readable storage medium 2720 in the form of a memory 2725. The memory 2725 contains a computer program 2730 comprising instructions executable by the processor 2710 whereby the first network device 200 is operative to perform the steps of the method 100.

[0375] In Figure 28, a second block diagram of the loT server device 220 is provided. The loT server device 220 comprises a processor 2810, and a computer readable storage medium 2820 in the form of a memory 2825. The memory 2825 contains a computer program 2830 comprising instructions executable by the processor 2810 whereby the loT server device 200 is operative to perform the steps of the method 2300.

[0376] The (non-transitory) computer readable storage media mentioned above may be Electrically Erasable Programmable Read-Only Memory (EEPROM), a flash memory, Field Programmable Gate Array, and a hard drive.

[0377] The processor 2710 of the Figure 27, and the processor 2810 of the Figure 28, may be single Central Processing Unit (CPU), but could also comprise two or more processing units. For example, the processor 2710 of the Figure 27, and the processor 2810 of the Figure 28 may include general purpose microprocessors; instructions set processors and / or related chips sets and / or special purpose microprocessors such as Application Specific Circuits (ASICs). The processor 2710 of the Figure 27 and the processor 2810 of the Figure 28 may also comprise board memory for caching purposes.

[0378] The computer program 2730 of the Figure 27, and the computer program 2830 of the Figure 28 may be carried by a computer program product connected to the processor 2710 of the Figure 27, and the processor of the Figure 28. The computer program products may be or comprise a non-transitory computer readable storage medium on which the computer programs 2730 of the Figure 27, and the computer program 2830 of the Figure 28 are stored. For example, the computer program products may be a flash memory, a Random-Access memory (RAM), a Read-Only Memory (ROM), or an EEPROM, and the computer programs described above could in alternative embodiments be distributed on different computer program products in the form of memories.

[0379] It should be understood that although the terms “first”, “second”, etc may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, the first time instance could be termed the second time instance, and similarly, the second time instance could be termed the first time instance.

[0380] As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limited of example embodiments. As used herein, the single forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes”, and / or “including”, when used herein, specific the presence of stated features, elements, and / or components etc. but not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0381] The disclosure has been described herein in reference to embodiments thereof. It should be understood that various modifications, alternatives, and additions can be made by those skilled in the art without departing from the scope of the disclosure. Therefore, the scope of the disclosure is not limited to the above particular embodiment but only defined by the claims as attached.

Claims

CLAIMS1 . A first network device (200) in a cellular network (210) for scheduling an appointment window for a communication session between an Internet-of- Things, loT, server device (220), and one or more loT devices (230, 231 , 232), the first network device (200) being configured to:- receive a booking request (240) from the loT server device (220) for the communication session;- create a booking identifier (250) associated with the booking request (240), and an appointment window (260) based on the booking request (240), if the loT server device (220) is authorized to perform the booking request (240); and- send a booking response (270) to the loT server device (220).

2. The first network device (200) according to claim 1 , wherein the booking request (240) comprises one or more of:- an identifier (310) of the one or more loT devices (230, 231 , 232);- an identifier (320) of the loT server device;- a value corresponding to a Quality of Service, QoS, requirement (330) for the communication session;- an event type (340) of which the loT server device (220) shall be notified;- a time interval (350) indicating when the event type (340) is to be performed; and- a schedule type (360) of the appointment window (260).

3. The first network device according to claim 2, wherein the value corresponding to the QoS requirement (330) is related to one or more of:- maximum allowed packet loss rate;- minimum bit rate;- minimum bandwidth;- maximum transmission delay;- maximum allowed jitter;- maximum size of transferred data in the communication session;- session length; anda maximum value of parallel booked session per cell.

4. The first network device (200) according to any one of claims 2-3, wherein the event type (340) comprises one or more of:- a reachability of the one or more loT devices (230, 231 , 232) being a Monitoring Event ReachabilityType “SMS”, and with an Idle Status Indication; and- a reachability of the one or more loT devices (230, 231 , 232) being a Monitoring Event ReachabilityType “data”, and with an Idle Status Indication.

5. The first network device (200) according to any one of claims 2-4, wherein the time interval (350) comprises one or more of:- a single time interval specified by a starting point timestamp, and an ending point timestamp;- an interval list comprising one or more single time intervals; and- a periodic time interval.

6. The first network device (200) according to any one of claims 2-5, wherein the schedule type (360) of the appointment window (260) indicates one or more of:- an individual schedule of the one or more loT devices (230, 231 , 232); and- a distributed schedule of the one or more loT devices (230, 231 , 232).

7. The first network device (200) according to any one of claims 1 -6, configured to:- send an authorization booking request (410) to a second network device (400); and- receive an authorization booking response (420) from the second network device (400).

8. The first network device (200) according to claim 7 when claim 7 is dependent on any one of claims 2-6, wherein the authorization booking request (410) comprises one or more of:- the identifier (310) of the one or more loT devices;- the identifier (320) of the loT server device (220);- the event type (340); and- the value corresponding to the QoS requirement (330).

9. The first network device (200) according to any one of claims 7-8, wherein the authorization booking response (420) comprises:- an indication notifying that the loT server device (220) is authorized to perform the booking request (240); or- a booking error response notifying that the loT server device (220) is not authorized to perform the booking request (240).

10. The first network device (200) according to any one of claims 1-9, wherein the first network device (200) comprises one or more of:- a booking registry (510) which comprises a booking entry (610) associated with information (620) related to the booking request (240);- a booking calendar (520) which comprises a calendar entry (710, 711 , 712) for each of the one or more loT devices (230, 231 , 232) and a first list (720, 721 , 722) of one or more booking identifiers that comprises the created booking identifier (250), and wherein each booking identifier of the first list (720, 721 , 722) is associated with a list (730, 731 , 732) of booking notifications;- a QoS monitor (530) which comprises one or more QoS statistics related to the cellular network (210); and- a notification monitor (540) which comprises a notification record (810, 811 , 812) for each of the one or more loT devices (230, 231 , 232), and a list (820, 821 , 822) of one or more Monitoring Event type records, wherein each of the one or more Monitoring Event type records comprises a second list (830, 831 , 832) of one or more booking identifiers, which second list (830, 831 , 832) comprises the created booking identifier (250).11 .The first network device (200) according to claim 10, wherein create the appointment window (260) comprises creating a booking entry (610) in thebooking register (510) and / or a calendar entry (710, 711 , 712) in the booking calendar (520) for each of the one or more loT devices (230, 231 , 232).

12. The first network device (200) according to any one of claims 10-11 , wherein the information (620) related to the booking request (240) comprises one or more of:- the booking identifier (250);- the identifier (310) of the one or more loT devices (230, 231 , 232);- the identifier (320) of the loT server device (220);- the value corresponding to the QoS requirement (330) for the communication session;- the event type (340) of which the loT server device (220) shall be notified;- the time interval (350) indicating when the event type (240) is to be performed; and- the schedule type (360) of the appointment window (260).

13. The first network device (200) according to any one of claims 1 -12, wherein the booking response (270) comprises one or more of:- the booking identifier (250); and- an indication (910) that the appointment window (260) is created based on the booking request (240), or an indication (910) that the appointment window (260) is created based on an alternative time interval.

14. The first network device (200) according to any one of claims 10-13, configured to:- update the notification monitor (540); and- update the booking calendar (520).

15. The first network device (200) according to claim 14, wherein updating the notification monitor (540) comprises:- sending, to a third network device (1000), a Monitoring Event Configuration Request (1010), wherein the Monitoring Event Configuration Request (1010) comprises the identifier (310) of the one or more loT devices (230, 231 , 232), and the event type (340); and- receiving, from the third network device (1000), a Monitoring Event Configuration Response, wherein the Monitoring Event Configuration Response (1020) comprises a monitoring identifier for each of the one or more loT devices (230, 231 , 232).

16. The first network device (200) according to any one of claims 14-15, wherein updating the booking calendar (520) comprises:- adding the booking identifier (250) to the calendar entry (710, 711 , 712) for each of the one or more loT devices (230, 231 , 232).

17. The first network device (200) according to any one of claims 15-16, configured to:- receive, at a first time instance, a Monitoring Event notification (1110) related to the one or more loT devices (230, 231 , 232) from the third network device (1000), the Monitoring Event notification (1110) comprises the event type (340) to be notified of, and the identifier (310) of the one or more loT devices (230, 231 , 232);- determine one or more booking identifiers (1120) associated with the one or more loT devices (230, 231 , 232), wherein each of the time interval (350) of the determined one or more booking identifiers (1120) comprises the first time instance; and wherein each of the one or more booking identifiers (1120) is associated with the event type (340) comprised in the Monitoring Event notification (1110);- send a booking appointment notification (1130) to the loT server device (220), wherein the booking appointment notification (1130) comprises the identifier (310) of the one or more loT devices (230, 231 , 232) associated with the determined one or more booking identifiers (1120); and- receive a booking appointment acknowledgment (1135) from the loT server device (220).

18. The first network device (200) according to claim 17, configured to:update the QoS monitor (540) by adding an action-started indication in relation to the one or more loT devices (230, 231 , 232) associated with the determined one or more booking identifiers (1120).

19. The first network device (200) according to any one of claims 10-18, configured to:- receive a booked action report (1210) from the loT server device (220), wherein the booked action report (1210) comprises the identifier (310) of the one or more loT devices (230, 231 , 232), the booking identifier (250), and a success indication (1310);- update the booking calendar (520);- update the notification monitor (540); and- update the QoS monitor (530) by adding an action-finished indication in relation to the one or more loT devices (230, 231 , 232) identified in the received booked action report (1210).

20. The first network device (200) according to any one of claims 1 -19, configured to:- send an appointment error notification (1410) to the loT server device (220), if one or more conditions are not met; and- subsequently receive an appointment error acknowledgment (1420) from the loT server device (220).21 . The first network device (200) according to claim 20, wherein the appointment error notification (1410) comprises one or more of:- the booking identifier (250);- the identifier (310) of the one or more loT devices (230, 231 , 232); and- an error indication (1510).

22. The first network device (200) according to any one of claims 2-21 , configured to:- receive, at a second time instance, a booking list query request (1610) from the loT server device (220), the booking list query request (1610) comprises the identifier (320) of the loT server device (220);- determine, if the loT server device (220) is authorized, one or more booking identifiers (1620) associated with the identifier (320) of the loT server device (220), wherein each of the time interval (350) of the determined one or more booking identifiers (1620) comprise the second time instance; and wherein each of the one or more booking identifiers (1620) is associated with the identifier (320) of the loT server device (220) comprised in the booking list query request (1610);- send, if the loT server device (220) is authorized, a booking list query response (1630), wherein the booking list query response (1630) comprises the determined one or more booking identifiers (1620).

23. The first network device according to claim 22, configured to:- send an authorization booking list query request (1710) to the second network device (400); and- receive an authorization booking list query response (1720) from the second network device (400).

24. The first network device according to claim 22, wherein the authorization booking list query request (1710) comprises the identifier 320 of the loT server device 220.

25. The first network device (200) according to any one of claims 23-24, wherein the authorization booking list query response (1720) comprises:- an indication notifying that the loT server device (220) is authorized to perform the booking list query request (1610); or- a booking query list error response notifying that the loT server device (220) is not authorized to perform the booking list query request (1610).

26. The first network device (200) according to any one of claims 1 -25, configured to:- receive a booking query request (1810) from the loT server device (220), wherein the booking query request (1810) comprises the booking identifier (250); and- send, if the loT server device (220) is authorized to receive information related to the booking identifier (250), a booking query response (1820) to the loT server device (220), wherein the booking query response (1820) comprises information related to the booking identifier (250).

27. The first network device (200) according to claim 26, wherein the information related to the booking identifier (250) comprises one or more of:- the identifier (310) of the one or more loT devices (230, 231 , 232);- the identifier (320) of the loT server device (220);- the value corresponding to the QoS requirement (330) for the communication session;- the event type (340) of which the loT server device (220) shall be notified;- the time interval (350) indicating when the event type (340) is to be performed; and- the schedule type (360) of the appointment window (260).

28. The first network device (200) according to any one of claims 26-27, configured to:- send an authorization booking query request (1910) to the second network device (400); and- receive an authorization booking query response (1920) from the second network device (400).

29. The first network device (200) according to claim 28, wherein the authorization booking query request (1910) comprises one or more of:- the booking identifier (250); and- the identifier (320) of the loT server device (220).

30. The first network device (200) according to to any one of claims 28-29 wherein the authorization booking query response (1920) comprises:- an indication notifying that the loT server device (220) is authorized to perform the booking query request (1810); or- a booking query error response notifying that the loT server device (220) is not authorized to perform the booking query request (1810).31 .The first network device (200) according to any one of claims 10-30, configured to:- receive a booking cancellation request (2010) from the loT server device (220), wherein the booking cancellation request (2010) comprises the booking identifier (250);- delete the booking entry (610) associated with the booking identifier (250), if the loT server device (220) is authorized to request the booking cancellation request (2010); and- send a booking cancellation response (2020) to the loT server device (220), if the loT server device (220) is authorized to request the booking cancellation request (2010).

32. The first network device (200) according to any one of claims 31-32, configured to:- send an authorization booking cancellation request (2110) to the second network device (400); and- receive an authorization booking cancellation response (2120) from the second network device (400).

33. The first network device (200) according to claim 33, wherein the authorization booking cancellation request (2110) comprises one or more of:- the booking identifier (250); and- the identifier (320) of the loT server device (220).

34. The first network device (200) according to any one of claims 33-34 wherein the authorization booking cancellation response (2120) comprises:- an indication notifying that the loT server device (220) is authorized to perform the booking cancellation request (2010); ora booking cancellation error response notifying that the loT server device (220) is not authorized to perform the booking cancellation request (2010).

35. The first network device (200) according to any one of claims 1 -34, configured to:- send, to the loT server device (220), a booking removal indication (2210), wherein the booking removal indication (2210) comprises the booking identifier (250), and a cause indication for a removal of a booking request associated with the booking identifier (250); and- receive a booking removal acknowledgement (2220) from the loT server device (220).

36. The first network device (200) according to any one of claims 1 -35, wherein the booking identifier (250) is a uniform resource identifier.

37. The first network device (200) according to any one of claims 7-36, wherein the second network device (400) comprises at least one of:- a Home Subscriber Server, HSS, associated with the one or more loT devices (230, 231 , 232); and- a unified Data Management, UDM, associated with the one or more loT devices (230, 231 , 232).

38. The first network device (200) according to any one of claims 15-37, wherein the third network device (1000) is a Service Capability Exposure Function, SCEF, device.

39. An Internet of Things, loT, server device (220), for scheduling an appointment window for a communication session between the loT server device (220), and one or more loT devices (230, 231 , 232), configured to:- send a booking request (240) to a first network device (200); and- receive a booking response (270) from the first network device (200).

40. The loT server device (220) according to claim 39, wherein the booking request (240) comprises one or more of:- an identifier (310) of the one or more loT devices (230, 231 , 232);- an identifier (320) of the loT server device (220);- a value corresponding to a Quality of Service, QoS, requirement (330) for the communication session;- an event type (340) of which the loT server device (220) shall be notified;- a time interval (350) indicating when the event type (340) is to be performed; and- a schedule type (360) of the appointment window (260).41 .The loT server device (220) according to claim 40, wherein the value corresponding to the QoS requirement (330) relates to one or more of:- maximum allowed packet loss rate;- minimum bit rate;- minimum bandwidth;- maximum transmission delay;- maximum allowed jitter;- maximum size of transferred data in the communication session;- session length; and- a maximum value of parallel booked session per cell.

42. The loT server device (220) according to any one of claims 40-41 , wherein the event type (340) comprises one or more of:- a reachability of the one or more loT devices (230, 231 , 232) being a Monitoring Event ReachabilityType “SMS”, and with an Idle Status Indication; and- a reachability of the one or more loT devices (230, 231 , 232) being a Monitoring Event ReachabilityType “data”, and with an Idle Status Indication.

43. The loT server device (220) according to any one of claims 40-42, wherein the time interval (350) comprises one or more of:- a single time interval specified by a starting point timestamp, and an ending point timestamp;- an interval list comprising one or more single time intervals; anda periodic time interval.

44. The loT server device (220) according to any one of claims 40-43, wherein the schedule type (360) of the appointment window (260) indicates one or more of:- an individual schedule of the one or more loT devices (230, 231 , 232); and- a distributed schedule of the one or more loT devices (230, 231 , 232).

45. The loT server device (220) according to any one of claims 39-44, wherein the booking response (270) comprises one or more of:- the booking identifier (250); and- an indication (910) that the appointment window (260) is created according to the booking request (240), or an indication (910) that the appointment window (260) is created according to an alternative time.

46. The loT server device (220) according to any one of claims 39-45, configured to:- receive a booking appointment notification (1130) from the first network device (200), wherein the booking appointment notification (1130) comprises the identifier (310) of the one or more loT devices (230, 231 , 232), wherein the one or more loT devices (230, 231 , 232) are ready to be booked; and- send a booking appointment acknowledgment (1135) to the first network device (200).

47. The loT server device (220) according to any one of claims 39-46, configured to:- send a booked action report (1210) to the first network device (200), wherein the booked action report (1210) comprises the identifier (310) of the one or more loT devices (230, 231 , 232), the booking identifier (250), and a success indication (1310).

48. The loT server device (220) according to any one of claims 39-47, configured to:- receive an appointment error notification (1410) from the first network device (200), if one or more conditions are not met; and- subsequently send an appointment error acknowledgement (1420) to the first network device (200).

49. The loT server device (220) according to claim 48, wherein the appointment error notification (1410) comprises one or more of:- the booking identifier (250);- the identifier (310) of the one or more loT device (230, 231 , 232); and- an error indication (1510).

50. The loT server device (220) according to any one of claims 39-49, configured to:- send, at a second time instance, a booking list query request (1610) to the first network device (200), the booking list query request (1610) comprises the identifier (320) of the loT server device (220); and- receive a booking list query response (1630), wherein the booking list query response (1630) comprises one or more booking identifiers (1620) associated to the identifier (320) of the loT server device (220).51 .The loT server device (220) according to any one of claims 39-50, configured to:- send a booking query request (1810) to the first network device (200), wherein the booking query request (1810) comprises the booking identifier (250); and- receive, if the loT server device (220) is authorized to receive information related to the booking identifier (250), a booking query response (1820) from the first network device (200), wherein the booking query response (1820) comprises the information related to the booking identifier (250).

52. The loT server device (220) according to claim 51 , wherein the information related to the booking identifier (250) comprises one or more of:- the identifier (310) of the one or more loT devices (230, 231 , 232);- the identifier (320) of the loT server device (220);- the value corresponding to the QoS requirement (330) for the communication session;- the event type (340) of which the loT server device (220) wants to be notified;- the time interval (250) indicating when the event type (340) is to be performed; and- the schedule type (360) of the appointment window (260).

53. The loT server device (220) according to any one of claims 39-52, is configured to:- send a booking cancellation request (2010) to the first network device (200), wherein the booking cancellation request (2010) comprises the booking identifier (250); and- receive a booking cancellation response (2020) from the first network device (200), if the loT server device (220) is authorized to request the booking cancellation request (2010).

54. The loT server device (220) according to any one of claims 39-53, configured to:- receive, from the first network device (200), a booking removal indication (2210), wherein the booking removal indication (2210) comprises the booking identifier (250), and a cause indication for a removal of a booking request associated with the booking identifier (250); and- send a booking removal acknowledgment (2220) to the first network device (200).

55. The loT server device (220) according to any one of claims 39-54, wherein the booking identifier (250) is a uniform resource identifier.

56. A method (100) performed by a first network device (200) in a cellular network (210), for scheduling an appointment window for a communication session between an Internet-of-Things, loT, server device (220), and one or more loT devices (230, 231 , 232), the method (100) comprising:- receiving (110) a booking request (240) from the loT server device (220);- creating (113) a booking identifier (250) associated with the booking request (240), and an appointment window (260) based on the booking request (240), if the loT server device (220) is authorized to perform the booking request (240); and- sending (114) a booking response (270) to the loT server device (220).

57. The method (100) according to claim 56, wherein the booking request (240) comprises one or more of:- an identifier (310) of the one or more loT devices (230, 231 , 232);- an identifier (320) of the loT server device;- a value corresponding to a Quality of Service, QoS, requirement (330) for the communication session;- an event type (340) of which the loT server device (220) shall be notified;- a time interval (350) indicating when the event type (340) is to be performed; and / or- a schedule type (360) of the appointment window (260).

58. The method (100) according to claim 57, wherein the value corresponding to the QoS requirement (330) is related to one or more of:- maximum allowed packet loss rate;- minimum bit rate;- minimum bandwidth;- maximum transmission delay;- maximum allowed jitter;- maximum size of transferred data in the communication session;- session length; and- a maximum value of parallel booked session per cell.

59. The method (100) according to any one of claims 57-58, wherein the event type (340) comprises one or more of:- a reachability of the one or more loT devices (230, 231 , 232) being a Monitoring Event ReachabilityType “SMS”, and with an Idle Status Indication; anda reachability of the one or more loT devices (230, 231 , 232) being a Monitoring Event ReachabilityType “data”, and with an Idle Status Indication.

60. The method (100) according to any one of claims 57-59, wherein the time interval (350) comprises one or more of:- a single time interval specified by a starting point timestamp, and an ending point timestamp;- an interval list comprising one or more single time intervals; and- a periodic time interval.

61. The method (100) according to any one of claims 57-60, wherein the schedule type (360) of the appointment window (260) indicates one or more of:- an individual schedule of the one or more loT devices (230, 231 , 232); and- a distributed schedule of the one or more loT devices (230, 231 , 232).

62. The method (100) according to any one of claims 56-61 , the method (100) comprising:- sending (111 ) an authorization booking request (410) to a second network device (400); and- receiving (112) an authorization booking response (420) from the second network device (400).

63. The method (100) according to claim 62, wherein the authorization booking request (410) comprises one or more of:- the identifier (310) of the one or more loT devices;- the identifier (320) of the loT server device (220);- the event type (340); and- the value corresponding to the QoS requirement (330).

64. The method (100) according to any one of claims 62-63, wherein the authorization booking response (420) comprises:- an indication notifying that the loT server device (220) is authorized to perform the booking request (240); ora booking error response notifying that the loT server device (220) is not authorized to perform the booking request (240).

65. The method (100) according to any one of claims 56-64, wherein the first network device (200) comprises one or more of:- a booking registry (510), which comprises a booking entry (610) associated with information (620) related to the booking request (240);- a booking calendar (520), which comprises a calendar entry (710, 711 , 712) for each of the one or more loT devices (230, 231 , 232), and a first list (720, 721 , 722) of one or more booking identifiers, which first list (720, 721 , 722) comprises the created booking identifier (250), wherein each booking identifier of the first list (720, 721 , 722) is associated with a list (730, 731 , 732) of booking notifications;- a QoS monitor (530), which comprises one or more QoS statistics related to the cellular network (210); and- a notification monitor (540), which comprises a notification record (810, 811 , 812) for each of the one or more loT devices (230, 231 , 232), and a list (820, 821 , 822) of one or more Monitoring Event type records, wherein each of the one or more Monitoring Event type records comprises a second list (830, 831 , 832) of one or more booking identifiers, which second list (830, 831 , 832) comprises the created booking identifier (250).

66. The method (100) according to claim 65, wherein creating (113) the appointment window (260) comprises creating a booking entry (610) in the booking register (510) and / or a calendar entry (710, 711 , 712) in the booking calendar (520) for each of the one or more loT devices (230, 231 , 232).

67. The method (100) according to any one of claims 65-66, wherein the information (620) related to the booking request (240) comprises one or more of:- the booking identifier (250);- the identifier (310) of the one or more loT devices (230, 231 , 232);- the identifier (320) of the loT server device (220);- the value corresponding to the QoS requirement (330) for the communication session;- the event type (340) of which the loT server device (220) shall be notified;- the time interval (350) indicating when the event type (240) is to be performed; and- the schedule type (360) of the appointment window (260).

68. The method (100) according to any one of claims 56-67, wherein the booking response (270) comprises one or more of:- the booking identifier (250); and- an indication (910) that the appointment window (260) is created based on the booking request (240), or an indication (910) that the appointment window (260) is created based on an alternative time interval.

69. The method (100) according to any one of claims 65-68, the method (100) comprising:- updating (115) the notification monitor (540); and- updating (116) the booking calendar (520).

70. The method (100) according to claim 69, wherein updating (115) the notification monitor (540) comprises:- sending, to a third network device (1000), a Monitoring Event Configuration Request (1010), wherein the Monitoring Event Configuration Request (1010) comprises the identifier (310) of the one or more loT devices (230, 231 , 232), and the event type (340); and- receiving, from the third network device (1000), a Monitoring Event Configuration Response, wherein the Monitoring Event Configuration Response (1020) comprises a monitoring identifier for each of the one or more loT devices (230, 231 , 232).

71. The method (100) according to any one of claims 69-70, wherein updating (116) the booking calendar (520) comprises:- adding the booking identifier (250) to the calendar entry (710, 711 , 712) for each of the one or more loT devices (230, 231 , 232).

72. The method (100) according to any one of claims 65-71 , the method (100) comprising:- receiving (120), at a first time instance, a Monitoring Event notification (1110) related to the one or more loT devices (230, 231 , 232) from the third network device (1000), the Monitoring Event notification (1110) comprises the event type (340) to be notified of, and the identifier (310) of the one or more loT devices (230, 231 , 232);- determining (121 ) one or more booking identifiers (1120) associated with the one or more loT devices (230, 231 , 232), wherein each of the time interval (350) of the determined one or more booking identifiers (1120) comprises the first time instance; and wherein each of the one or more booking identifiers (1120) is associated with the event type (340) comprised in the Monitoring Event notification (1110);- sending (122) a booking appointment notification (1130) to the loT server device (220), wherein the booking appointment notification (1130) comprises the identifier (310) of the one or more loT devices (230, 231 , 232) associated with the determined one or more booking identifiers (1120); and- receiving (123) a booking appointment acknowledgment (1135) from the loT server device (220).

73. The method (100) according to claim 72, the method (100) comprising:- updating (124) the QoS monitor (540) by adding an action-started indication in relation to the one or more loT devices (230, 231 , 232) associated with the determined one or more booking identifiers (1120).

74. The method (100) according to any one of claims 65-73, the method (100) comprising:- receiving (130) a booked action report (1210) from the loT server device (220), wherein the booked action report (1210) comprises the identifier(310) of the one or more loT devices (230, 231 , 232), the booking identifier (250), and a success indication (1310);- updating (131 ) the booking calendar (520);- updating (132) the notification monitor (540); and- updating (133) the QoS monitor (530) by adding an action-finished indication in relation to the one or more loT devices (230, 231 , 232) identified in the received booked action report (1210).

75. The method (100) according to any one of claims 56-74, the method (100) comprising:- sending (140) an appointment error notification (1410) to the loT server device (220), if one or more conditions are not met; and- subsequently receiving (141 ) an appointment error acknowledgment (1420) from the loT server device (220).

76. The method (100) according to claim 75, wherein the appointment error notification (1410) comprises one or more of:- the booking identifier (250);- the identifier (310) of the one or more loT devices (230, 231 , 232); and- an error indication (1510).

77. The method (100) according to any one of claims 57-76, method (100) comprising:- receiving (150), at a second time instance, a booking list query request (1610) from the loT server device (220), the booking list query request (1610) comprises the identifier (320) of the loT server device (220); and- determining (151 ), if the loT server device (220) is authorized, one or more booking identifiers (1620) associated with the identifier (320) of the loT server device (220), wherein each of the time interval (350) of the determined one or more booking identifiers (1620) comprise the second time instance; andwherein each of the one or more booking identifiers (1620) is associated with the identifier (320) of the loT server device (220) comprised in the booking list query request (1610);- sending (152), if the loT server device (220) is authorized, a booking list query response (1630), wherein the booking list query response (1630) comprises the determined one or more booking identifiers (1620).

78. The method (100) according to claim 77, the method (100) comprising:- sending (153) an authorization booking list query request (1710) to the second network device (400); and- receiving (154) an authorization booking list query response (1720) from the second network device (400).

79. The method (100) according to claim 78, wherein the authorization booking list query request (1710) comprises the identifier (320) of the loT server device (220).

80. The method (100) according to any one of claims 78-79, wherein the authorization booking list query response (1720) comprises:- an indication notifying that the loT server device (220) is authorized to perform the booking list query request (1610); or- a booking query list error response notifying that the loT server device (220) is not authorized to perform the booking list query request (1610).

81. The method (100) according to any one of claims 56-80, the method (100) comprising:- receiving (160) a booking query request (1810) from the loT server device (220), wherein the booking query request (1810) comprises the booking identifier (250); and- sending (161 ), if the loT server device (220) is authorized to receive information related to the booking identifier (250), a booking query response (1820) to the loT server device (220), wherein the booking query response (1820) comprises information related to the booking identifier (250).

82. The method (100) according to claim 81 , wherein the information related to the booking identifier (250) comprises one or more of:- the identifier (310) of the one or more loT devices (230, 231 , 232);- the identifier (320) of the loT server device (220);- the value corresponding to the QoS requirement (330) for the communication session;- the event type (340) of which the loT server device (220) shall be notified;- the time interval (350) indicating when the event type (340) is to be performed; and- the schedule type (360) of the appointment window (260).

83. The method (100) according to any one of claims 81-82, the method (100) comprising:- sending (162) an authorization booking query request (1910) to the second network device (400); and- receiving (163) an authorization booking query response (1920) from the second network device (400).

84. The method (100) according to claim 83, wherein the authorization booking query request (1910) comprises one or more of:- the booking identifier (250); and- the identifier (320) of the loT server device (220);85. The method (100) according to any one of claims 83-84 wherein the authorization booking query response (1920) comprises:- an indication notifying that the loT server device (220) is authorized to perform the booking query request (1810); or- a booking query error response notifying that the loT server device (220) is not authorized to perform the booking query request (1810).

86. The method (100) according to any one of claims 65-85, the method (100) comprising:- receiving (170) a booking cancellation request (2010) from the loT server device (220), wherein the booking cancellation request (2010) comprises the booking identifier (250);- deleting (171 ) the booking entry (610) associated with the booking identifier (250), if the loT server device (220) is authorized to request the booking cancellation request (2010); and- sending (172) a booking cancellation response (2020) to the loT server device (220), if the loT server device (220) is authorized to request the booking cancellation request (2010).

87. The method (100) according to any one of claims 62-86, the method (100) comprising:- sending (173) an authorization booking cancellation request (2110) to the second network device (400); and- receiving (174) an authorization booking cancellation response (2120) from the second network device (400).

88. The method (100) according to claim 87, wherein the authorization booking cancellation request (2110) comprises one or more of:- the booking identifier (250); and- the identifier (320) of the loT server device (220).

89. The method (100) according to any one of claims 87-88 wherein the authorization booking cancellation response (2120) comprises:- an indication notifying that the loT server device (220) is authorized to perform the booking cancellation request (2010); or- a booking cancellation error response notifying that the loT server device (220) is not authorized to perform the booking cancellation request (2010).

90. The method (100) according to any one of claims 56-89, the method (100) comprising:- sending (180), to the loT server device (220), a booking removal indication (2210), wherein the booking removal indication (2210) comprises thebooking identifier (250), and a cause indication for a removal of a booking request associated with the booking identifier (250); and- receiving (181 ) a booking removal acknowledgement (2220) from the loT server device (220).

91. The method (100) according to any one of claims 56-90, wherein the booking identifier (250) is a uniform resource identifier.

92. The method (100) according to any one of claims 62-91 , wherein the second network device (400) comprises at least one of:- a Home Subscriber Server, HSS, associated with the one or more loT devices (230, 231 , 232); and- a unified Data Management, UDM, associated with the one or more loT devices (230, 231 , 232).

93. The method (100) according to any one of claims 70-92, wherein the third network device (1000) is a Service Capability Exposure Function, SCEF, device.

94. A method (2300) performed by an Internet of Things, loT, server device (220), for scheduling an appointment window for a communication session between the loT server device (220), and one or more loT devices (230, 231 , 232), the method (2300) comprising:- sending (2310) a booking request (240) to a first network device (200); and- receiving (2311 ) a booking response (270) from the first network device (200).

95. The method (2300) according to claim 94, wherein the booking request (240) comprises one or more of:- an identifier (310) of the one or more loT devices (230, 231 , 232);- an identifier (320) of the loT server device (220);- a value corresponding to a Quality of Service, QoS, requirement (330) for the communication session;- an event type (340) of which the loT server device (220) shall be notified;- a time interval (350) indicating when the event type (340) is to be performed; and- a schedule type (360) of the appointment window (260).

96. The method (2300) according to claim 95, wherein the value corresponding to the QoS requirement (330) is related to one or more of:- maximum allowed packet loss rate;- minimum bit rate;- minimum bandwidth;- maximum transmission delay- maximum allowed jitter;- maximum size of transferred data in the communication session;- session length; and- a maximum value of parallel booked session per cell.

97. The method (2300) according to any one of claims 95-96, wherein the event type (340) comprises one or more of:- a reachability of the one or more loT devices (230, 231 , 232) being a Monitoring Event ReachabilityType “SMS”, and with an Idle Status Indication; and- a reachability of the one or more loT devices (230, 231 , 232) being a Monitoring Event ReachabilityType “data”, and with an Idle Status Indication.

98. The method (2300) according to any one of claims 95-97, wherein the time interval (350) comprises one or more of:- a single time interval specified by a starting point timestamp, and an ending point timestamp;- an interval list comprising one or more single time intervals; and- a periodic time interval.

99. The method (2300) according to any one of claims 95-98, wherein the schedule type (360) of the appointment window (260) indicates one or more of:- an individual schedule of the one or more loT devices (230, 231 , 232); and- a distributed schedule of the one or more loT devices (230, 231 , 232).

100. The method (2300) according to any one of claims 94-99, wherein the booking response (270) comprises one or more of:- the booking identifier (250); and- an indication (910) that the appointment window (260) is created according to the booking request (240), or an indication (910) that the appointment window (260) is created according to an alternative time.101 . The method (2300) according to any one of claims 94-100, the method (2300) comprising:- receiving (2320) a booking appointment notification (1130) from the first network device (200), wherein the booking appointment notification (1130) comprises the identifier (310) of the one or more loT devices (230, 231 , 232), wherein the one or more loT devices (230, 231 , 232) are ready to be booked; and- sending (2321 ) a booking appointment acknowledgment (1135) to the first network device (200).

102. The method (2300) according to any one of claims 94-101 , the method (2300) comprising:- sending (2330) a booked action report (1210) to the first network device (200), wherein the booked action report (1210) comprises the identifier (310) of the one or more loT devices (230, 231 , 232), the booking identifier (250), and a success indication (1310).

103. The method (2300) according to any one of claims 94-102, the method (2300) comprising:- receiving (2340) an appointment error notification (1410) from the first network device (200), if one or more conditions are not met; andsubsequently sending (2341 ) an appointment error acknowledgement (1420) to the first network device (200).

104. The method (2300) according to claim 103, wherein the appointment error notification (1410) comprises one or more of:- the booking identifier (250);- the identifier (310) of the one or more loT device (230, 231 , 232); and- an error indication (1510).

105. The method (2300) according to any one of claims 94-104, the method (2300) comprising:- sending (2350), at a second time instance, a booking list query request (1610) to the first network device (200), the booking list query request (1610) comprises the identifier (320) of the loT server device (220); and- receiving (2351 ) a booking list query response (1630), wherein the booking list query response (1630) comprises one or more booking identifiers (1620) associated to the identifier (320) of the loT server device (220).

106. The method (2300) according to any one of claims 94-105, the method (2300) comprising:- sending (2360) a booking query request (1810) to the first network device (200), wherein the booking query request (1810) comprises the booking identifier (250); and- receiving (2361 ), if the loT server device (220) is authorized to receive information related to the booking identifier (250), a booking query response (1820) from the first network device (200), wherein the booking query response (1820) comprises the information related to the booking identifier (250).

107. The method (2300) according to claim 106, wherein the information related to the booking identifier (250) comprises one or more of:- the identifier (310) of the one or more loT devices (230, 231 , 232);- the identifier (320) of the loT server device (220);- the value corresponding to the QoS requirement (330) for the communication session;- the event type (340) of which the loT server device (220) shall be notified;- the time interval (250) indicating when the event type (340) is to be performed; and- the schedule type (360) of the appointment window (260).

108. The method (2300) according to any one of claims 94-107, the method (2300) comprising:- sending (2370) a booking cancellation request (2010) to the first network device (200), wherein the booking cancellation request (2010) comprises the booking identifier (250); and- receiving (2371 ) a booking cancellation response (2020) from the first network device (200), if the loT server device (220) is authorized to request the booking cancellation request (2010).

109. The method (2300) according to any one of claims 94-108, the method (2300) comprising:- receiving (2380), from the first network device (200), a booking removal indication (2210), wherein the booking removal indication (2210) comprises the booking identifier (250), and a cause indication for a removal of a booking request associated with the booking identifier (250); and- sending (2381 ) a booking removal acknowledgment (2220) to the first network device (200).

110. The method (2300) according to any one of claims 94-109, wherein the booking identifier (250) is a uniform resource identifier.

111. A computer program (2730) comprising instructions, which when executed on a first network device (200), causes the first network device (200) to perform the method (100) according to any one of claims 56-93.

112. A computer program (2830) comprising instructions, which when executed on a loT server device (220), causes the loT server device (220) to perform the method (2300) according to any one of claims 94-110.

113. A computer readable storage medium (2720, 2820) comprising a computer program (2730, 2830) according to claim 111 , and / or claim 112.

Images