Internet-Draft Fine Grained Privacy for network July 2025
Li & Liu Expires 5 January 2026 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-li-6gip-fine-grained-privacy-network-00
Published:
Intended Status:
Informational
Expires:
Authors:
L. Li
Huawei
F. Liu
Huawei Singapore

Future Requirements of Fine-Grained Privacy for the Network

Abstract

This draft describes some potential new privacy requirements for the future network. We start from the data lifecycle and propose that the privacy needs to be considered during the data is processing. We also introduce some new academic research results. Some use cases are proposed. The goal is to attract IETF working or interest groups in researching to these new requirements in protocol level for the future network.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 5 January 2026.

Table of Contents

1. Introduction

As mentioned in ITU-R "Framework and Overall Objectives of the Future Development of IMT in 2030 and beyond", new services in future network will be very likely to use computing power for data processing instead of only data transmission [ITU2083]. However, privacy issues may occur in the data processing and management phase. Possible scenarios can be sensing services and/or data analytics services, where user-related data will be collected and processed for example to derive sensing/analytic results, which may touch the sensitive information contained in the data. As shown in Figure 1, 5G networks do consider protecting user privacy with mechanisms like identity concealment, user consent and so on. However, existing mechanisms do not cover privacy preserving consideration happening in heavy data processing and management services provided in network system.

Given that the latest legal regulations (e.g., Data Act [DATAACT] and eIDAS2.0 in EU [EUDI]) force stronger privacy protection and full sovereignty of the data ownership , the lifecycle privacy-preserving consideration and management should be further enhanced.

        |
        v  Data lifecycle management
+-------------+
|  Generation/|
|  collection |
+-------------+
+-------------+
|  Storage    |
+-------------+
+-------------+
|Transmission |
+-------------+
+-------------+
| Processing  | <-----Potential
+-------------+       new issues
+-------------+
|    Usage    |
+------|------+
       |
       v
                  Figure 1: Vulnerability of privacy in data lifecycle

In future telco network, individual users may want their data being processed in their favorable way. First of all, depending conditions such as whether the user is at home, in public, or consumes certain types of services, a user may either relax or escalate the privacy preserving level. Second, a user may want to indicate at where his data shall be processed, e.g., centralized at the operator side or partly exposed to third parties. Third, a user may want to specify what type of data processing techniques shall be used to process his data to guarantee the privacy preserving strength. In general, a user expects a stronger but more fine-grained privacy-preserving consideration for data processing and management services.

Same issues have also been raised in internet apps, Regarding to the processing privacy, such as the privacy information retrieval (PIR) mentioned by Apple at WWDC25. Through PIR, a device can retrieve and return data through a server, but the server cannot associate the device with the specific returned content. This is achieved through homomorphic encryption and is open-sourced at link: https://github.com/apple/swift-homomorphic-encryption. Besides, We also see the potential of new technologies, such as private set intersection (PSI), which is very useful in cloud computing, such as in the field of federated learning. These drive us to research how new privacy-preserving technologies can be used in future networks in protocol level.

2. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

3. AIML Use case for privacy reqirements in future network

# TODO

4. Potential New Requirements of Privacy as a serivce(PrivaaS)

Several users request services where their data will be processed by the network. Given individual preferences indicated by the users, the network should provide fine-grained privacy-preserving schemes during the service time for the users. This could for example based on service types, user subscriptions/context, network states, etc.

Users A, B, and C request different network services. For example, user A uses network to browse web pages, and user B uses the network to share data with a third party to obtain third-party services. User C relies on the network to assist his vehicle self-driving, where environment sensing information including privacy content will be collected by the network.

Depending on the user's requirements and network settings, fine-grained privacy mechanisms will be used correspondingly for each user. For example:

By leveraging privacy as a service, both users' requirements are fulfilled with fine-grained privacy-preserving mechanism supported from the network such as in telecom. User requirements and service data requirements can be adapted at the same time.

4.1. Potential new privacy technique for PrivaaS

As the example shows, homomorphic encryption is just an example of a new technology. Some new technologies have been discussed in academia, and they can all be considered. The following are some examples of new potential privacy technologies for processing privacy.

#TODO: How the new technology is used at the protocol level is an ffs

5. Existing Privacy Designs in the Telco netowrk.

Requirements for privacy for 5G are defined in 3GPP TS 22.261 [TS22261]: The 5G system shall support a secure mechanism to collect system information while ensuring end-user and application privacy (e.g., application-level information is not to be related to an individual user identity or subscriber identity and UE information is not to be related to an individual subscriber identity).Some design principles have been applied to the solution, such as exposure collection of user information and use consent principles. User identifiers are also protected, such as concealment the user's permanent identity (SUPI) and using non-permanent identifiers such as GUTI(Globally Unique Temporary Identifier) and GPSI(Generic Public Subscription Identifier) to handle user-related information.

It is worth mentioning that these technologies often use pseudonymization, and the privacy of data and content processing may need to be enhanced.

Some potential WGs may be related to the privacy needs mentioned above, as follows:

TODO: Identifying more WG is ffs

7. IANA Considerations

This document has no IANA considerations.

8. Security Consideration

TODO

9. References

9.1. Normative Reference

[ITU2083]
(ITU), I. T. U., "Framework and Overall Objectives of the Future Development of IMT in 2030 and beyond", Group ITU-D SG2, , <https://www.itu.int/dms_pub/itu-d/oth/07/31/D07310000090015PDFE.pdf>.
[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/rfc/rfc2119>.
[TS22261]
3GPP, "Service requirements for the 5G system", TS 22.261, Group 3GPP/SA3, , <https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3107>.

9.2. Informative References

[DATAACT]
law, E. U., "Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on harmonised rules on fair access to and use of data (Data Act)", , <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:52022PC0068>.
[EUDI]
law, E. U., "European Commission. Proposal for a Regulation of the European Parliament and of the Council amending Regulation (EU) No 910/2014 as regards establishing a framework for a European Digital Identity.", , <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:52022PC0068>.

Acknowledgments

TODO

Authors' Addresses

Lun Li
Huawei
Faye Liu
Huawei Singapore