Enabling privacy compliant data set service for ai training in communication systems
The 6G network system addresses the limitations of current 3GPP architecture by integrating Data Marketplace and Privacy Engine functionalities to ensure secure, privacy-compliant data services for AI training, enhancing user consent management and anonymization, thus supporting AI applications while maintaining regulatory compliance.
Patent Information
- Application Number
- PCT/US2026/025960
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-30
- Publication Date
- 2026-11-12
AI Technical Summary
Current 3GPP architecture lacks a unified mechanism for managing large-volume dataset provisioning that satisfies user privacy preferences, regional regulations, and commercial licensing requirements, limiting the ability of operators and third-party developers to participate in privacy-aware data ecosystems for AI training.
A 6G network system is proposed with functionalities like a Data Marketplace, Consent Management, Privacy Engine, Anonymization/Synthetic Data, Charging Function, and Audit & Compliance NFs to support dynamic intent-based data requests, enforce multi-level user consent, and provide scalable anonymization and monetizable data delivery.
Enables secure, privacy-preserving, and regulation-compliant data services that support AI-based applications, safeguarding user interests and enabling trusted collaboration among stakeholders.
Smart Images

Figure US2026025960_12112026_PF_FP_ABST
Abstract
Description
ENABLING PRIVACY COMPLIANT DATA SET SERVICE FOR Al TRAINING IN COMMUNICATION SYSTEMSCROSS-REFERENCE TO RELATED APPLICATION(S)
[0001] This application claims priority to Indian Provisional Patent Application No.202541044864, filed on May 9, 2025, and Indian Non-Provisional Patent Application No.202541044864, filed on November 7, 2025, the entire contents of which are incorporated herein by reference.FIELD
[0002] The present disclosure relates to enabling privacy compliant data set service for Artificial Intelligence (Al) training in communication systems.BACKGROUND
[0003] The exponential growth of mobile communications, coupled with the increasing deployment of intelligent services, has led to a significant rise in the generation of data across networks. In next-generation mobile systems, particularly those envisioned under 6G, Mobile Network Operators (MNOs) are expected to handle massive volumes of data generated by User Equipment (UE), connected devices, sensors, and network infrastructure. This data may include information related to mobility patterns, service usage, Quality of Service (QoS), environmental metrics, and more. Artificial Intelligence (Al) and Machine Learning (ML) technologies are increasingly being utilized to extract insights from such data to enable various data-driven applications. The quality, scale, and real-time nature of mobile network data make it a highly valuable asset for training and improving AI / ML models across these domains.
[0004] The information disclosed in this background section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.SUMMARY
[0005] In an embodiment, the present disclosure discloses a method for receiving a request for access to network data, from an Artificial Intelligence (Al) service provider. The method comprises determining whether access to the network data is permitted based on one or more access permissions. The method further comprises generating a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data. Furthermore, the method comprises providing the modified version of the network data to the Al service provider over a secured communication channel.
[0006] In an embodiment, the present disclosure discloses a network system. The network system comprises a processor, a plurality of network functions and a memory. The processor in conjunction with the plurality of network functions is configured to receive a request for access to network data, from an Artificial Intelligence (Al) seivice provider. The processor in conjunction with the plurality of network functions is configured to determine whether access to the network data is permitted based on one or more access permissions. Further, the processor in conjunction with the plurality of network functions is configured to generate a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data. Furthermore, the processor in conjunction with the plurality of network functions is configured to provide the modified version of the network data to the Al service provider over a secured communication channel.
[0007] In an embodiment, the present disclosure discloses a non-transitory computer readable medium. The non-transitory computer readable medium including instructions for performing operations comprising receiving a request for access to network data, from an Artificial Intelligence (Al) service provider. The operations comprises determining whether access to the network data is permitted based on one or more access permissions. Further, the operations comprises generating a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data. Furthermore, the operations comprises providing the modified version of the network data to the Al service provider over a secured communication channel.BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which reference numerals denote like elements, and wherein:
[0009] Fig. 1 illustrates an exemplary environment for supporting secure and privacy-compliant dataset services for Artificial Intelligence (Al) training in a mobile communication system, in accordance with embodiments of the present disclosure;
[0010] Fig.2 illustrates a block diagram of a device to enable secure and privacy-compliant dataset services for Al training in a mobile communication network, in accordance with some embodiments of the present disclosure;
[0011] Fig.3 illustrates an exemplary signalling diagram for enabling privacy-compliant, consent-aware dataset provisioning in the communication system in accordance with an embodiment of the present disclosure; and
[0012] Fig. 4 illustrates an exemplary flow chart illustrating method steps for enabling privacy compliant data set service for Al training in communication systems, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION
[0013] The following detailed description of example embodiments refers to the accompanying drawings. The present disclosure provides illustrations and descriptions but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the present disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flow chart and description of operations provided below relate to at least one of the embodiments in the present disclosure. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).
[0014] It will be apparent that systems and / or methods described herein may be implemented in different forms of hardware, software, or a combination of hardware and software. The actualspecialized control hardware or software code used to implement these systems and / or methods should not limit their implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.
[0015] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, the particular combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Even if a dependent claim directly depends on only one claim, the present disclosure may indicate that the dependent claim is dependent on other claims in the claim set.
[0016] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” (in other words, nouns not mentioned in the plural) are intended to include one or more items and may be used interchangeably with “one or more.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.
[0017] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.
[0018] Third Generation Partnership Project (3GPP) for 5G mobile networks define a servicebased architecture (SBA) that enables modular and standardized interactions among network functions. Functions such as the Network Exposure Function (NEF), Policy Control Function (PCF), Unified Data Management (UDM), and Application Function (AF) support capabilities such as event notification, subscription-based data access, and user-specific policy enforcement. The exposure framework allows external applications to access certain data and services through authorized APIs, subject to predefined policies and service-level agreements. The emergence of data-driven use cases in domains such as intelligent transportation, smart infrastructure,personalized healthcare, and immersive applications has introduced a growing demand for access to large-scale datasets derived from user activity, mobility behavior, network performance, and service interactions. Such datasets are increasingly considered valuable for Artificial Intelligence (Al) model development and training, especially where real-world, diverse, and high-frequency data can enhance inference accuracy or support context-aware automation.
[0019] While existing 3GPP architecture supports limited forms of data exposure, such as charging information, mobility events, or service usage metrics, it does not provide a unified mechanism for managing large-volume dataset provisioning in a manner that satisfies user privacy preferences, regional regulations, and commercial licensing requirements. Current mechanisms lack support for dynamic dataset discovery, category -based consent enforcement, or fine-grained anonymization prior to exposure. As a result, third-party Al service providers seeking access to network-derived datasets must often rely on external arrangements or operator-specific integrations that fall outside standardized architectural control.
[0020] 3GPP Technical reports such as TR 22.874 and TR 23.700-series have initiated studies into enabling enhanced data collection and analytics capabilities in 5G and future networks such as 6G. These efforts acknowledge the potential of the mobile network as a source of intelligence for external applications. However, standardized methods for governing access to such data, particularly in the context of Al training, remain undefined. Moreover, privacy-preserving data transformation techniques such as pseudonymization, differential privacy, or federated learning are not natively integrated into the current architectural model for data access or exposure.
[0021] There is, therefore, a growing need to explore new paradigms for enabling secure, privacy -preserving, and regulation-compliant data services that can support the evolving demands of AI-based applications while safeguarding user interests and enabling trusted collaboration among stakeholders.
[0022] In the context of evolving mobile systems such as 6G, which are expected to support more pervasive sensing, context-awareness, and Al-native infrastructure, the role of the network in facilitating secure and privacy-compliant data services is expected to expand However, no architectural provisions currently exist to support dynamic intent-based data requests, enforcement of multi-level user consent, scalable anonymization pipelines, or monetizable and auditable data delivery workflows for Al service consumers. These gaps limit the ability of operators and third-party developers to participate in privacy-aware data ecosystems at a scale.
[0023] Although these limitations are described with respect to 5G and 6G systems, similar challenges are anticipated in other future network generations unless explicit support is introduced for the controlled provisioning of datasets intended for Al or analytics purposes. The architectural elements responsible for such operations may be distributed across core, edge, and external domains, and may rely on a combination of standardized interfaces and deployment-specific configurations depending on implementation.
[0024] Abstract:
[0025] The present disclosure proposes new requirements for Use case on 6G System Supporting Secure and Privacy-Compliant Data Set Service for Al Training into TR 22.870 v0.2.1
[0026] Introduction:
[0027] The present contribution proposes a new use case on Use case on 6G System Supporting Secure and Privacy-Compliant Data Set Service for Al Training.
[0028] Reason for Change:
[0029] TR 22.870 vO.2.1 does not yet contain any use case that covers Use case on 6G System Supporting Secure and Privacy-Compliant Data Set Service for Al Training..
[0030] Proposal
[0031] It is proposed to agree the following changes to 3GPP TR 22.870 v0.2.1
[0032] 6.x Use case on 6G System Supporting Secure and Privacy-Compliant Data Set Service for Al Training
[0033] 6.x.l Description:
[0034] Mobile Network Operators (MNOs) in 6G systems will have access to vast amounts of real-time, high-quality data generated by users, devices, and network functions — including mobility patterns, traffic flows, service usage metrics, and QoS / KPI measurements not to mention huge volumes of Al inference data. This data holds immense value for AI / ML model training, particularly for industries like smart cities, autonomous transportation, predictive healthcare, and personalized sendees. However, accessing such datasets is often challenging for third-party Al developers due to privacy regulations (e.g., GDPR, CCPA), lack of scalable data collection infrastructure, and concerns about data bias or quality. With the advent of new data intensive services such as Sensing etc., we see the Concept of Telco as the Future Data Bank for a Country (refer SI -242023)
[0035] This use case enables MNOs to act as trusted intermediaries in a privacy-preserving data marketplace, where:
[0036] User Consent & Control:A. Users grant / revoke consent for specific data categories (e.g., location, browsing behaviour)B. Consent is dynamically enforced at the network level via existing or enhanced subscription mechanisms.
[0037] Anonymization & Privacy Techniques:A. Raw data is processed using various techniques (e.g., k-anonymity, differential privacy, or synthetic data generation) to prevent re-identification.B Various forms of learning techniques e.g., Federated learning (FL) may be supported, allowing Al training without raw data leaving the MNO’s domain.
[0038] Monetization & Licensing:A. MNOs offer tiered datasets (e.g., Real-time footfall data (premium tier for advertisers) vs historical trends (cheaper, bulk datasets for urban planning)) with usage-based pricing. B. Smart contracts (e.g., via blockchain) automate compliance (e.g., data retention limits, purpose restrictions).
[0039] Regulatory Compliance:A. Built-in mechanisms enforce regional rules (e.g., GDPR’s "right to be forgotten," data minimization).B. Audit logs track data access for accountability.
[0040] Example Scenarios where these services can be offered are:A. A smart city planner purchases anonymized foot-traffic data from an MNO to optimize public transport routes.B. An advertising firm uses federated learning to train recommendation engines without accessing raw user profiles.
[0041] 6.x.2 Pre-conditions:
[0042] The MNO has established legal agreements with third-party Al service providers for data sharing. The 6G system implements:A. Data anonymization / pseudonymization functions.B. Consent management framework (e.g., per-category user preferences).C. Secure data delivery APIs (e.g., encrypted datasets, tokenized access).
[0043] Regulatory compliance is ensured (e g., regional data protection laws).
[0044] 6,x,3 Service Flows:
[0045] The service flow is as following:
[0046] 1. Third-party request:
[0047] An Al service provider requests access to specific anonymized datasets (e.g., mobility trends).
[0048] The request could be in the form on an intent e.g.,
[0049] “I need to train a model for UE mobility for Tokyo West from 6 am to 6 pm for traffic light optimization.
[0050] Provide anonymized batch mobility traces dataset for Tokyo West, weekdays 6AM-6PM, at 5-minute granularity and at least 10,000 unique UEs / day to avoid bias for traffic optimization training.”
[0051] 2. Authorization & consent check:a. The 6G system verifies the third party’s credentials.b. The system confirms user consent for the requested data categories.
[0052] 3. Data processing:a. The MNO’s privacy engine applies anonymization (e.g., k-anonymity, synthetic data generation).b. Optional: Data is pre-processed (e.g., aggregated, noise-injected) for privacy preservation.
[0053] 4. Secure delivery:a. The dataset is transferred via a secure channel (e.g., encrypted, audit-trailed)b. Usage restrictions (e.g., retention period) are enforced via smart contracts.
[0054] 5. The MNO charges the third party based on data volume / utility (e.g., per-record, subscription model).
[0055] 6.x.4 Post-conditions:1. The Al service provider obtains high-quality, compli nt datasets for model training.2. Users retain control over their data via granular consent settings.3. The MNO generates revenue while maintaining regulatory compliance.
[0056] 6.x.5 Existing features partly or fully covering the use case functionality: <tbd>
[0057] 6.x.6 Potential New Requirements needed to support the use case:
[0058] [6. X.6-1] Based on operator’s policy, user consent and local regulations the 6G network shall support secure mechanisms for dataset discovery (e.g., metadata search, sample access, category of data) for third parties to via intent.
[0059] [6. X.6-2] The 6G network shall include configurable (i.e. dynamic) anonymization, consent enforcement, and audit logging.
[0060] [6. X.6-3] The 6G system shall support privacy mechanisms for aggregated data sharing.
[0061] [6. X.6-4] The 6G network shall be able to charge for these services.
[0062] Key 6G Network Functions (NFs) Introduced
[0063] 1. 6G Data Marketplace (NF)A. Discovers, licenses, and brokers datasets between MNOs and third parties.B. Integrates with smart contracts for automated compliance.
[0064] 2. Consent Management (NF)A. Manages granular user consent (e.g., location, browsing history) via UE dashboards. B. Enforces dynamic consent revocation.
[0065] 3. Privacy Engine (NF)A. Applies differential privacy, k-anonymity, or synthetic data generation.B. Supports federated learning workflows (data stays on-premises).
[0066] 4. Anonymization / Synthetic Data (NF)A. Generates non-reversible anonymized datasets.B. Optional: Federated Learning Aggregator for distributed Al training.
[0067] 5. Charging Function (NF)A. Usage-based pricing (per-record, subscription).B. Blockchain-integrated smart contracts for automated payments.
[0068] 6. Audit & Compliance (NF)A. Logs all data access for GDPR / CCPA compliance.B. Enforces "right to be forgotten" deletions.
[0069] Call Flow Steps:
[0070] 1. Dataset RequestA. Third-party queries the Data Marketplace NF for a dataset (e.g., "real-time mobility data").
[0071] 2. Consent VerificationA. Consent Management NF checks user permissions via UE privacy dashboard.
[0072] 3. Privacy EnforcementA. If consent exists, Privacy Engine NF applies anonymization (e.g., noise injection).
[0073] 4. Secure DeliveryA. Data is encrypted and transferred with usage restrictions (e.g., 30-day retention).
[0074] 5. Monetization & ComplianceA. Charging NF charges the third party; Audit NF records the transaction.
[0075] Fig. 1 illustrates an exemplary environment 100 for supporting secure and privacy-compliant dataset services for Artificial Intelligence (Al) training in a mobile communication system, in accordance with embodiments of the present disclosure. The exemplary environment 100 includes a User Equipment (UE) 102, a network 104, and an Al service provider 106. The environment 100 serves as a high-level framework for enabling data-driven interactions among user devices, network infrastructure, and authorized third-party Al applications. In particular, the configuration shown in Fig. 1 represents the foundational environment for enabling controlled access to network-generated data while adhering to user consent preferences and applicable privacy regulations. The UE 102 represents any end-user device configured to access services over the mobile communication system. The UE 102 may include, but is not limited to, smartphones, tablets, laptops, wearabl es, connected vehicles, or any other device capable of communicating with the network 104. In some embodiments, the UE 102 may be a source of data related to mobility, application usage, radio environment characteristics, or other behavioural attributes. The UE 102 may operate in accordance with subscription and privacy settings that govern processing or sharing of data associated with the user by the network.
[0076] The network 104 represents the communication infrastructure that facilitates data exchange between the UE 102 and the Al service provider 106. In an embodiment, the network 104 corresponds to a 6G system comprising both access and core segments, including New Radio (NR) access nodes, transport mechanisms, and core network functions. The network 104 may provide the necessary connectivity, session control, and service-level enforcement to support the secure provisioning and delivery of datasets in response to authorized requests. Depending on implementation, the network 104 may include various logical and physical components configured to perform data collection, consent enforcement, transformation (e.g., anonymization), and exposure functions.
[0077] The Al service provider 106 represents an external application, platform, or authorized entity that utilizes datasets derived from network infrastructure for the purpose of Al training or inference. The Al service provider 106 may be associated with domains such as, but not limited to, smart infrastructure, mobility optimization, retail analytics, or public planning In an embodiment, the Al service provider 106 submits a request to the network 104 for access to specific types of data such as, but not limited thereto, mobility traces, service usage statistics subject to predefined parameters such as time window, location, or data granularity among others. The network 104 may validate such requests based on access permissions, applicable user consent, and policy constraints before provisioning the requested dataset.
[0078] While Fig. 1 shows a high-level conceptual architecture, the internal details of the network 104, including the presence of one or more functional components such as consent managers, privacy engines, or data exposure interfaces, are abstracted at this stage. These components may be instantiated as logical functions within the core network or as part of distributed service platforms deployed at the edge or in the cloud. The interactions shown in Fig. 1 are intended to represent a generalized environment that supports secure and policy-compliant data services in alignment with emerging 6G architecture principles. In some embodiments, the network 104 may also support mechanisms for logging access events, managing data retention policies, and enforcing restrictions on downstream usage of the datasets provided to the Al service provider 106 The architecture shown in Fig. 1 thus enables a privacy-preserving, consent-aware, and standards-aligned approach to facilitating Al-centric use cases that rely on data generated within mobile communication systems.
[0079] Fig. 2 illustrates a block diagram of a device 200 to enable secure and privacy-compliant dataset services for Al training in a mobile communication network, in accordance with some embodiments of the present disclosure. In an embodiment, the device 200 may be implemented as functional component within a network entity, such as a 6G network node, a data exposure gateway, or a service function deployed in a trusted cloud or edge domain. As shown in the Fig. 2, the device 200 includes a processor 210, a memory 220, a storage component 230, an input component 240, an output component 250, a communication interface 260, and a bus 270.
[0080] The processor 210, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 210 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-coreprocessors and / or one or more single core processors, a distributed processing system, or the like. The processor 210 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.
[0081] The memory 220 includes a non-transitory computer readable medium. The memory 220 includes a Random-Access Memory (RAM), a Read Only Memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by the processor 210. The memory 220 comprises machine-readable instructions which are executable by the processor 210. These machine-readable instructions when executed by the processor 210 cause the processor 210 to perform one or more method steps of an embodiment described.
[0082] Storage component 230 stores information and / or software related to the operation and use of the DU 106. For example, storage component 230 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.
[0083] Input component 240 is configured to receive information, such as user data. For example, the input component 240 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 240 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).
[0084] The output component 250 is configured to provide output information from the device 200. For example, the output component 250 may be, but not limited to, a display, a speaker, an instruction device to an external device, and / or one or more light-emitting diodes (LEDs).
[0085] Communication interface 260 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 260 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 200 and other devices. In other words, the standard of the communication interface 260 is not limited.
[0086] The bus 270 acts as an interconnect between the processor 210, the memory 220, the storage component 230, the input component 240, the output component 250, and the communication interface 260 of the device 200. The bus 270 may include a wired interconnection or a wireless interconnection.
[0087] In an embodiment, the device 200 may correspond to a network system configured to enable secure, policy-controlled, and privacy-preserving access to network-derived datasets for Al training applications. The processor 210, in conjunction with memory 220 and communication interface 260, may be configured to implement a set of operations associated with dataset request handling, consent verification, data transformation, delivery orchestration, and compliance enforcement. In one embodiment, the processor 210 in conjunction with the plurality of network functions, is configured to receive a request for access to network data from the Al service provider..
[0088] Upon receiving a dataset access request via communication interface 260 the processor 210 is configured to check a consent database for determining whether consent exists for the requesting Al service provider to access the network data, wherein the consent database stores the one or more access permissions for a plurality of categories of the network data. In this context, the processor 210 may communicate with a Consent Management Function (CMF) or a User Data Management (UDM) function to retrieve fine-grained, per-category consent metadata corresponding to end users whose data may be implicated in the dataset. For example, consent may vary across data categories such as mobility traces, application usage, or location history, and may be user-specific or aggregated based on subscription tier or data sensitivity classification. If access is not permitted, the processor 210, in conjunction with the plurality of network functions, is configured to deny the request for access for at least a portion of the requested dataset. However, if the request is authorized, the processor 210 invokes one or more data transformation techniques, which may include removing direct identifiers, generalizing sensitive attributes, and generating artificial records. These techniques are applied based on one or more predefined data protection policies, and may be retrieved from stored policy configurations in memory 220 or storage 230 Prior to exposing this data, the processor 210 may also be configured to invoke one or more privacy transformation mechanisms based on configurable policy rules. These transformations may include anonymization (e.g., k-anonymity), attribute generalization, synthetic data generation, or federated abstraction layers, depending on the risk profile and usage purpose.
[0089] In some embodiments, the processor 210 may further enrich the data with context-aware attributes or temporal smoothing to avoid re-identification risks. For example, when a request includes parameters such as "mobility traces from 6 AM to 6 PM in a specific urban district," the network 104 may inject noise or bucket time intervals to maintain differential privacy guarantees while preserving dataset utility for model training. The data transformation logic may be retrieved from stored configurations in storage component 230 or adapted dynamically based on consent constraints.. Once the modified version of the network data is generated, the processor 210, in conjunction with the plurality of network functions, is further configured to encrypt the modified version of the network data prior to providing it to the Al service provider, ensuring end-to-end confidentiality. The delivery is executed over a secure channel facilitated by communication interface 260. Optionally, metadata indicating usage terms, retention periods, and downstream constraints may accompany the dataset.
[0090] The device 200 may also support reverse consent enforcement or data access revocation. In case a user withdraws consent post-disclosure or a regulator invokes a right-to-be-forgotten request, the processor 210 is configured to track affected datasets, issue revocation notices or deletion triggers, and update downstream usage logs accordingly. In some embodiments, the output component 250 may provide a real-time summary or compliance report to network operators or auditors, while the input component 240 may be used to configure tiered dataset offerings, consent templates, or policy thresholds. For example, different data classes (e.g., real-time mobility vs. coarse historical summaries) may be allocated different monetization schemes, which are managed and executed by internal business logic modules running on the processor 210.
[0091] Fig. 3 illustrates an exemplary signalling diagram 300 for privacy-compliant and consent-aware provisioning of network data to the Al service provider, in accordance with some embodiments of the present disclosure. In an embodiment, the signaling diagram 300 illustrates a network environment comprising a plurality of functional entities that collectively form part of a network system configured to facilitate privacy-compliant data provisioning in a 6G communication framework. The environment includes a Third-Party Al service provider 302 (similar to the Third-Party Al service provider 106 described under Fig. 1), a 6G Data Marketplace implemented as a Network Function (NF) 304, a Consent Management Function (NF) 306, a Privacy Engine (NF) 308, an Anonymization / Synthetic Data Generation Function (NF) 310, a Charging Function (CHF) 312, an Audit and Compliance Function (NF) 314, and one or more UserDevices (UEs) 102. In some embodiments, the network functions 304 through 314 may be implemented as virtualized, containerized, or distributed modules within the 6G core network or an associated edge domain. These NF s may also operate collaboratively to orchestrate end-to-end policy enforcement, consent validation, data transformation, and secure delivery workflows as further described herein.
[0092] At step 1, a request to access the network data is received from the Al service provider 302 by the 6G Data Marketplace 304. This corresponds to the step of receiving a request for access to network data from the Al service provider. In an embodiment, the request may be made to access a specific category of dataset (e.g., aggregated mobility trends or behavioural metrics among others). This request may also include data selection parameters such as a desired time range, geographical scope, category or type of data (e.g, mobility traces, application metadata), and intended use case (e g., model training, behavior analysis), and corresponds to the step of receiving a request for access to network data from the Al service provider 302. At step 2, the Data Marketplace 304 initiates a process to determine whether access to the requested network data is permitted based on one or more access permissions. For this purpose, the Data Marketplace 304 interacts with the Consent Management function 306 to verify if valid user consent has been granted for the requested category of network data. In this regard, the Consent Management Function 306 is configured to check a consent database for determining whether consent exists for the Al service provider 302 to access the network data. The consent database stores the access permissions mapped to a plurality of data categories of the network data, as well as purpose-based or scope-specific policy attributes.. At step 3, the Consent Management 306 performs a granular verification of consent across the user base potentially contributing data to the requested dataset. This consent evaluation may include checking whether users have al lowed data use for Al training, research, commercial modelling, etc., and may leverage historical consent logs or interact with user devices 102 to fetch updated opt-in status. The consent evaluation may also consider policy templates, real-time opt-in status, or user-specific conditions. At step 4, the Consent Management 306 returns the result of the consent verification process to the Data Marketplace 304. In one embodiment (step 4. a), the consent is granted, the process proceeds with compliant data provisioning. In another embodiment (step 4.b), the consent is denied, in which case the request is rejected and the Al service provider 302 may be notified that access is not permitted, correspondingto the step 13 of denying the request for access when access for at least a portion of the network data is not permitted, based on the one or more access permissions..
[0093] Upon consent approval (step 4. a), the Data Marketplace 304 proceeds to proceeds to generate a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data. At step 5, the Data Marketplace 304 triggers the Privacy Engine 308 to invoke one or more data transformation techniques configured to comply with applicable data protection policies. The one or more data transformation techniques may comprise at least one of: removing direct identifiers, generalizing sensitive attributes, and generating artificial records from the network data, and may be defined based on one or more predefined data protection policies. At step 6, the Privacy Engine 308 interacts with the Anonymization / Synthetic Data Function 310 to process the dataset. This process may involve k-anonymity, 1-diversity, differential privacy, suppression, or generation of synthetic data replicas designed to preserve utility while minimizing re-identification risks. At step 7, the Anonymization / Synthetic Data Function 310 returns the transformed, privacy-compliant dataset to the Privacy Engine 308. The dataset may now be devoid of personal identifiers, aggregated, masked, or replaced with artificial samples, depending on the configured transformation logic. At step 8, the modified version of the network data is routed back to the Data Marketplace 304. Before delivery, the system may optionally trigger additional steps to fulfil service-level and operational transparency requirements.
[0094] At step 9, the Data Marketplace 304 triggers usage reporting events. This may include metadata such as data volume, usage tier (e.g., real-time, batch, historical), geographic scope, and transformation level. These reports are sent to the Audit and Compliance function 314 for tracking usage trends and enforcing auditability. In particular, the Data Marketplace 304 logs the request for access for compliance tracking, including metadata associated with the transformation and access request. At step 10, a billing notification is sent from the Charging Function 312 to the Al service provider 302, which computes corresponding charges for the Al service provider 302 based on usage attributes such as volume, categoiy, and duration. The notification may be structured via a standardized OpenAPI format, indicating consumption parameters and monetization rules (e g., pay-per-byte, tiered access, or subscription models).. At step 11, the Audit and Compliance function 314 logs the transaction details for future accountability. This log may include the transaction ID, consumer identity, consent linkage, data version, anonymization technique, andtimestamp to ensure traceability and retrospective compliance audits, especially under privacy regimes like GDPR. At step 12, the Data Marketplace 304 proceeds to provide the modified version of the network data to the Al service provider 302 over a secured communication channel. The modified data may be encrypted prior to transmission using secure transport mechanisms (e.g., TLS, IPsec), optionally accompanied by metadata describing its permitted usage scope, retention limits, and downstream controls.
[0095] In the alternate flow, at step 13, if access is denied due to lack of consent or revocation of permission, the request is denied and a rejection message may be issued to the Al service provider 302, indicating that the network data cannot be shared due to the unavailability of the requested data under current user privacy conditions.
[0096] Fig, 4 illustrates an exemplary flow chart 400 illustrating method steps for enabling privacy compliant data set service for Al training in communication systems, in accordance with an embodiment of the present disclosure.
[0097] As illustrated in Fig. 4, the method 400 may comprise one or more steps. The method 400 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types
[0098] The order in which the method 400 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.
[0099] At block step 402, the method includes receiving a request for access to network data, from an Artificial Intelligence (Al) service provider. The request for access comprises data selection parameters indicating at least one of: a time range, a location and a data type associated with the network data. The one or more access permissions are defined at a per-category level for a plurality of types of the network data.
[0100] At block step 404, the method includes determining whether access to the network data is permitted based on one or more access permissions. The method of determining whether access to the network data is permitted further comprises checking a consent database for determiningwhether consent exists for the Al service provider 106 (or the Al service provider 302 of Fig. 3) to access the network data, wherein the consent database stores the one or more access permissions for a plurality of categories of the network data. In another embodiment, the method further compri ses denying the request for access when access for at least a portion of the network data is not permitted, based on the one or more access permissions.
[0101] At block step 406, generating a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data. The one or more data transformation techniques comprise at least one of: removing direct identifiers, generalizing sensitive attributes and generating artificial records from the network data. The one or more data transformation techniques are applied based on one or more predefined data protection policies.
[0102] At block step 408, providing the modified version of the network data to the Al service provider 106 over a secured communication channel. The method further comprises encrypting the modified version of the network data prior to providing the modified version to the Al service provider.
[0103] The following paragraphs presents various aspects of the present disclosure:
[0104] 1. In an embodiment, a method for receiving a request for access to network data, from an Artificial Intelligence (Al) service provider. The method comprises determining whether access to the network data is permitted based on one or more access permissions. The method further comprises generating a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data. Furthermore, the method comprises providing the modified version of the network data to the Al service provider over a secured communication channel.
[0105] 2. In an embodiment, the method as described in preceding aspect 1, the one or more data transformation techniques comprise at least one of: removing direct identifiers, generalizing sensitive attributes and generating artificial records from the network data.
[0106] 3. In an embodiment, the method as described in any of preceding aspects 1 or 2, determining whether access to the network data is permitted comprises checking a consent database for determining whether consent exists for the Al service provider to access the network data, wherein the consent database stores the one or more access permissions for a plurality of categories of the network data.
[0107] 4 In an embodiment, the method as described in any of preceding aspects 1 through 3, the request for access comprises data selection parameters indicating at least one of: a time range, a location and a data type associated with the network data
[0108] 5 In an embodiment, the method as described in any of preceding aspects 1 through 4, receiving the request for access further comprising: logging the request for access for compliance tracking.
[0109] 6 In an embodiment, the method as described in any of preceding aspects 1 through 5, denying the request for access when access for at least a portion of the network data is not permitted, based on the one or more access permissions.
[0110] 7 In an embodiment, the method as described in any of preceding aspects 1 through 6, encrypting the modified version of the network data prior to providing the modified version to the Al service provider.
[0111] 8. In an embodiment, the method as described in any of preceding aspects 1 through 7, the one or more access permissions are defined at a per-category level for a plurality of types of the network data.
[0112] 9 In an embodiment, the method as described in any of preceding aspects 1 through 8, the one or more data transformation techniques are applied based on one or more predefined data protection policies.
[0113] 10. In an embodiment, a network system comprises a processor, a plurality of network functions and a memory. The processor in conjunction with the plurality of network functions is configured to receive a request for access to network data, from an Artificial Intelligence (Al) service provider. The processor in conjunction with the plurality of network functions is configured to determine whether access to the network data is permitted based on one or more access permissions. Further, the processor in conjunction with the plurality of network functions is configured to generate a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data. Furthermore, the processor in conjunction with the plurality of network functions is configured to provide the modified version of the network data to the Al service provider over a secured communication channel.
[0114] 11. In an embodiment, the network system as described in preceding aspect 10, wherein to determine whether access to the network data is permitted, the processor in conjunction with theplurality of network functions is configured to check a consent database for determining whether consent exists for the Al service provider to access the network data, wherein the consent database stores the one or more access permissions for a plurality of categories of the network data
[0115] 12 In an embodiment, the network system as described in preceding aspect 10 or 11, the one or more data transformation techniques comprise at least one of: removing direct identifiers, generalizing sensitive attributes and generating artificial records from the network data.
[0116] 13. In an embodiment, the network system as described in any of preceding aspects 10 through 12, wherein the request for access comprises data selection parameters indicating at least one of: a time range, a location and a data type associated with the network data.
[0117] 14. In an embodiment, the network system as described in any of preceding aspects 10 through 13, wherein to receive the request for access, the processor is configured to log the request for access for compliance tracking.
[0118] 15. In an embodiment, the network system as described in any of preceding aspects 10 through 14, wherein to determine, the processor in conjunction with the plurality of network functions is configured to deny the request for access when access for at least a portion of the network data is not permitted, based on the one or more access permissions.
[0119] 16. In an embodiment, the network system as described in any of preceding aspects 10 through 15, wherein to provide, the processor in conjunction with the plurality of network functions is configured to encrypt the modified version of the network data prior to providing the modified version to the Al service provider.
[0120] 17. In an embodiment, the network system as described in any of preceding aspects 10 through 16, wherein the one or more access permissions are defined at a per-category level for a plurality of types of the network data.
[0121] 18. In an embodiment, the network system as described in any of preceding aspects 10 through 17, wherein the one or more data transformation techniques are applied based on one or more predefined data protection policies.
[0122] 19. In an embodiment, a non-transitory computer readable medium for enabling sensing services in a wireless communication system is disclosed in an aspect. The non-transitory computer readable medium including instructions stored thereon that when processed by at least one processor, cause a computing system to perform operations comprising receiving a request for access to network data, from an Artificial Intelligence (Al) service provider. The operationscomprises determining whether access to the network data is permitted based on one or more access permissions. Further, the operations comprises generating a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data. Furthermore, the operations comprises providing the modified version of the network data to the Al service provider over a secured communication channel.
[0123] 20. In an embodiment, the non-transitory computer readable medium as described in preceding aspect 19, the operations further comprising determining whether access to the network data is permitted comprises checking a consent database for determining whether consent exists for the Al service provider to access the network data, wherein the consent database stores the one or more access permissions for a plurality of categories of the network data.
[0124] 21. In an embodiment, the non-transitory computer readable medium as described in preceding aspect 19 or 20, the operations further comprising receiving the request for access further comprising: logging the request for access for compliance tracking.
[0125] 22. In an embodiment, the non-transitory computer readable medium as described in any of preceding aspects 19 through 21, the operations further comprising denying the request for access when access for at least a portion of the network data is not permitted, based on the one or more access permissions.
[0126] 23. In an embodiment, the non-transitory computer readable medium as described in any of preceding aspects 19 through 22, the operations further comprising encrypting the modified version of the network data prior to providing the modified version to the Al service provider.
Claims
WE CLAIM:
1. A method comprising:receiving a request for access to network data, from an Artificial Intelligence (Al) service provider;determining whether access to the network data is permitted based on one or more access permissions;generating a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data; and providing the modified version of the network data to the Al service provider over a secured communication channel.
2. The method of claim 1, wherein the one or more data transformation techniques comprise at least one of: removing direct identifiers, generalizing sensitive attributes and generating artificial records from the network data.
3. The method of claim 1, wherein determining whether access to the network data is permitted comprises checking a consent database for determining whether consent exists for the Al service provider to access the network data, wherein the consent database stores the one or more access permissions for a plurality of categories of the network data.
4. The method of claim 1, wherein the request for access comprises data selection parameters indicating at least one of: a time range, a location and a data type associated with the network data.
5. The method of claim 1, wherein receiving the request for access further comprising: logging the request for access for compliance tracking.
6. The method of claim 1, wherein the determining further comprising denying the request for access when access for at least a portion of the network data is not permitted, based on the one or more access permissions.
7. The method of claim 1, wherein the providing further comprising encrypting the modified version of the network data prior to providing the modified version to the Al service provider.
8. The method of claim 1, wherein the one or more access permissions are defined at a per-category level for a plurality of types of the network data.
9. The method of claim 1, wherein the one or more data transformation techniques are applied based on one or more predefined data protection policies.
10. A network system comprises:a processor;a plurality of network functions; anda memory, wherein the processor in conjunction with the plurality of network functions is configured to:receive a request for access to network data, from an Artificial Intelligence (Al) service provider;determine whether access to the network data is permitted based on one or more access permissions;generate a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data; andprovide the modified version of the network data to the Al service provider over a secured communication channel.
11. The network system of claim 10, wherein the one or more data transformation techniques comprise at least one of: removing direct identifiers, generalizing sensitive attributes and generating artificial records from the network data.
12. The network system of claim 10, wherein to determine whether access to the network data is permitted, the processor in conjunction with the plurality of network functions is configured to check a consent database for determining whether consent exists for the Al service provider toaccess the network data, wherein the consent database stores the one or more access permissions for a plurality of categories of the network data.
13. The network system of claim 10, wherein the request for access comprises data selection parameters indicating at least one of: a time range, a location and a data type associated with the network data.
14. The network system of claim 10, wherein to receive the request for access, the processor is configured to log the request for access for compliance tracking.
15. The network system of claim 10, wherein to determine, the processor in conjunction with the plurality of network functions is configured to deny the request for access when access for at least a portion of the network data is not permitted, based on the one or more access permissions.
16. The network system of claim 10, wherein to provide, the processor in conjunction with the plurality of network functions is configured to encrypt the modified version of the network data prior to providing the modified version to the Al service provider.
17. The network system of claim 10, wherein the one or more access permissions are defined at a per-category level for a plurality of types of the network data.
18. The network system of claim 10, wherein the one or more data transformation techniques are applied based on one or more predefined data protection policies.
19. A non-transitory computer readable medium including instructions for performing operations comprising:receiving a request for access to network data, from an Artificial Intelligence (Al) service provider;determining whether access to the network data is permitted based on one or more access permissions;generating a modified version of the network data, in response to determining that the access is permitted, by applying one or more data transformation techniques to the network data; and providing the modified version of the network data to the Al service provider over a secured communication channel.
20. The non-transitory computer readable medium as claimed in claim 19, wherein determining whether access to the network data is permitted comprises checking a consent database for determining whether consent exists for the Al service provider to access the network data, wherein the consent database stores the one or more access permissions for a plurality of categories of the network data.
21. The non-transitory computer readable medium as claimed in claim 19, wherein receiving the request for access further comprising: logging the request for access for compliance tracking.
22. The non-transitory computer readable medium as claimed in claim 19, wherein the determining further comprising denying the request for access when access for at least a portion of the network data is not permitted, based on the one or more access permissions.
23. The non-transitory computer readable medium as claimed in claim 19, wherein the providing further comprising encrypting the modified version of the network data prior to providing the modified version to the Al service provider.
