Patent Description:
When setting up or designing an internet-of-things system that comprises at least a plurality of internet-of-things communication devices in a (typically existing) communication network providing radio coverage in a predetermined geographical area, a huge choice of different implementation possibilities typically exists. This is due to the possibility to use, in order to actually set up the internet-of-things system, many hundreds if not many thousands of different possible hardware alternatives regarding, typically, each and every sub-system, or modular functional block or component of the internet-of-things communication devices - such as, e.g., the types of sensors, actuators, microcontroller units, chipsets, wireless communication modules, battery units or configurations thereof, and power units. This huge choice, typically at the level of each one of these hardware components, creates an even increased number of different possibilities or different combinations how to implement such an internet-of-things system, and, hence, the need to invest substantially in the design process and the process to define a configuration of the internet-of-things communication devices that is viable in practice, i.e., in a real-life environment. Additionally, the business viability and performance of constrained, battery-powered internet-of-things communication devices are often not in the control of end-customers, service providers, or manufacturers: Often, products (i.e., internet-of-things communication devices) are designed and deployed with specific use cases in mind, which turn out not to reflect the reality that devices are ultimately exposed to. Multiple factors might impact the battery life of such devices -for instance, aspects related to the telecommunication networks on which (or within which) the devices operate, environmental effects where the devices are either statically deployed or moved into, as well as factors controlling if and how often the application communicates. Hence, there is the need to provide solutions such that the behavior of the internet-of-things communication devices is able to be adapted in a manner such as to realize or to exceed the intended battery lifetime. International Application <CIT> relates to resource optimization executed by a network node in an Internet-of-Things (loT) system utilizing event prediction to optimize system performance and Quality of Experience (QoE). European Patent Application <CIT> relates to provisioning and managing Internet-of-Things devices over a network using device based tunneled nodes and device profiles for IoT devices,.

An object of the present invention is to provide a method for efficiently operating an internet-of-things system using an internet-of-things performance management system, the internet-of-things system comprises a plurality of internet-of-things communication devices in a communication network and the internet-of-things system providing an internet-of-things service, wherein each of the internet-of-things communication devices comprises a performance management client functionality and operates according to configuration information of a respective performance vector dataset that is specifically adapted to the very internet-of-things communication device, respectively, and its respective environment or situation and/or is iteratively adapted or able to be iteratively adapted. Additionally, objects of the present invention relate to a system for operating an internet-of-things system, to an internet-of-things performance management system, and/or to an internet-of-things communication device as part of the internet-of-things system, to a program comprising a computer readable program code, and to a computer-readable medium comprising instructions which when executed help to perform an inventive method.

The object of the present invention is achieved by a method for operating an internet-of-things system using an internet-of-things performance management system according to independent claim <NUM>.

Each of the internet-of-things communication devices is configured in some manner, i.e., acts according to a configuration, or, in other words, comprises configuration information. According to the present invention, each one of the internet-of-things communication devices comprises a performance management client functionality and operates according to configuration information of (or received by means of) a respective performance vector dataset, wherein the performance vector dataset is adapted and/or iteratively adapted (and/or able to be iteratively adapted) to the (specifically considered) internet-of-things communication device, respectively, and its respective environment or situation.

This is able to be realized, according to the present invention, by means of the specific (i.e., considered) internet-of-things communication device receiving at least one downlink performance vector dataset, and by means of transmitting, by the specific internet-of-things communication device, at least one uplink performance vector dataset towards the internet-of-things performance management system. Especially, this is realized by means of a first downlink performance vector dataset being transmitted, triggered by the internet-of-things performance management system, towards the specific internet-of-things communication device, and a first uplink performance vector dataset being transmitted, by the specific internet-of-things communication device, towards the internet-of-things performance management system.

Multiple factors might impact the battery life of such devices -for instance, aspects related to the telecommunication networks on which (or within which) the devices operate, environmental effects where the devices are either statically deployed or moved into, as well as factors controlling if and how often the application communicates. The following factors typically influence the internet-of-things communication device's performance, especially regarding the battery life:.

