CN111327711A - A data service method, data service device, terminal and machine-readable storage medium - Google Patents

Abstract

Embodiments of the present application provide a data service method, a data service apparatus, a terminal, and a machine-readable storage medium. The data service method includes: running a unique data service on a terminal, the data service collects first data, and the first data includes data generated when a first type of application program that comes with the terminal is running; the data service receives the data sent by the data service SDK. Second data generated when the second type of application program installed on the terminal is running; the first data and the second data are stored. In the embodiment of the present invention, since the terminal only runs one data service, the first type of application running on the terminal collects data through the data service, and the data collected by the second type of application running on the terminal passes through the unified data service SDK. to store.

Description

A data service method, data service device, terminal and machine-readable storage medium

technical field

The embodiments of the present application relate to the field of information technology, and more particularly, to a data service method, a data service apparatus, a terminal, and a machine-readable storage medium.

Background technique

At present, the smart mobile terminals on the market or the applications running on the terminals will collect data such as the unique identification code of the terminal, the application operation, the usage time, and the usage of the terminal. After third-party data acquisition platforms and software developers obtain these data, they are used to analyze user behavior and basic hardware conditions, and provide reference and optimization suggestions for future iterations.

Generally, current applications mainly use SDKs provided by third-party platforms to record data such as terminal or software usage behavior. When the terminal is running normally, the SDK will run a service in the background, and collect and upload data according to the preset buried points. Since a terminal will run multiple merchant applications, and if each application integrates a third-party data collection SDK, then the terminal's background service will run multiple data collection services, all of which require CPU and memory resources. At the same time, it will speed up the power consumption and traffic consumption of the terminal, and the upload mechanism is basically fixed and does not allow customization. Therefore, the current method is prone to occupy system resources, the security is unknown, and the commercial scene environment is poor.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a data service method, a data service device, a terminal, and a machine-readable storage medium. Each mobile terminal only runs one data service module, and uses the data service to collect, store, and upload data for applications installed on the terminal. It can provide data services with minimal resource occupation and consumption.

On the one hand, an embodiment of the present application provides a data service method, in which a unique data service runs on a terminal, and the method includes:

The data service collects first data, and the first data includes data generated when the first type of application program that comes with the terminal is running;

The data service receives the second data sent by the data service SDK and generated when the second type of application program installed on the terminal is running;

The first data and the second data are stored.

As a preferred manner, the first data further includes basic information of the terminal, and the second data includes service data.

As a preferred manner, the storing of the first data and the second data specifically includes:

respectively encapsulating the first data and the second data into a DataBean format;

Store the encapsulated data to the content provider.

Further, the method also includes:

The data stored by the content provider is uploaded to the cloud server according to a predetermined upload policy and upload time.

Further, the method also includes:

Determine whether the uploaded data is uploaded successfully;

When judging that the uploading fails, trigger the uploading of the uploading data to be re-uploaded within the uploading time;

When it is determined that the upload is successful, the content provider is triggered to delete the successfully uploaded data.

As a preferred manner, the uploading policy is specifically provided according to the network status and traffic pattern of the terminal, and/or the data level of the stored data, and the uploading time is between 1:00 am and 4:00 am.

On the other hand, an embodiment of the present application provides a data service device, including a unique data service, a data service SDK module, and a content provider:

The data service is used to collect the first data generated when the first type of application program that comes with the terminal is running;

The data service SDK module is connected to the data service module, and is used for sending the second data generated when the second type of application program installed on the terminal is running to the data service;

The content provider is connected to the data service for storing the first data and the second data collected by the data service.

As a preferred manner, the data service device further includes an encapsulation module, which is connected to the content provider and is used to encapsulate the first data and the second data into a DataBean format, respectively, and encapsulate the encapsulated data. Data is stored to the content provider.

Further, the data service device further includes an uploading module configured to upload the data of the content provider to the cloud server according to a predetermined uploading strategy and uploading time.

Wherein, the data service device further includes a judging module, the judging module is connected to the content provider and used to judge whether the uploaded data is uploaded successfully, when the upload fails, trigger the data to be re-uploaded within the uploading time, and when the uploading fails, the data is re-uploaded. When successful, the content provider is triggered to delete the successfully uploaded data.

