Data anonymization for service subscriber's privacy
An IoT/M2M service layer may be provided with the capability to protect user privacy. This functionality may allow the IoT/M2M service layer to anonymize user data, particularly when user data is shared with third party consumers. A privacy policy service may enable the IoT service layer system to generate anonymization (e.g., privacy) policies based on inputs such as legal obligations, subscriber privacy preferences, and an authorization level of the data consumer. Data anonymization policies may be output from the privacy policy service and may be sent to a data anonymization service, where raw data may be anonymized based on the one or more data anonymization policies. The output from the data anonymization service function may be a privatized (e.g., anonymized) version of data that may prevent the data consumer from discovering one or more identifying characteristics of a user.
1 . A method comprising:
receiving, by a service supporting service capabilities through a set of Application Programming Interfaces (APIs) and from an application service provider, a request to access data;
determining, by the service and based on the request to access the data, one or more privacy policies to be applied to the data for the application service provider, wherein the one or more privacy policies are generated by the service based on a subscriber privacy preference preconfigured by the service based on a request from a subscriber;
generating, by the service and based on the determined one or more privacy policies, an anonymized data set that prevents the application service provider from determining one or more user-identifying characteristics of the data; and
sending, to the application service provider, the anonymized data set.
2 . The method of claim 1 , wherein the subscriber privacy preference is preconfigured by the service upon obtaining subscriber's consent to the service's privacy policy.
3 . The method of claim 1 , wherein generating the anonymized data set comprises one or more of removing at least a portion of the data or modifying at least a portion of the data.
4 . The method of claim 3 , wherein modifying at least a portion of the data comprises one or more of abbreviating at least a portion of the data, substituting at least a portion of the data, shuffling at least a portion of the data, or encrypting at least a portion of the data.
5 . The method of claim 1 , wherein the one or more privacy policies comprise one or more user policies associated with a particular user, one or more application service provider policies, or one or more legal policies.
6 . The method of claim 1 , wherein the request to access the data comprises one or more characteristics associated with the application service provider.
7 . The method of claim 6 , further comprising selecting, based at least on the one or more characteristics associated with the application service provider, one or more of a plurality of privacy policies.
8 . The method of claim 1 , wherein sending the anonymized data set comprises sending, to the application service provider, at least one of an indication that the data has been anonymized or an indication of the anonymization techniques used to anonymize the data.
9 . An apparatus for a service of a communications network, wherein the service supports service capabilities through a set of Application Programming Interfaces (APIs), the apparatus comprising circuitry configured to:
receive, from an application service provider, a request to access data;
determine, based on the request to access the data, one or more privacy policies to be applied to the data for the application service provider, wherein the one or more privacy policies are generated by the service based on a subscriber privacy preference preconfigured by the service based on a request from a subscriber;
generate, based on the determined one or more privacy policies, an anonymized data set that prevents the application service provider from determining one or more user-identifying characteristics of the data; and
send, to the application service provider, the anonymized data set.
10 . The apparatus of claim 9 , wherein the subscriber privacy preference is preconfigured by the service upon obtaining subscriber's consent to the service's privacy policy.
11 . The apparatus of claim 10 , wherein the circuitry is configured to generate the anonymized data set by one or more of removing at least a portion of the data or modifying at least a portion of the data.
12 . The apparatus of claim 11 , wherein the circuitry is configured to modify at least a portion of the data by one or more of abbreviating at least a portion of the data, substituting at least a portion of the data, shuffling at least a portion of the data, or encrypting at least a portion of the data.
13 . The apparatus of claim 9 , wherein the one or more privacy policies comprise one or more user policies associated with a particular user, one or more application service provider policies, or one or more legal policies.
14 . The apparatus of claim 9 , wherein the request to access the data comprises one or more characteristics associated with the application service provider.
15 . The apparatus of claim 14 , wherein the circuitry is further configured to perform operations comprising selecting, based at least on the one or more characteristics associated with the application service provider, one or more of a plurality of privacy policies.
16 . The apparatus of claim 9 , wherein the circuitry is configured to send the anonymized data set by sending, to the application service provider, at least one of an indication that the data has been anonymized or an indication of the anonymization techniques used to anonymize the data.
17 . The method of claim 1 , wherein the service is provided as a middleware service for IoT services.
18 . The method of claim 17 , wherein the middleware service is a service layer located on top of network protocol stacks.
19 . The method of claim 18 wherein the service layer is defined according to ETSI/oneM2M standards.