To counteract these risks, it is conventionally known to perform reactive and human-triggered policy changes that are able to be pushed to the considered devices via device management protocols. Furthermore, it is conventionally known to use a trained artificial intelligence or machine learning middleware that is running on constrained devices and that might identify patterns, albeit only based on locally recorded data. Both of these technologies are limited by the fact that such algorithms are a reactive, a learned response to specific local changes, and usually ignorant of wider trends happening to similar applications, similar use cases, in similar deployment environments, globally.

Hence, there is no proactive management of the devices themselves to control, (reconfigure, or steer them based on population-wide performance trends or predictive modeling based on population-wide references. There is additionally no feedback loop of field data to the devices.

Especially, the device performance management relies on, on the one hand, the performance management client functionality as part of each one of the considered internet-of-things communication devices of the internet-of-things system, and, on the other hand, minimally a performance management service, hereinafter also called PMS, executing on a service provider's internet-of-things platform, application server, edge computing node (ECN), or other.

The device performance management client (functionality), hereinafter also called PMC, executes on each constrained internet-of-things (communication) device managed by the performance management service, typically either on its microcontroller, 3GPP™ wireless communication module, or 3GPP™ communication chipset. According to the present invention, the internet-of-things performance management system (or platform) or the performance management service especially comprises:.

Especially, the PMS uses the information received from the IOA to generate device-specific "Performance Vector Datasets" (PVD), which are sent to the PMC on the Downlink (loT Platform/AS/ECN/other towards the device).

The PMC is able to use the device-specific KPIs and instruction sets received in Downlink PVD files to optimize the device's battery consumption performance. This is done by reconfiguring multiple hardware and application properties of the device (e.g. reconfigure the 3GPP™ wireless communication module or chipset, reconfigure the GNSS chip, reconfigure the cadence of communication, reconfigure the content of the communication, reconfigure the communication protocol(s) used, reconfigure the smart antenna tuning circuit, reconfigure the smart battery front-end circuitry, etc.).

According to the present invention, the PMC periodically inspects the hardware and application properties (of the internet-of-things communication device) for the purpose of generating and sending a PVD update back to the PMS on the Uplink (device towards loT Platform/AS/ECN/other).

Regarding the transmission of these PVD files:.

Upon receiving each Uplink PVD update, the PMS is able to consult the IOA, together with updates sourced from the EDS, and the IOA begins a new optimization analysis using IPPL data. The UDP in the IDPL is updated, if applicable. The PMS generates a Downlink PVD update and sends it back to the PMC.

This cycle of Downlink optimization recommendation, Uplink performance feedback, Downlink optimization recommendation, Uplink performance feedback, etc., will continue until the service is discontinued, either by the decommissioning of the device, or the setting of the PVD timer to "<NUM>". The service can be reactivated by sending an initial PVD update to the device on the downlink.

According to the present invention, it is furthermore advantageously possible and preferred that in determining the different configuration information of the second downlink performance vector dataset, the internet-of-things performance management system, an intelligent optimizer algorithm and/or a performance management service thereof, especially takes into account the performance feedback information of the first uplink performance vector dataset.

Thus, by means of providing the specific internet-of-things communication device with modified or different configuration information - transmitted by means of the second downlink performance vector dataset -, it is advantageously possible according to the present invention to arrange for a more optimized configuration of the specific internet-of-things communication device, and, hence, to a more optimized operation of this device, especially one having an improved battery behavior or an increased battery life time.

According to the present invention, it is furthermore advantageously possible and preferred that the different configuration information (of the second downlink performance vector dataset or of a subsequent downlink performance vector dataset), especially compared to the first downlink performance vector dataset, is obtained by means of the internet-of-things performance management system, especially its performance management service, using at least one of the following:.

Thereby, it is advantageously possible according to the present invention to be able to determine the second downlink performance vector dataset such that it corresponds to an improvement compared to the first downlink performance vector dataset (i.e. results in an improved operation of the specific (considered) internet-of-things communication device.

According to the present invention, it is furthermore advantageously possible and preferred that in determining - by the internet-of-things performance management system, and especially the intelligent optimizer algorithm thereof - the configuration information of the second downlink performance vector dataset at least one of the following data sources is or are taken into consideration, in addition to taking into consideration the performance feedback information of the first uplink performance vector dataset:.

Hence, according to the present invention, it is advantageously possible to rely on a broad range of data sources in order to be able to optimize the internet-of-things communication device's behavior.

According to the present invention, it is furthermore advantageously possible and preferred that, regarding the specific internet-of-things communication device, the first and/or subsequent downlink performance vector dataset is or corresponds to a unique device profile, especially stored in the internet-of-things device profile library, and/or wherein, likewise regarding the specific internet-of-things communication device, the first and/or subsequent uplink performance vector dataset comprises or its data are derived from or generated in view of device-specific key performance indicators and/or instruction sets as part of the or one of the preceding downlink performance vector dataset.

According to the present invention, it is furthermore advantageously possible and preferred that regarding the specific internet-of-things communication device and a considered downlink performance vector dataset, the subsequent uplink performance vector dataset either corresponds to:.

wherein in case of the uplink performance vector dataset being timer-triggered, the timer interval corresponds to a timer interval as defined by a performance vector dataset timer indication being part of the considered downlink performance vector dataset, or a preceding downlink performance vector dataset.

It is thereby advantageously possible to trigger the (subsequent) uplink performance vector dataset in a flexible and meaningful manner; e.g. it is advantageously possible to avoid unnecessary performance vector dataset-traffic in case that the device configuration is considered comparatively optimal in which case an uplink performance vector dataset is triggered only in case of a deterioration of the operation (and/or the battery drain) of the considered device; but it is also possible to regularly or repeatedly or mandatorily trigger a (subsequent) uplink performance vector dataset as indicated by the (preceding) considered downlink performance vector dataset.

According to the present invention, it is furthermore preferred that the first or subsequent downlink performance vector dataset (i.e., any downlink performance vector dataset) is tied to a unique device identifier or identifier information of the internet-of-things communication device in question (i.e., the specific internet-of-things communication device).

According to the present invention, it is furthermore advantageously possible and preferred that, in a third step prior to the first step, the unique device profile is generated or created by the internet-of-things performance management system, especially its performance management service, wherein especially the unique device profile comprises at least one of the following:
the primary vertical or use case type, the device manufacturer and/or model, the device software version, the device hardware version, the wireless communication module manufacturer and/or model, the wireless communication module firmware version, the wireless communication module hardware version, the cloud provider, the battery manufacturer and/or model, including performance characteristics, the antenna manufacturer and/or model, the sensor and/or actuator manufacturer and/or model, the global navigation satellite system manufacturer and/or model, communication profile-related key performance indicators, radio access technology-related key performance indicators, power saving features-related key performance indicators, and deployment characteristics-related key performance indicators.

It is thereby advantageously possible to already start with a configuration of each specific internet-of-things communication device which is comparatively optimal or at least comparatively near to an optimal configuration.

According to the present invention, it is furthermore advantageously possible and preferred that between a considered downlink performance vector dataset being received by the specific internet-of-things communication device, and the subsequent uplink performance vector dataset being transmitted by the specific internet-of-things communication device, especially between the first step and the second step, the specific internet-of-things communication device, especially its performance management client functionality, processes the content of the considered downlink performance vector dataset, and especially sets a time according to the performance vector dataset timer indication and/or triggers a reconfiguration of parts, modules or components of the internet-of-things communication device, the latter especially comprising at least one out of the following:.

It is thereby advantageously possible to influence almost all operational aspects of the internet-of-things communication device, especially those having a non-negligeable influence on battery drain.

According to the present invention, it is furthermore advantageously possible and preferred that the uplink performance vector dataset, being transmitted by the specific internet-of-things communication device to the internet-of-things performance management system, especially its performance management service, comprises at least one out of the following:.

It is thereby advantageously possible that the internet-of-things communication device - by means of transmitting the considered uplink performance vector dataset - provides information regarding almost all of its parts or components, especially those having a non-negligeable influence on battery drain.

According to the present invention, it is furthermore advantageously possible and preferred that both the downlink performance vector datasets and the uplink performance vector datasets are transmitted, between the specific internet-of-things communication device and the internet-of-things performance management system, especially its performance management service, via an edge computing node, ECN, especially a base station entity or an eNodeB/radio base station or a gateway entity or a oneM2M middle node, and especially, at least in case of the uplink performance vector datasets, back-to-back of the next regularly scheduled app message in uplink direction.

It is thereby advantageously possible to efficiently transmit the performance vector datasets, and especially to limit the additional battery drain of the internet-of-things communication device for transmitting the uplink performance vector datasets.

The present invention also relates to a system for operating an internet-of-things system according to independent claim <NUM>.

The present invention further relates to an internet-of-things communication device for being operated as part of an internet-of-things system according to independent claim <NUM>.

Thereby, it is advantageously possible according to the present invention that, by means of the internet-of-things communication device, or rather by means of a plurality of internet-of-things communication devices, the internet-of-things system and/or the internet-of-things performance management system is able to be used to operate an internet-of-things system more efficiently.

Furthermore, the present invention relates to a program according to independent claim <NUM>.

Additionally, the present invention relates to a computer-readable medium according to independent claim <NUM>.

The present invention will be described also with reference to certain drawings, but the invention is not limited thereto but only by the claims.

Where an indefinite or definite article is used when referring to a singular noun, e.g., "a", "an", "the", this includes a plural of that noun unless something else is specifically stated.

Furthermore, the terms first, second, third and the like in the description are used for distinguishing between similar elements and not necessarily for describing a sequential or chronological order. It is to be understood that the terms so used are interchangeable and that other sequences than described or illustrated are possible.

An improved method for a realistic simulation of the behavior and/or the performance of an internet-of-things system and/or for determining at least one performance indicator of a simulated internet-of-things system, using an internet-of-things simulation environment is provided.

In <FIG>, an internet-of-things system <NUM> is schematically shown, comprising a (physical) communication network <NUM> as well as a plurality of internet-of-things communication devices <NUM>. The communication network <NUM> is typically a cellular communication network <NUM>, such as a public land mobile network, and is schematically represented as comprising an access network <NUM>, and a core network <NUM>. Exemplarily, a base station entity <NUM> is shown as part of the access network <NUM> of the communication network <NUM>. Furthermore, a geographical area <NUM> is schematically shown in <FIG>, this geographical area <NUM> can be understood as either corresponding to a radio cell of the access network of the communication network <NUM>, especially the radio cell <NUM> being served by the base station entity <NUM>, or, alternatively, the geographical area <NUM> can be understood as corresponding to the total geographical area of radio coverage (typically comprising a multitude of different radio cells, in turn being served by a multitude of different base station entities, not represented in detail in <FIG>) of the communication network <NUM>. In any case, the internet-of-things communication devices <NUM> of a real-world (or physical) internet-of-things system <NUM> are "in" the communication network <NUM> (or connected to the communication network <NUM>), i.e. there is, at least intermittently, a radio communication link operational between the internet-of-things communication devices <NUM> and the communication network <NUM> (typically in the form of the corresponding access network <NUM>, using a base station entity <NUM>) for the transmission of internet-of-things payload data from the internet-of-things communication devices <NUM>, respectively, to the communication network <NUM> and/or from the communication network <NUM> to the internet-of-things communication devices <NUM>, respectively.

The internet-of-things system <NUM> is operated using an internet-of-things performance management system <NUM>. This is schematically shown in <FIG>. Each one of the internet-of-things communication devices <NUM> (of the internet-of-things system <NUM>) comprises a performance management client functionality <NUM>, and especially a performance management subscription <NUM>. Furthermore, each one of the internet-of-things communication devices <NUM> operates according to configuration information. According to the present invention, in order to define the configuration information of the plurality of internet-of-things communication devices <NUM> (of the internet-of-things system <NUM>), performance vector datasets are used. These performance vector datasets are transmitted between a considered internet-of-things communication device <NUM> (represented in <FIG> and hereinafter also called specific internet-of-things communication device <NUM>) on the one hand, and the internet-of-things performance management system <NUM> (or a performance management service <NUM> thereof, i.e., as part of the internet-of-things performance management system <NUM>) on the other hand. There are performance vector datasets transmitted from the (specific) internet-of-things communication device <NUM> towards the internet-of-things performance management system <NUM>, i.e., in uplink direction; these are called uplink performance vector datasets. Furthermore, there are performance vector datasets transmitted from the internet-of-things performance management system <NUM> towards the (specific) internet-of-things communication device <NUM>, i.e., in downlink direction; these are called downlink performance vector datasets. According to the present invention (especially for each one of the internet-of-things communication devices of the system), at least a first downlink performance vector dataset <NUM> is transmitted towards the specific internet-of-things communication device <NUM> (triggered by the internet-of-things performance management system <NUM>), and at least a first uplink performance vector dataset <NUM> is transmitted, by the specific internet-of-things communication device <NUM>, towards the internet-of-things performance management system <NUM>. These performance vector datasets <NUM>, <NUM> are schematically illustrated in <FIG> between the specific internet-of-things communication device <NUM> and the internet-of-things performance management system <NUM> together with, schematically, a base station entity <NUM> of the telecommunications network <NUM> that is used with the internet-of-things system <NUM>. Especially the first downlink performance vector dataset <NUM> (but also subsequent downlink performance vector datasets; not specifically indicated by means of a reference sign in <FIG>) is adapted to the specific internet-of-things communication device <NUM>, and its respective environment or situation and/or is iteratively adapted or able to be iteratively adapted.

It is preferred that this adaptation is even improved by means of a subsequent downlink performance vector dataset (also called second uplink performance vector dataset): The first uplink performance vector dataset <NUM> comprises performance feedback information regarding the specific internet-of-things communication device <NUM> and its operation, which is processed by the internet-of-things performance management system <NUM> (especially an intelligent optimizer algorithm <NUM> and/or the performance management service <NUM> thereof). This processing triggers the second downlink performance vector dataset <NUM>, transmitted to the specific internet-of-things communication device <NUM>, wherein the second downlink performance vector dataset <NUM> comprises, compared to the first downlink performance vector dataset <NUM>, different (especially optimized) configuration information.

It is especially preferred, according to the present invention, that the different configuration information, especially compared to the first downlink performance vector dataset <NUM>, of the second or a subsequent downlink performance vector dataset <NUM> is obtained by means of the internet-of-things performance management system <NUM>, especially its performance management service <NUM>, using at least one of the following:.

Especially, the first and/or subsequent downlink performance vector dataset <NUM> or datasets is or are (or correspond) to a unique device profile, especially stored on the internet-of-things device profile library <NUM>. Furthermore especially, the first and/or subsequent uplink performance vector dataset <NUM> or datasets comprise(s), or its data are derived from or generated in view of device-specific key performance indicators and/or instruction sets as part of the or one of the preceding downlink performance vector dataset(s). Especially, the internet-of-things communication device <NUM> comprises a plurality of sensors and/or actuators, such as, e.g.,.

It is proposed to iteratively apply the first and second step (i.e. the transmission of the downlink performance vector dataset and the uplink performance vector dataset) repeatedly, and thereby realize a closed-loop system or service, providing for an optimization regarding the individual configuration of the internet-of-things communication devices <NUM> of the internet-of-things system <NUM> or service. The repetition of this exchange of performance vector datasets is preferably able to be specifically adapted for each of the internet-of-things communication devices <NUM> individually (depending on their respective environment-especially the battery draining situation), especially by means of - regarding the specific internet-of-things communication device <NUM> and a considered downlink performance vector dataset <NUM> - the subsequent uplink performance vector dataset <NUM> either corresponding to a timer-triggered uplink performance vector dataset <NUM>, or to an event-triggered uplink performance vector dataset <NUM>. In case of the uplink performance vector dataset <NUM> being timer-triggered, the timer interval especially corresponds to a timer interval as defined by a performance vector dataset timer indication being either part of the considered downlink performance vector dataset <NUM>, or being part of a preceding downlink performance vector dataset <NUM>.

Preferably in a third step prior to the first step, the unique device profile is generated or created by the internet-of-things performance management system <NUM>, especially its performance management service <NUM>, wherein especially the unique device profile comprises at least one of the following:
the primary vertical or use case type, the device manufacturer and/or model, the device software version, the device hardware version, the wireless communication module manufacturer and/or model, the wireless communication module firmware version, the wireless communication module hardware version, the cloud provider, the battery manufacturer and/or model, including performance characteristics, the antenna manufacturer and/or model, the sensor and/or actuator manufacturer and/or model, the global navigation satellite system manufacturer and/or model, communication profile-related key performance indicators, radio access technology-related key performance indicators, power saving features-related key performance indicators, and deployment characteristics-related key performance indicators.

In following example the inventive method is performed by means of ten processing steps:.

In a first processing step, a unique device profile is created:.

In a second processing step, service activation is performed: The internet-of-things service provider activates the "managed connectivity service" for one of the internet-of-things communication devices (i.e. for a 'unique' (or specific) device) on the performance management system <NUM>: the corresponding base station system (BSS) (especially for 3GPP™ scenarios) or base station entity <NUM> is triggered to communicate with the specific internet-of-things communication device <NUM>; a corresponding billing/mediation system is initialized in the background, and a "Customer Profile" (performance management subscription <NUM> of the internet-of-things communication device <NUM>) created. The latter point especially comprises to logically assign all unique device IDs (and SIM cards IMSI, if applicable) to the customer profile, in accordance with local compliance rules (authorization to host and process data, date permission given). Furthermore, the service activation especially comprises to define a validity period of "managed connectivity service" subscription per device, as well as to define (as a first key performance indicator) a "service tier", defined per device, especially according to the frequency of downlink performance vector file transfer, e.g.: light tier - set-up, yearly KPI tracking, EOL (end of life) report; medium tier - set-up, quarterly KPI tracking, EOL report; or high tier - set-up, weekly KPI tracking, EOL report.

In a third processing step, the initial downlink performance vector dataset (PVD) is generated for the (specific) device <NUM>, and especially involves one or a plurality of the following sub-steps:.

In a fourth processing step, the initial downlink performance vector dataset (PVD) is generated for the (specific) device <NUM>: The initial downlink (or first downlink) performance vector dataset <NUM> is sent to the corresponding, i.e., specific, internet-of-things communication device <NUM>, especially by means of the PMS <NUM> pushing the initial PVD <NUM> to each device via an Edge Computing Node (ECN) e.g., eNodeB/radio base station, Gateway, oneM2M Middle Node. Especially, specific policies are implemented for the downlink message, for instance: a randomization timer is used to prevent harm to the network (i.e. to ensure that the PVD times for a plurality of internet-of-things communication devices <NUM> are not terminated at the same point in time for too many devices), customer and/or device-specific settings for delivery (priority, event-based triggering) are possible, depending on the PMS configuration, this may be done during times of low traffic (e.g., non-peak hours).

In a fifth processing step, the internet-of-things communication device <NUM> processes the Initial downlink (or first downlink) performance vector dataset <NUM> (i.e. each device processes its specific initial downlink PVD), and especially involves one or a plurality of the following sub-steps:.

In a sixth processing step, the device <NUM> generates & sends uplink PVD update (i.e. each device generates an uplink PVD update), especially by means of:.

In a seventh processing step, the PMS <NUM> processes the uplink PVD (update) <NUM> (i.e. the PMS <NUM> processes the uplink PVD <NUM> (update) from each device), and especially involves one or a plurality of the following sub-steps:.

In an eighth processing step, the PMS sends downlink PVD update (i.e. the second downlink performance vector dataset) to the internet-of-things communication device <NUM> (i.e. the downlink PVD update is pushed to each device), especially by means of:.

In a nineth processing step, each device processes the downlink PVD update (i.e. the second downlink performance vector dataset (PVD file) generated is received at the corresponding device), and especially involves one or a plurality of the following sub-steps:.

The sixth to nineth processing steps are repeated according to the preferred embodiment of the present invention described here, until the managed connectivity service is discontinued.

In a tenth processing step, the performance management service is discontinued; an device (internet-of-things communication device <NUM>) is preferably able to have the managed connectivity service deactivated/resumed at any time:
Whenever the PMS <NUM> sets the PVD timer (TPVD) to a value of <NUM>, the PMC <NUM> will deactivate the managed connectivity service; the PMS <NUM> can resume the service at any time by sending to the PMC the most recent PVD file with a non-zero value of the timer TPVD.

The loT Project Profile Library (IPPL) <NUM> preferably has the purpose of building upon a virtual twin modeling data base of devices, and to find potential optimization scenarios much faster and in an adaptive way, rather than using conventional manual assessments. Hence, a "Profile Library" is proposed, especially comprising or consisting of a searchable library (in a database or a data lake) of loT projects modeled by a virtual twin modeling engine, wherein each loT project is stored in a manner that allows for quick comparison and weighting/ranking by key performance and configuration properties, including one or a plurality out of the following:.

The performance vector dataset (PVD) (either downlink <NUM> or uplink <NUM>) has the purpose to be exchanged within the managed connectivity service according to the present invention, bidirectionally between device-based clients (Performance Management Client, PMC <NUM>) and an authorized server (connectivity management server or internet-of-things performance management system <NUM> or performance management service <NUM>). The purpose of this file is to exchange data between the client and server regarding the current configuration and performance status of the device on the uplink (from client to the server), as well as to provide an initial or updated proposal of configuration changes to the device on the downlink (from server to client). The file is device-specific, i.e., it is especially tied to a unique device ID.

Regarding file handling, one or a plurality of the following formats are preferably used: JSON, CBOR, XML, YML. The transmission is performed, preferably using CoAP, MQTT, MQTT-SN, HTTP, Non-IP, and the provenance of data and/or the quality of Information (Qol) is provided or assured by means of tags. The file transfer is preferably performed, on the uplink, by the PMC <NUM> back-to-back after a regular application message from the device, only after a PVD timer (TPVD)(i.e., this may be a device-specific or generic value defined by the PMS) expires; on the downlink, the PMS <NUM> pushes an initial PVD to the unique device, respecting any specific policies which may be implemented for such downlink messages, for instance: a randomization timer is used to prevent harm to the network; customer and/or device-specific settings for delivery (priority, event-based triggering) are possible; depending on the PMS configuration, this may be done during times of low traffic (e.g., non-peak hour). All transmission to/from the server are preferably directed via an Edge Computing Node (ECN) e.g., eNodeB, Gateway, oneM2M Middle Node.

Claim 1:
Method for operating an internet-of-things system (<NUM>) using an internet-of-things performance management system (<NUM>), wherein the internet-of-things system (<NUM>) comprises a plurality of internet-of-things communication devices (<NUM>) in a communication network (<NUM>) that provides radio coverage in a predetermined geographical area (<NUM>), and - by means of transmission of internet-of-things payload data from the internet-of-things communication devices (<NUM>), respectively, to the communication network (<NUM>) and/or from the communication network (<NUM>) to the internet-of-things communication devices (<NUM>), respectively - the internet-of-things system (<NUM>) provides an internet-of-things service,
wherein each of the internet-of-things communication devices (<NUM>) comprises a performance management client functionality (<NUM>) and operates according to configuration information of a respective performance vector dataset (<NUM>, <NUM>), wherein the performance vector dataset (<NUM>, <NUM>) is adapted to the internet-of-things communication device (<NUM>), respectively, and its respective environment or situation and/or is iteratively adapted or able to be iteratively adapted, wherein, in order to operate a specific internet-of-things communication device (<NUM>), the method comprises the following steps:
-- in a first step, transmitting a first downlink performance vector dataset (<NUM>), triggered by the internet-of-things performance management system (<NUM>), towards the specific internet-of-things communication device (<NUM>),
-- in a second step, transmitting a first uplink performance vector dataset (<NUM>), by the specific internet-of-things communication device (<NUM>), towards the internet-of-things performance management system (<NUM>),
wherein the first uplink performance vector dataset (<NUM>) comprises performance feedback information regarding the specific internet-of-things communication device (<NUM>) and its operation,
wherein at least a second downlink performance vector dataset (<NUM>) is transmitted, triggered by the internet-of-things performance management system (<NUM>), towards the specific internet-of-things communication device (<NUM>), wherein the second downlink performance vector dataset (<NUM>) comprises, compared to the first downlink performance vector dataset (<NUM>), different configuration information.