In another aspect, an embodiment of the present application provides a terminal, where the terminal includes any of the foregoing data service apparatuses.

As a preferred manner, the terminal further includes a data recovery module for performing data recovery when the data stored by the content provider of the data service device reaches a certain threshold.

Wherein, when the data stored by the content provider of the data service device reaches a certain threshold, the data recovery module performs recovery according to the storage time and data level of the data.

In yet another aspect, an embodiment of the present application provides a machine-readable storage medium on which executable instructions are stored, and when executed by a machine, the executable instructions enable the implementation of the above method.

It can be seen that in the above technical solution, the terminal only runs one data service (DataService), the first type of application running on the terminal collects data through the data service, and the data collected by the second type of application running on the terminal is unified The data service SDK (DataServiceSDK) is stored to the content provider (ContentProvider). By using the only data service for data collection and storage, the background service of the terminal only runs one collection service, which occupies less CPU and memory resources, and reduces the consumption of power and traffic of the terminal.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present application more clearly, the following briefly introduces the accompanying drawings that are required to be used in the description of the embodiments or the prior art. However, it should be understood by those skilled in the art that the accompanying drawings in the following description are merely some examples of the present application and do not limit its scope.

FIG. 1 is a schematic flowchart of a data service method according to an embodiment.

FIG. 2 is a schematic flowchart of another data service method according to an embodiment.

FIG. 3 is a schematic diagram of the workflow of yet another data service according to an embodiment.

FIG. 4 is a schematic structural diagram of a data service apparatus according to an embodiment.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. It should be understood by those skilled in the art that the described embodiments are some, but not all, embodiments of the present invention. Based on the embodiments in this application, those skilled in the art can make any suitable modifications or variations to obtain all other embodiments.

At present, there are various applications running on the terminal, and each application integrates the data acquisition SDK (Software Development Kit, software development kit) provided by the third-party platform. When the terminal is running normally, the SDK will run a service in the background, and press Pre-set buried points are used for data collection and uploading. This method of running multiple SDKs for data services not only occupies CPU, memory and other resources to speed up the terminal's power consumption and traffic consumption, but also has a great impact on the terminal's WIFI and base station signals. In the case of poor SIM card package traffic, data collection services and uploading will be affected.

In view of this, the embodiments of the present application provide a data service solution. In this technical solution, the terminal only runs one data service, that is, DataService. The DataService includes two parts: a data processing module and a data acquisition module. The data acquisition module is used to collect the data generated when the first type of application is running, and store the data. Now, ContentProvider (content provider), and the data independently collected by the second type of application program is stored in the ContentProvider through the DataServiceSDK, and the data processing module is used to upload the data stored in the ContentProvider to the cloud server.

The above technical solutions will be described in detail below with reference to specific embodiments.

FIG. 1 provides a schematic flowchart of a data service method according to an embodiment, which mainly includes three steps.

Step 101, the terminal runs a unique data service, the data service collects first data, and the first data includes data generated when the first type of application program that comes with the terminal is running;

In this step, the terminal runs only one data service, that is, the DataService, and the DataService stores and uploads data generated by the running of each application program installed on the terminal. Specifically, in this embodiment, the application programs running on the terminal are divided into the first type of application program and the second type of application program. The first type of application program refers to the application program that comes with the terminal from the factory and is related to the operating system of the terminal. The second type of applications refers to general commercial applications or third-party applications, which have nothing to do with the operating system of the terminal. In practical applications, the terminal in this embodiment can run under a specific operating system, such as SUNMI OS, that is, Sunmi operating system. At this time, DataServicec can collect any data of the terminal. If the terminal runs on a non-SUNMI Android ROM, then DataService cannot obtain some data that requires specific interface access, such as monitoring CPU peak value, battery power, etc., but general data collection and uploading can work normally.

Step 102: the data service receives the second data sent by the data service SDK and generated when the second type of application program installed on the terminal is running;

In this embodiment, for the second type of application installed on the terminal, the second data generated when the application is running is sent to the data service through the data service SDK. The second data here is generally service data, which may be the download speed information of the ROM package generated during the over-the-air download upgrade, the download speed of the application that needs to be collected as the application market, the number of clicks or operations of the module, and the like.

Currently, all the capabilities of DataService are used in Sunmi's own application (APP), which is not open to general commercial APPs. The DataService SDK provided in this embodiment stores the data collected by general commercial APPs in the ContentProvider.

Step 103: Store the first data and the second data.

Among them, in the embodiment of the present invention, the first data and the second data stored by the data service are collectively referred to as stored data. , to ensure that the data can be completely transmitted to the cloud server with the minimum resource occupation and consumption.

In this application, the above technical solutions can be applied to smart terminals, mobile terminals, and the like.

In one embodiment, the terminal runs only one data service, namely DataService, which runs after the terminal is powered on, records data generated when the terminal's own application runs, and collects data from general applications installed on the terminal. Data is stored to ContentProvider through DataService SDK.

In order to help those skilled in the art better understand the technical solutions of the present application, the following description will be given with reference to specific examples. However, it should be understood that these examples do not impose any limitation on the scope of protection of the present application.

Figure 2 is an example of a data service method according to one embodiment.

Step 201: the terminal runs a unique data service, and the data service runs after the terminal is powered on;

In practical applications, the data service obtains the service timestamp at the first time after it is powered on, and the specific time of the server can be known by calculating the subsequent time. The data in this service is all recorded by the server time.

The terminal in this embodiment can run under a specific operating system, such as SUNMI OS, that is, Sunmi operating system. At this time, DataServicec can collect any data of the terminal. If the terminal runs on a non-SUNMI Android ROM, DataService cannot obtain certain data. Some data that require specific interface access, such as monitoring CPU peak, battery power, etc., but general data collection, upload, etc. can run normally.

Specifically, in this embodiment, a timing service (AlarmManager) of the Android system is used to provide timing tasks, and waking up the AlarmManager is a system wake-up. Even if the system is in a dormant state, it can be woken up to process data collection tasks in the data service. This ensures that the data collection task runs on time after the set time.

After AlarmManager is started, different timing tasks and timings are set. After the timing is reached, the data service running program collects relevant data.

Step 202: the data service collects the first data generated when the first type of application program that comes with the terminal is running;

In this embodiment, the application programs running on the terminal are divided into the first type of application program and the second type of application program. The first type of application program refers to the application program that comes with the terminal from the factory and is associated with the operating system of the terminal. The second type of application program refers to a general commercial application program, which has nothing to do with the operating system of the terminal.

The data collection function of the data service of the present invention is collected based on the API provided by the Android native and customized rom, so the accurate performance of the data is well guaranteed.

Further, the first data also includes the basic information of the terminal, and the data service also collects the basic information of the terminal, and the basic information can be the terminal memory, terminal power, location information, ROM information and/or the running time of the installed APP, etc., the basic information It is collected through system broadcast. The broadcast adopts static registration. Even if the data service exits or is recycled, it can be restarted after receiving the broadcast, which can save system memory and reduce system consumption.

Step 203: the data service receives the second data sent by the data service SDK and generated when the second type of application installed on the terminal is running;

Specifically, for the second type of application installed on the terminal, the second data generated when it is running is generally business data, such as the download speed information of the system package generated by the upgrade of the second type of application, the number of clicks or operations of the module, etc. , and send it to the data service through the data service SDK, so that the collected data is stored and uploaded to the cloud server through the data service.

Among them, the second data is generally business data, which can be the download speed information of the ROM package generated during the over-the-air download upgrade, the download speed of the application that needs to be collected as the application market, the number of clicks or operations of the module, etc. The second type of application program The collected second data needs to be transmitted to the database of ContentProvider through DataServiceSDK. The ROM package is like an installation disk required when a computer is installed with a system, and in this embodiment refers to the system package of the terminal.

Step 204: Store the first data and the second data.

The data is stored in the database of the ContentProvider, and other components can store the data in the set database through the URI. In this embodiment, permission control is added here to prevent other APPs from storing or reading the data. Other components cannot read data through URI. The URI service can only add data, but cannot read data.

Specifically, the data receiving part of the data service is controlled by many broadcast receivers and timing tasks. After receiving the data, the data is pushed to the queue of the data processing module for processing one by one, and then stored in the database for preservation.

When DataService stores data, it can summarize the data of some specified important services, such as summarizing the daily traffic consumption of each APP, or summarizing the daily traffic consumption of a single device. In addition, DataService divides data into three types: detailed, semi-aggregated, and aggregated. The importance levels of these three types are detailed→low, semi-aggregated→medium, aggregated→high. The data level of the stored data will affect the to data storage and upload policies.

For convenience, this embodiment encapsulates the entire process, and other apps only need to call related APIs to complete operations.

For the storage method of the first data, all the collected first data is encapsulated into the List collection of DataBean, and stored in the ContentProvider, which can be stored in batches. Preferably, in this embodiment, the time recorded by the server shall prevail, and the data service The service timestamp is obtained at the first time after booting, and the server timestamp records the time of data collection. All the data collected between the current time and 0:00 am the next day is encapsulated into the List collection of DataBean, which is stored in the ContentProvider, which can be batched. storage.

For the storage method of the second data, the data collected by other third-party APPs is encapsulated into a fixed DataBean and stored in the ContentProvider through the DataServiceSDK.

Step 205: The data service uploads the stored data to the cloud server.

The workflow of the data service in this embodiment is shown in Figure 3. In this embodiment, the data of Sunmi APP, third-party APP and other APPs are collected respectively, and then the collected data is marked with a grade, and the collected data is passed through the DataServiceSDK Store to the content provider; when DataService uploads data, it obtains the data from the content provider, and uploads the data to the cloud server through the upload strategy and processing logic. The figure does not show the collection of the only data service installed by the Sunmi APP through the terminal, while the third-party APP and other APPs use their own collection functions, and only store the collected data to the ContentProvider through the DataServiceSDK.

The data upload function is controlled by a timed task. In this embodiment, the Android system service AlarmManager provides a timed task. Even if the system is in a dormant state, it can be woken up to process the data collection task and data upload service in the data service. It not only ensures that the data collection task runs on time after the set time, but also ensures that the time recorded by the server shall prevail when the data is uploaded, which overcomes the current data generation time using the server time and the traffic consumption on the day when the app is obtained. However, it is calculated in the local time interval, because the data cannot truly describe the traffic consumption of the day when the local time and server time do not match.

After the AlarmManager service is started, different timing tasks and timings will be set. After the timing time is reached, the data service running program collects relevant data, and waking up the AlarmManager is the system wakeup.

In practical applications, after 1:00 am every day, select a random time to start extracting data from the ContentProvider according to a certain strategy, for example, every time the data within 1MB is extracted and compressed by Gzip, an Http request upload occurs, and it is performed in multiple times until all the Uploaded successfully.

If the upload fails, it will be re-uploaded after a random period of time, and the upload will be stopped at 4:00 a.m. until the next morning. If the upload is successful, the data that has been uploaded successfully will be deleted.

In this embodiment, a verification method is provided for whether the data is uploaded successfully, and the upload result will be obtained through the interface callback. In practice, if the data cannot be obtained within 2 minutes, it will fail by default. The 2 minutes here is used as an example, and The actual time value is not limited.

In the method of uploading data between 1:00 am and 4:00 am provided in this embodiment, the data is uploaded in time according to the idle state of the implement. Compared with the method of setting a fixed time after the early morning and uploading data regularly in the existing solution, it will not cause the lag of data displayed in the backend. The idle state of the equipment refers to the time when the terminal is idle and not used.

The terminal in this embodiment also provides a data recovery module. If the accumulated data exceeding 20MB is not deleted, the data recovery function will be automatically activated, and the low-priority and early data will be deleted according to time and data level, keeping the overall data within 20MB. .

In addition, this embodiment also provides the data service to comprehensively select the upload strategy according to the current network state and traffic mode of the terminal, and combine the upload time to ensure that the data can be completely transmitted to the cloud server with minimum resource occupation and consumption.

Among them, the network status can be a network connection type, such as wifi, wired, sim card, etc. The traffic mode of the device can be the ultra-saving traffic mode or the unlimited mode. If the terminal uses a SIM card and is in the ultra-saving traffic mode, the DataService will only upload the summary data, while the terminal is in the ultra-saving traffic mode and using WIFI, the DataService will upload all the data. grade data. The upload strategy is to determine which data to upload and whether to upload it or not based on the network status and traffic pattern before uploading.

On this basis, the upload policy provided in this embodiment not only considers the network state and traffic mode of the terminal, but also can combine the data level of the stored data. High-level data is uploaded to the cloud server.

In the method provided by the embodiment of the present invention, the terminal only runs one data service, namely DataService, the data service will run after the terminal is powered on, record the first data generated when the terminal's own application program runs, and store it in the database of DataService , and store the second data collected by the general application installed on the terminal to the ContentProvider through the SDK of DataService. Both the first data and the second data are encapsulated into a List collection of DataBean and stored in the ContentProvider.

This embodiment takes the time recorded by the server as the criterion, which can avoid calculating data in the local time interval, and the data generation time is the server time.

When uploading data in this embodiment, an upload strategy is provided according to the network state and traffic pattern of the terminal, so the service provider can upload data according to its own needs, and is no longer limited by a single upload strategy, which helps the uploaded data to dynamically adapt to the network state .

In one embodiment, FIG. 4 provides a schematic structural diagram of a data service device, the data service device includes a unique data service 301, a data service SDK module 302 and a content provider 303:

The data service 301 is used to collect the first data generated when the first type of application program that comes with the terminal is running;

The data service SDK module 302 is connected to the data service module 301, and is used for sending the second data generated when the second type of application installed on the terminal is running to the data service 301;

The content provider 303 is connected to the data service 301 for storing the first data and the second data collected by the data service 301 .

Wherein, the data service device is located on a mobile terminal or an intelligent terminal.

For other functions and operations of the data service apparatus in FIG. 3 , reference may be made to the processes of the method embodiments in FIG. 1 to FIG. 2 above, which will not be repeated here in order to avoid repetition.

The data service device provided by the embodiment of the present invention records the data generated when the terminal's own application is running according to the data service running on the terminal and stores it in the database of DataService, and collects the data of the general application installed on the terminal through the DataService. The SDK is stored in ContentProvider.

In one embodiment, a schematic structural diagram of a terminal is provided, where the terminal includes any of the data service apparatuses described in the foregoing embodiments;

The data service device at least includes a unique data service, a data service SDK module and a content provider. The data service is used to collect the first data generated when the first type of application program that comes with the terminal is running; the data service SDK module is installed on the terminal. The second data generated when the second type of application program runs is sent to the data service; the content provider stores the first data and the second data collected by the data service.

Further, the terminal further includes a data recovery module for performing data recovery when the data stored by the content provider reaches a certain threshold.

Specifically, data recovery is performed according to the data storage time and data level. In practice, data with low priority and/or data with an earlier storage time are generally recovered.

In practice, the threshold can be 20MB. If the data hoarding of the content provider exceeds 20MB and the data is not deleted, the data recovery function will be automatically activated, and the low-priority and early data will be deleted according to the time and data level, keeping the overall data in the Within 20MB.

Wherein, the terminal may be an intelligent terminal or a mobile terminal, and the terminal can run the android system.

The terminal provided by the embodiment of the present invention collects and stores the data generated when the terminal's own application program runs and the third-party application program installed by the terminal according to the unique data service running on the terminal, and uploads it to the cloud server, through the unique data service Completing the data collection and storage operation helps to reduce the number of collection services running in the terminal background service. Compared with the current integration of third-party data collection SDKs for each application, multiple collection services are run in the device background service, which consumes a large amount of In the case of CPU and memory resources, this embodiment does not need to occupy a large amount of CPU and memory resources, and can speed up the power consumption and traffic consumption of the device.

In addition, the embodiments of the present application further provide a machine-readable storage medium. The machine-readable storage medium may store executable instructions, which, when executed by the machine, cause the machine to implement the specific processes of the method embodiments described above with reference to FIGS. 1 to 2 .

For example, a machine-readable storage medium may include, but is not limited to, random access memory (Random Access Memory, RAM), read-only memory (Read-Only Memory, ROM), electrically-erasable programmable read-only memory (Electrically-Erasable Programmable Read-only memory) -Only Memory, EEPROM), static random access memory (Static Random Access Memory, SRAM), hard disk, flash memory, etc.

It can be understood by those skilled in the art that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may implement the described functions in different ways for each specific application, but such implementations should not be considered beyond the scope of this application.

In the embodiments of the present application, the disclosed systems, devices, and methods may be implemented in other manners. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system. In addition, the coupling between the various units may be direct coupling or indirect coupling. In addition, each functional unit in the embodiments of the present application may be integrated into one processing unit, or may exist independently physically, or the like.

The functions, if implemented in the form of software functional units and sold or used as separate products, may be stored in a machine-readable storage medium. Therefore, the technical solution of the present application may be embodied in the form of a software product, and the software product may be stored in a machine-readable storage medium, which may include several instructions to enable the electronic device to execute the technical solutions described in the embodiments of the present application. all or part of the process. The above-mentioned storage medium may include ROM, RAM, removable disks, hard disks, magnetic disks or optical disks and other mediums that can store program codes.

The above contents are only specific embodiments of the present application, and the protection scope of the present application is not limited thereto. Those skilled in the art can make changes or substitutions within the technical scope disclosed in this application, and these changes or substitutions should all fall within the protection scope of this application.

Claims (15)

1. A data service method, wherein a unique data service is run on a terminal, the method comprising:

the data service acquires first data, wherein the first data comprises data generated when a first type of application program carried by the terminal runs;

the data service receives second data which are sent by the data service SDK and generated when a second type of application program installed on the terminal runs;

storing the first data and the second data.

2. The method of claim 1, wherein the first data further comprises basic information of a terminal, and wherein the second data comprises service data.

3. The method according to claim 1 or 2, wherein the storing the first data and the second data specifically comprises:

respectively packaging the first data and the second data into a DataBean format;

the packaged data is stored to the content provider.

4. The method of claim 3, further comprising:

and uploading the data stored by the content provider to a cloud server according to a preset uploading strategy and uploading time.

5. The method of claim 4, wherein the upload time comprises a locate upload time, the method further comprising:

providing timing acquisition time and timing uploading time according to timing service of the android system;

when the timing acquisition time is reached, starting the data service to acquire first data;

and when the timed uploading time is reached, uploading the data stored by the content provider to a cloud server according to the uploading strategy.

6. The method of claim 4, further comprising:

judging whether the uploaded data is uploaded successfully or not;

when the uploading failure is judged, triggering the uploading data to be uploaded again within the uploading time;

and triggering the content provider to delete the successfully uploaded data when judging that the uploading is successful.

7. The method according to claim 4, wherein the uploading policy is provided according to a network status and a traffic pattern of the terminal and/or a data level of stored data, and the uploading time is from 1 am to 4 am.

8. A data service arrangement, characterized in that the data service arrangement comprises a unique data service, a data service SDK module and a content provider,

the data service is used for acquiring first data generated when a first type of application program carried by the terminal runs;

the data service SDK module is connected with the data service module and used for sending second data generated when a second type of application program installed on the terminal runs to the data service;

the content provider is connected with the data service and used for storing the first data and the second data collected by the data service.

9. The apparatus of claim 8, wherein the data service further comprises an encapsulation module, connected to the content provider, for encapsulating the first data and the second data into DataBean format, respectively, and storing the encapsulated data to the content provider.

10. The apparatus according to claim 8 or 9, wherein the data service apparatus further comprises an uploading module, configured to upload the data stored by the content provider to a cloud server according to a predetermined uploading policy and uploading time.

11. The device according to claim 10, wherein the data service device further comprises a judging module, connected to the content provider, for judging whether the upload of the upload data is successful, and when the upload is unsuccessful, the data is triggered to be uploaded again within the upload time, and when the upload is successful, the content provider is triggered to delete the successfully uploaded data.

12. A terminal, characterized in that it comprises a data service device according to any of claims 8-11.

13. The terminal of claim 12, further comprising a data recycling module for recycling data when the data stored by the content provider of the data service device reaches a certain threshold.

14. The terminal of claim 13, wherein the data recovery module recovers data stored by a content provider of the data service device according to a storage time and a data level of the data when the data reaches a certain threshold.

15. A machine-readable storage medium having stored thereon executable instructions that when executed by a machine result in the implementation of a method according to any one of claims 1-7.

Images