Granular user consent and its enforcement

Abstract

A first network node may transmit, to a second network node, first information associated with granular user consent control. The first information may be further associated with a data processing task and a UE. The second network node may receive, from the first network node or the UE, second information associated with the granular user consent control. The second information may be further associated with the data processing task and the UE. The second network node may identify a user consent result associated with the data processing task and a user of the UE based on the granular user consent control. The user consent result may be further based on the first information or the second information. The second network node may transmit, to the first network node, the user consent result. Thereafter, the first network node may handle the data processing task based on the user consent result.

Description

[Technical Field]

[0001] This patent application claims the benefit and priority of U.S. Provisional Application No. 63 / 267,387 entitled “GRANULAR USER CONSENT AND ITS ENFORCEMENT”, filed January 31, 2022, and U.S. Patent Application No. 18 / 161,507 entitled “GRANULAR USER CONSENT AND ITS ENFORCEMENT”, filed January 30, 2023, the entire contents of which are expressly incorporated herein by reference.

[0002] In general, this case concerns communication systems, and more specifically, user consent to control and implementation within communication systems. [Previous Technology]

[0003] Wireless communication systems are widely deployed to provide various telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiplexing access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiplexing access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] These multiplexing access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMBE) issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with Enhanced Mobile Broadband (eMBB), Massive Machine-Type Communications (mMTC), and Ultra-Reliable Low-Latency Communications (URLLC). Some forms of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiplexing access technologies and telecommunications standards that employ these technologies. There is also a need to improve user control over data sharing with the network. [Summary of the Invention]

[0005] The following presents a brief overview of one or more patterns to provide a basic understanding of such patterns. This overview is not a broad generalization of all anticipated patterns, nor is it intended to identify key or important factors of all patterns, nor to describe the scope of any or all patterns. The sole purpose of this overview is to present some concepts of one or more patterns in a simplified form as an introduction to the more detailed description that follows.

[0006] In one embodiment of the present invention, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a first network node. The apparatus may transmit first information associated with nuanced user consent control to a second network node. The first information may also be associated with a data processing task and a user equipment (UE). The apparatus may receive user consent results associated with the user of the data processing task and the UE from the second network node based on the nuanced user consent control. The apparatus may process the data processing task based on the user consent results.

[0007] In one embodiment of this invention, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a second network node. The apparatus may receive first information associated with nuanced user consent control from a first network node. The first information may also be associated with a data processing task and a UE. The apparatus may receive second information associated with nuanced user consent control from either the first network node or the UE. The second information may also be associated with a data processing task and the UE. The apparatus may identify a user consent result associated with a user of the data processing task and the UE based on the nuanced user consent control. The user consent result may also be based on either the first information or the second information. The apparatus may transmit the user consent result to either the first network node or the UE.

[0008] To achieve the foregoing and related objectives, the one or more forms include features fully described below and specifically pointed out in the claims. The following description and figures illustrate certain illustrative features of the one or more forms in detail. However, these features only indicate a few of the various ways in which the principles of the various forms can be employed, and this description is intended to include all such forms and their equivalent transformations.

Implementation Method

[0028] The specific embodiments described below with reference to the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configuration in which the concepts described herein can be practiced. These specific embodiments include detailed information to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without such detailed information. In some instances, well-known structures and elements are illustrated in block diagram form to avoid confusion with these concepts.

[0029] Several forms of telecommunications systems will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in the following specific embodiments and illustrated in the accompanying drawings via various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] For example, an element, any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, individual hardware circuits, and other suitable hardware configured to perform the various functions described throughout this document. One or more processors in a processing system can execute software. Software should be interpreted broadly as meaning instructions, instruction sets, code, code fragments, code, program, subprogram, software component, application, software application, software suite, convention, sub-convention, object, executable program, executable thread, program, function, etc., regardless of whether it is called software, firmware, middleware, microcode, hardware description language, or other terms.

[0031] Therefore, in one or more exemplary embodiments, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes computer storage media. Storage media can be any available medium accessible by a computer. By way of example, and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electronically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of various types of computer-readable media, or any other medium that can be used to store computer-executable code having a computer-accessible instruction or data structure.

[0032] Although various forms and implementations are described in this document through the illustration of a few examples, those skilled in the art will understand that other implementations and use cases can emerge in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, various implementations and / or uses can emerge by integrating chip-level implementations with other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, devices with artificial intelligence (AI) capabilities, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applications of the described innovations can emerge. The range of implementations can extend from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more forms of the described innovations. In some practical settings, devices incorporating the described forms and features may also include additional elements and features to implement and practice the claimed and described forms. For example, the transmission and reception of wireless signals require multiple elements (e.g., hardware elements including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) for analog and digital purposes. It is intended that the innovations described herein be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., with different sizes, shapes, and compositions.

[0033] As data processing tasks (such as data collection and other use cases) are performed at an increasing frequency, technologies for managing how wireless communication networks collect and process user-related data are likely desirable. Specifically, implementing restrictions on data collection and / or processing based on user consent or the lack thereof may be appropriate or desirable. In one or more instances, a first network node (e.g., a subscription entity / data collection request entity) may transmit first information associated with granular user consent control (i.e., user consent control under various granularities for different users / services / use cases, etc.) to a second network node (e.g., a UDM), and the second network node may receive this first information from the first network node. The first information may also be associated with the data processing task and the UE. The second network node may receive second information associated with the granular user consent control from the first network node or the UE. The second information may also be associated with the data processing task and the UE. The second network node may identify the user consent outcome (e.g., whether the user consents to data collection) associated with the data processing task and the user based on the UE's user's granular user consent control for one or more specific services. User consent can be based on either the first or second information. The second network node can transmit the user consent result to the first network node, and the first network node can receive the user consent result from the second network node. Subsequently, the first network node can process data processing tasks based on the user consent result. Accordingly, restrictions on data collection or processing tasks based on user consent can be implemented and enforced with finer granularity, providing users with greater flexibility in controlling data collection or processing tasks.

[0034] Figure 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0035] Base station 102 configured for 4G LTE (collectively referred to as Evolutionary Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Layer (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), user and device tracking, RAN Information Management (RIM), paging, location, and warning message delivery. Base stations 102 can communicate directly or indirectly (e.g., via EPC 160 or core network 190) to each other via a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 can be wired or wireless.

[0036] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network including both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network may also include a Home Evolutionary Node B (eNB) (HeNB) that can provide services to a restricted group called a Closed User Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be via one or more carriers. Base station 102 / UE 104 can use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth per carrier allocated in carrier aggregation for transmission in each direction. Carriers can be adjacent to each other or not. Carrier allocation can be asymmetrical for DL ​​and UL (e.g., more or fewer carriers can be allocated to DL than to UL). Component carriers can include primary component carriers and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell), and the secondary component carriers can be referred to as secondary cells (SCells).

[0037] Some UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. D2D communication links 158 may use DL / UL WWAN spectrum. D2D communication links 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink explore channel (PSDCH), physical sidelink shared channel (PSSCH), and physical sidelink control channel (PSCCH). D2D communication may be via various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0038] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, 5 GHz unlicensed spectrum. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform an idle channel assessment (CCA) before communication to determine whether the channel is available.

[0039] The small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as the Wi-Fi AP 150. Employing NR in unlicensed spectrum can improve access network coverage and / or increase access network capacity.

[0040] The electromagnetic spectrum is typically subdivided into categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. Similar naming issues sometimes occur with FR2, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is different from the extremely high frequency (EHF) band (30 GHz – 300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0041] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) frequencies. Recent 5G NR studies have identified the operating bands used for these IF frequencies as the frequency range designation FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 into the IF frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range designations FR2-2 (52.6 GHz – 71 GHz), FR4 (71 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0042] Taking into account the above-described conditions, unless otherwise specifically stated, it should be understood that the terms "sub-6 GHz" etc., as used herein, can broadly refer to frequencies that are less than 6 GHz, within FR1, or can include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that the terms "millimeter wave" etc., as used herein, can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0043] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, g node B (gNB), or another type of base station. Some base stations (e.g., gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-mmW frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Both base station 180 and UE 104 may include multiple antennas (e.g., antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0044] Base station 180 may transmit beamformed signals to UE 104 in one or more transmission directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more reception directions 182''. UE 104 may also transmit beamformed signals to base station 180 in one or more transmission directions. Base station 180 may receive beamformed signals from UE 104 in one or more reception directions. Base station 180 / UE 104 may perform beam training to determine the optimal reception and transmission directions for each of base station 180 / UE 104. The transmission and reception directions of base station 180 may be the same or different. The transmission and reception directions of UE 104 may be the same or different.

[0045] EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a service gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172. MME 162 can communicate with the Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted via service gateway 166, which is itself connected to PDN gateway 172. PDN gateway 172 provides UE IP address allocation and other functions. PDN gateway 172 and BM-SC 170 are connected to IP service 176. IP service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 can provide functions for MBMS user service provisioning and delivery. BM-SC 170 can serve as an entry point for content provider MBMS transmission, can be used to authorize and initiate MBMS bearer services within the Public Land Mobile Network (PLMN), and can be used to schedule MBMS transmissions. MBMS gateway 168 can be used to distribute MBMS traffic to base station 102 within a Broadcast-Specific Service Multicast Single Frequency Network (MBSFN) area, and can be responsible for communication period management (start / stop) and collection of eMBMS-related billing information.

[0046] The core network 190 may include Access and Mobility Management Function (AMF) 192, other AMFs 193, Term Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Typically, AMF 192 provides QoS procedures and term management. All user Internet Protocol (IP) packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) service, and / or other IP services.

[0047] The base station may include and / or be referred to as gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver functional unit, basic service set (BSS), extended service set (ESS), transmit receiving point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, SIP phones, laptop devices, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implanted devices, sensors / actuators, displays, or any other similar functional devices. Some UEs (User Equipment) 104 may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). UEs (User Equipment) 104 may also be referred to as stations, mobile stations, user stations, mobile units, user cells, radio units, remote units, mobile devices, radio devices, wireless communication devices, remote devices, mobile user stations, access terminals, mobile terminals, radio terminals, remote terminals, handheld devices, user agents, mobile service clients, clients, or any other suitable term. In some scenarios, the term UE may also be applied to one or more accompanying devices in a device cluster deployment. These devices may share network access and / or access the network individually.

[0048] Referring again to FIG1, in some configurations, the first network node 191 (e.g., Operation, Administration and Maintenance (OAM), RAN, or Network Data Analysis Function (NWDAF)) may include a user consent element 198, which may be configured to transmit first information associated with granular user consent control to the second network node. The first information may also be associated with a data processing task and the UE. The user consent element 198 may be configured to receive, based on the granular user consent control, a user consent result associated with the user of the data processing task and the UE from the second network node. The user consent element 198 may be configured to process the data processing task based on the user consent result. In some configurations, the second network node 191' (e.g., UDM) may include a user consent element 199, which may be configured to receive, based on the granular user consent control, first information associated with granular user consent control from the first network node. The first information may also be associated with a data processing task and the UE. User consent element 199 can be configured to receive second information associated with granular user consent control from a first network node or UE. The second information can also be associated with a data processing task and the UE. User consent element 199 can be configured to identify a user consent result associated with a user of the data processing task and the UE based on the granular user consent control. The user consent result can also be based on either the first or second information. User consent element 199 can be configured to transmit the user consent result to the first network node or the UE. In different configurations, user consent element 198 and / or user consent element 199 can be implemented in software, hardware, or a combination thereof. Although the following description may focus on 5G NR, the concepts described herein can be applied to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0049] Figure 2A is Figure 200, illustrating an example of the first sub-frame within the 5G NR frame structure. Figure 2B is Figure 230, illustrating an example of the DL channel within the 5G NR sub-frame. Figure 2C is Figure 250, illustrating an example of the second sub-frame within the 5G NR frame structure. Figure 2D is Figure 280, illustrating an example of the UL channel within the 5G NR sub-frame. The 5G NR frame structure can be Frequency Division Duplex (FDD) or Time Division Duplex (TDD). In FDD, a specific set of subcarriers (carrier system bandwidth) and sub-frames within that set are dedicated to either DL or UL. In TDD, a specific set of subcarriers (carrier system bandwidth) and sub-frames within that set are dedicated to both DL and UL. In the examples provided in Figures 2A and 2C, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format via a received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the above description also applies to 5G NR frame structures as TDD.

[0050] Figures 2A-2D illustrate the frame structure, and various embodiments of the present invention can be applied to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 sub-frames (1 ms) of equal size. Each sub-frame may include one or more time slots. Sub-frames may also include mini-time slots, which may include 7, 4, or 2 symbols. Depending on whether the cyclic prefix (CP) is normal or extended, each time slot may include 14 or 12 symbols. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. The symbols on the DL can be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high-volume scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on CP and the numerical scheme. The numerical scheme defines the subcarrier spacing (SCS) (see Table 1) and, in effect, defines the symbol length / duration, which is equal to 1 / SCS. µ SCS Cyclic prefixes 0 15 normal 1 30 normal 2 60 Normal, expansion 3 120 normal 4 240 normal Table 1: Numerical Scheme, SCS, and CP

[0051] For a normal CP (14 symbols / slot), different numerical schemes µ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, numerical scheme 2 allows 4 slots per subframe. Accordingly, for the normal CP and numerical scheme µ, there are 14 symbols / slot and 2 µ slots / subframe. The subcarrier spacing can be equal to 2 µ * 15 kHz, where µ is numerical scheme 0 to 4. Therefore, numerical scheme µ=0 has a subcarrier spacing of 15 kHz, and numerical scheme µ=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D provide examples of a normal CP with 14 symbols per slot and a numerical scheme µ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 µs. Within a frame set, there may be one or more different bandwidth portions (BWPs) that have undergone frequency division multiplexing (see Figure 2B). Each BWP may have a specific numerical scheme and CP (normal or extended).

[0052] The resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0053] As shown in Figure 2A, some REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are also possible), and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0054] Figure 2B illustrates examples of various DL channels within a sub-frame of a frame. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbols of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a shared search space, a UE-specific search space) during PDCCH monitoring on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies across the channel bandwidth. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific sub-frame of the frame. The PSS is used by the UE 104 to determine sub-frame / symbol timing and physical layer identity. The Secondary Synchronization Signal (PSS) can be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identity Group Number and the radio frame timing. Based on the Physical Layer Identity and Physical Layer Cell Identity Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH) carrying the Primary Information Block (MIB) can be logically classified with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS Block (SSB)). The MIB provides multiple RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data and broadcast system information not transmitted via the PBCH, such as the System Information Block (SIB) and paging messages.

[0055] As shown in Figure 2C, some REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are also possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE can transmit a Sound Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to achieve frequency-related scheduling on the UL.

[0056] Figure 2D illustrates examples of various UL channels within a sub-frame of a frame. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCIs.

[0057] Figure 3 is a block diagram of communication between base station 310 and UE 350 in the access network. In DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reports; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and delivery support functions; RLC layer functions associated with transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs and TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0058] The transmit (TX) processor 316 and the receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transmit channel, forward error correction (FEC) decoding / decoding of the transmit channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal cluster based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be separated into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot frequency) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine the decoding and modulation schemes, as well as those used for spatial processing. Channel estimates can be derived from reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate a radio frequency (RF) carrier using the corresponding spatial stream for transmission.

[0059] At UE 350, each receiver 354RX receives a signal via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, these multiple spatial streams can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal cluster point transmitted by base station 310. These soft decisions can be based on channel estimates calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

[0060] The controller / processor 359 may be associated with memory 360 storing code and data. Memory 360 may be referred to as computer-readable media. In UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transmission and logic channels to recover IP packets from EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0061] Similar to the functions described in the DL transmission performed in conjunction with the base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transmission channels, multiplexing of MAC SDUs on TBs, demultiplexing of MAC SDUs and TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0062] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0063] UL transmissions are processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0064] The controller / processor 375 may be associated with memory 376 storing code and data. Memory 376 may be referred to as computer-readable media. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logic channels to recover IP packets from the UE 350. IP packets from the controller / processor 375 can be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0065] Network nodes can be implemented as aggregated base stations, distributed base stations, integrated access and backhaul (IAB) nodes, relay nodes, sidelink nodes, etc. Network entities can be implemented in aggregated or monolithic base station architectures, or alternatively in distributed base station architectures, and can include one or more of the following: central unit (CU), distributed unit (DU), radio unit (RU), near real-time (near RT) RAN intelligent controller (RIC), or non-real-time (non-RT) RIC.

[0066] In this document, data processing can mean any operation or set of operations performed on personal data or sets of personal data, whether or not by automated means, such as collecting, recording, organizing, structuring, storing, adapting or altering, obtaining, consulting, using, disclosing by transmission, disseminating, or otherwise providing, aligning or combining, restricting, erasing or destroying.

[0067] As data processing tasks (such as data collection and other use cases) are performed at an increasing frequency, technologies for managing how wireless communication networks collect and process user-related data are likely to be desirable. Specifically, it may be appropriate or desirable to implement restrictions on data collection and / or processing based on user consent or the lack thereof. In other words, data collection and / or processing may be performed with user consent and may not be performed without user consent. Use cases in which such restrictions can be implemented may include, for example, data collection associated with Minimum Driven Testing (MDT) or Self-Organizing Network (SON) frameworks, data collection associated with Quality of Experience (QoE), Artificial Intelligence (AI) / Machine Learning (ML) training, AI / ML inference, data collection for AI / ML use cases that do not use MDT frameworks, or RF sensing, etc.

[0068] In one or more configurations, data collection for the MDT may be based on user consent. In one or more configurations, the collection and / or processing of user personal data for a specific purpose at the Network Data Analysis Function (NWDAF) may be performed based on user consent. In one or more configurations, user consent parameters (e.g., parameters defining user consent for a specific data collection or processing activity) may become effective after user consent is provided and may remain effective until withdrawn by the user. In one or more configurations, user consent may be provided, modified, or withdrawn out of band (e.g., at a point of sale or via a customer service channel (e.g., a portal)).

[0069] In one or more configurations, user consent parameters can be stored and maintained at the UDM. Specifically, user consent parameters may include one or more of the following: UE identifier (ID), data processor ID, purpose of data processing, or user consent result. Among these parameters, in one or more instances, the UE ID may be a Subscription Permanent Identifier (SUPI). Furthermore, the data processor ID may correspond to the data processor that processes data for the UE, and may be an Application Function (AF) ID or a more general ID (e.g., a "Third Party" indicator or an "All" indicator). Additionally, the purpose of data processing may be combined with a service operation name and / or other inputs. Furthermore, a positive user consent result may instruct the user to consent to the corresponding data processor processing data according to the corresponding data processing purpose.

[0070] In one or more configurations, user consent to data collection and / or processing can be provided and implemented with more granular detail than described above. In one or more configurations, new user consent can be provided and implemented on a per-use-case or per-service basis. In one or more configurations, procedures for implementing updates to existing user consent can be provided. In one or more configurations, for a given user, the UDM can maintain user consent information on a per-service basis. In one or more configurations, the UDM can maintain user consent information based on granular detail. In one or more configurations, for a device shared by multiple users, the UDM can maintain user consent information based on user ID. In one or more configurations, the UDM can store user consent on a per-service basis. Depending on the use case, additional parameters associated with user consent can also be stored at the UDM.

[0071] Figure 4 is a diagram 400 illustrating exemplary user consent information stored at a UDM according to one or more formats. As illustrated in Figure 4, user consent information 402 may include a set of user consent parameters stored for each combination of service 404 (which may be identified by a service ID) and user 406 (which may be identified by a user ID). For each combination of service 404 and user 406, the exemplary set of user consent parameters may include one or more of the following: UE ID, data requester ID (if applicable to the service), purpose of data request (if applicable to the service), data processor ID (e.g., data processor ID, ML trainer ID, or inference entity ID) (if applicable to the service), purpose of data processing, action to be taken upon revocation of user consent (e.g., erasing data, modifying data collection and / or processing, or stopping data collection and / or processing), or user consent information (e.g., one or more validity conditions associated with user consent, wherein user consent is invalid / lapsed if the validity conditions are not met). In one or more configurations, validity conditions may be associated with different nuances for different services. Specifically, validity conditions can correspond to, for example, a validity area (e.g., a Public Land Mobile Network (PLMN) coverage area, a RAT coverage area, a Radio Network Controller (RNC) coverage area, a destination area (e.g., a geographic area or the geopolitical name of an area; a PLMN can transform and define a destination area as the identity of one or more radio cells or tracking areas, etc.), a validity period (e.g., the period of the validity period, the start and end times of the validity period, etc.), a validity slice (e.g., a slice on which the user consents to be valid), one or more carrier frequencies (e.g., carrier frequencies on which the user consents to be valid), a UE power state (e.g., a threshold of remaining UE power levels above which the user consents to be valid), or a UE computed power state (e.g., a threshold of available UE computed power levels above which the user consents to be valid), and so on. Accordingly, in one or more configurations, the user consent result, which can be affirmative (i.e., allowing the task based on user consent) or negative (i.e., disallowing the task based on the absence of user consent), can be identified based on stored user consent parameters, depending on the conditions or factors associated with the attempted data collection and processing task.

[0072] Figure 5 is a flowchart 500 illustrating a method for handling user consent at a subscription entity according to one or more states. In some instances, a subscription entity may refer to an entity that can initiate data collection or processing tasks at the UE. For example, for MDT data collection, the subscription entity may be OAM. For ML-related data collection or processing tasks, the subscription entity may be OAM or RAN. In other instances, a subscription entity may refer to an entity that can initiate data collection or processing tasks at another network node for a specific user. For example, for federated data analysis or ML-related data collection or processing tasks, the subscription entity may be NWDAF. In other instances, a subscription entity may refer to an entity that can perform data processing tasks related to a specific UE.

[0073] At 502, the subscribing entity may check (e.g., via querying the UDM) the user consent result associated with the data collection or processing task before attempting to initiate the task. The user consent result may be based on one or more of the following: region, PLMN, RAT, RNC, destination region, slice, service, carrier frequency, time, UE power state, available UE computed power, or the UE's user. Accordingly, at 504, the user consent result may be returned from the UDM based on one or more of the above conditions or factors, or similar conditions or factors. If the user consent result is affirmative (yes), then at 506, the subscribing entity may initiate the data collection or processing task. Alternatively, if the user consent result is negative (no), then at 508, the subscribing entity may not initiate the data collection or processing task because the task is not permitted based on the user consent parameters stored in the UDM.

[0074] After initiating the data collection or processing task at point 506, at point 510, the subscribing entity can identify whether it has received a notification of a change in the user's consent outcome from the UDM. If a notification of a change in the user's consent outcome has been received (yes), and the updated user consent outcome is negative, then at point 512, the subscribing entity can terminate the data collection or processing task. Furthermore, the subscribing entity can release user-specific information. For example, if the user withdraws their consent, the subscribing entity can erase user-specific information (if instructed to do so based on the user's consent outcome). If a notification of a change in the user's consent outcome has not yet been received (no), then at point 514, the subscribing entity can continue the data collection or processing task.

[0075] Figure 6 is a flowchart 600 illustrating an exemplary method of user consent processing at a UDM according to one or more states. At 602, the UDM may store user consent information for different services and corresponding user consent results for any given configuration. At 604, if any conditions or factors that may affect the user consent result (e.g., region, slice, carrier frequency, UE power state, UE compute power state, etc.) have changed since the last user consent result was provided to the subscriber entity, the subscriber entity may notify the UDM. Based on this notification and the user consent information stored at the UDM, the UDM may recalculate (re-identify) the updated user consent result. At 606, the UDM may identify whether the updated user consent result is different from the last user consent result provided to the subscriber entity. If the updated user consent result is different (yes), then at 608, the UDM may notify the subscriber entity of the change in user consent result so that the subscriber entity can take appropriate action. If the updated user consent result is no different from the previous user consent result provided to the subscriber (no), then at 610, UDM may not take any additional action (at least not until UDM is notified of any changes to the conditions or factors that may affect the user consent result).

[0076] Therefore, the network can implement restrictions on data collection or processing tasks based on user consent. In one or more configurations, the operator can be a data controller. In one or more configurations, a data collection request entity can refer to an entity that can request the UE to collect data. In some instances, a data collection request entity can be identified by an AF ID or a more general ID (e.g., a "third party" indicator or an "all" indicator). In one or more configurations, a data processor can refer to an entity that can process data from the UE. In some instances, a data processor can be identified by an AF ID or a more general ID (e.g., a "third party" indicator or an "all" indicator). In one or more instances, a user can update their user consent information out of band (e.g., via a customer service channel, such as an operator portal).

[0077] Accordingly, the subscription entity may be a data processor and / or a data collection request entity. In one or more configurations, the UDM may notify the subscription entity of any updates to the user consent outcome based on various conditions or factors. After receiving notification from the UDM regarding changes to the user consent outcome, the subscription entity may modify or terminate active (ongoing) data collection or processing tasks, or may reconfigure the UE to modify the data collection procedure.

[0078] Figure 7 is a diagram illustrating a communication flow 700 for implementing an exemplary method for updating user consent results according to one or more formats. At 708, the subscription entity 704 may check the user consent results associated with a data collection or processing task before attempting to initiate such task. The data collection or processing task may correspond to a service and may be associated with a service ID. At 710, the subscription entity 704 may transmit a request for the user consent results to the UDM 706. The subscription entity 704 may also transmit instructions to the UDM 706 regarding conditions or factors that may affect the user consent results.

[0079] At 712, UDM 706 may calculate (identify) the user consent result for the service ID based on user consent information stored in UDM 706 and other information (e.g., instructions received from subscription entity 704 and / or UE 702). At 714, UDM 706 may transmit the user consent result to subscription entity 704. At 716, if the user consent result is positive, subscription entity 704 may initiate a data collection or processing task. Alternatively, if the user consent result is negative, subscription entity 704 may not initiate a data collection or processing task.

[0080] At 718, where appropriate or suitable, the subscription entity 704 may configure UE 702 to perform data collection or processing tasks. At 720 and / or 724, UE 702 may provide UE-collected input (e.g., UE power status, available UE computing power status, etc.) that may affect the user consent outcome to the subscription entity 704 and / or directly to the UDM 706. If the UE-collected input is provided to the subscription entity 704 by UE 702, the subscription entity 704 may forward the UE-collected input to the UDM 706 at 722. Furthermore, at 722, the subscription entity 704 may provide additional information (e.g., region, slice, carrier frequency, time, etc.) that may affect the user consent outcome to the UDM 706.

[0081] At 726, UDM 706 can recalculate (re-identify) the updated user consent result based on the updated user consent information, the updated input collected by the UE, and the updated input from the subscription entity 704. If the updated user consent result differs from the user consent result 714 provided to the subscription entity 704, UDM 706 can notify the subscription entity 704 of the change in the user consent result. Specifically, if the user consent result has changed from affirmative to negative, UDM 706 can transmit a termination signal to the subscription entity 704 to prompt the subscription entity 704 to terminate the data collection or processing task.

[0082] At 728, if the updated user consent result differs from the user consent result 714 provided to the subscription entity 704, then UDM 706 may notify the subscription entity 704 of the change in user consent result so that the subscription entity 704 can take appropriate action. In some configurations, the subscription entity 704 may choose not to terminate the data collection or processing task even if the user consent result has become negative. Alternatively, the subscription entity 704 may modify the tracking communication period associated with the data collection or processing task based on the updated user consent result.

[0083] Figure 8 is a diagram illustrating a communication flow 800 for implementing an exemplary method for updating user consent results according to one or more states. Specifically, at 810, UDM 808 has identified that the user consent result has become negative based on the latest inputs (e.g., 720, 722, 724) indicating updated conditions or factors that may affect the user consent result.

[0084] In one or more configurations, for modifications to the tracking communication period based on updated user consent results, at 812, UDM 808 may notify AMF 806 of the update to the user consent results based on the updated user consent results. At 814, AMF 806 may transmit a first indication of the tracking communication period modification to base station 804 based on the updated user consent results. At 816, base station 804 may transmit a second indication of the tracking communication period modification to UE 802 based on the updated user consent results. Accordingly, the tracking communication period may be modified at UE 802 based on the updated user consent results.

[0085] In one or more configurations, for modifications to the managed tracking communication period based on the updated user consent result, at 818, UDM 808 may transmit an indication of the updated user consent result to AMF 806. At 820, AMF 806 may store information related to the updated user consent result. At 822, AMF 806 may transmit the updated user consent result to base station 804 based on the UE context modification message. At 824, base station 804 may choose to retain, modify, or release the configuration associated with the data collection or processing task based on the information related to the updated user consent result. At 826, base station 804 may transmit a configuration update indicating the updated user consent result to UE 802 (e.g., via RRC signaling).

[0086] In one or more configurations, the UDM 808 may be unaware of the active (ongoing) tracking communication period associated with the data collection or processing task. Accordingly, if the tracking communication period is inactive for the user / UE, excessive unnecessary signaling may be involved. For example, when user consent is updated, the corresponding ongoing tracking communication period for data collection or processing may also be updated. However, for users / UEs whose user consent has been updated, there may often be no ongoing tracking communication period associated with that user / UE. In such scenarios, if the UDM still updates the OAM related to the user consent update, the associated signaling may be considered unnecessary signaling. In one or more other configurations, based on the updated user consent result, the UDM may send the updated user consent result to the UE for potential termination or modification of the data collection or processing task at the UE.

[0087] Figure 9 is a diagram illustrating a communication flow 900 for implementing an exemplary method for updating user consent results according to one or more states. Specifically, at 908, UDM 906 has identified that the user consent result has become negative based on the latest inputs (e.g., 720, 722, 724) indicating updated conditions or factors that may affect the user consent result.

[0088] At 910, UDM 906 can transmit the updated user consent result to UE 902. In one configuration, UDM 906 can transmit the updated user consent result to UE 902 during the registration process (e.g., via a registration acceptance message). In another configuration, UDM 906 can transmit the updated user consent result to UE 902 via a UE parameter update message. In some instances, the message carrying the updated user consent result from UDM 906 can be forwarded by AMF 904 before reaching UE 902.

[0089] At 912, in some configurations, UE 902 may modify measurements associated with data collection or processing tasks (e.g., modify measurement objects in reports) or other procedures based on updated user consent result information received from UDM 906.

[0090] Accordingly, based on the process illustrated in Figure 9, modifications to the tracking communication period (e.g., termination and re-initialization) after the user agrees to the updated result can be avoided. Therefore, any unnecessary signaling can also be avoided.

[0091] If UE 902 terminates measurements and reports for an active (ongoing) tracking communication period (e.g., associated with data collection or processing tasks) based on updated user consent, then for managed measurements and reports, UE 902 can indicate the termination of the tracking communication period to the base station via UE Assisted Information (UAI) messages. For signaling-based measurements and reports, UE 902 can use NAS signaling to indicate the termination of the tracking communication period to the network.

[0092] Figure 10 is a diagram illustrating a communication flow 1000 of an exemplary wireless communication method. At 1008, a first network node 1004 (e.g., a subscription entity) may transmit first information associated with granular user consent control to a second network node 1006 (e.g., a UDM). The first information may also be associated with a data processing task and the UE 1002. In one configuration, the transmission of the first information 1008 to the second network node 1006 may correspond to a request for user consent results.

[0093] The first network node 1004 can receive the second information from UE 1002 at 1010a, and can forward the second information from UE 1002 to the second network node 1006 at 1010b. The second information can also be associated with data processing tasks and UE 1002.

[0094] Alternatively or alternatively, at 1012, the second network node 1006 can receive second information associated with the nuanced user consent control from the UE 1002.

[0095] At 1014, the second network node 1006 can identify the user consent result associated with the data processing task and the user of UE 1002 based on granular user consent control. The user consent result can also be based on first information and / or second information.

[0096] At 1016, the second network node 1006 may transmit user consent results associated with the data processing task and the user of UE 1002 to the first network node 1004 based on granular user consent control, and the first network node 1004 may receive the user consent results from the second network node 1006.

[0097] Alternatively or alternatively, at 1018, the second network node 1006 may transmit the user consent result to the UE 1002.

[0098] At 1020, the first network node 1004 can process the data processing task based on the user's consent result. At 1020a, the first network node 1004 can start, modify, or terminate the data processing task based on the user's consent result 1016. At 1020b, the first network node 1004 can transmit the configuration associated with the data processing task to the UE 1002 based on the user's consent result 1016 / 1018.

[0099] In one configuration, granular user consent control may be based on at least one of the following: region, PLMN, RAT, RNC, destination region, slice, service associated with data processing task, carrier frequency, time, UE power state, available UE computed power, or the user of the UE. In one configuration, the user consent result may also be based on second information or first information from the UE. The first information 1008 may indicate at least one of region, PLMN, RAT, RNC, destination region, or carrier frequency. The second information 1010a / 1010b / 1012 may include the power state of UE 1002 or an indication of the available UE 1002 computed power.

[0100] In one configuration, the data processing task can be a data collection task based on a service associated with a service ID. In one configuration, the first network node 1004 can be a subscription entity associated with the data processing task, and can be a data collection request entity associated with the data processing task or a data processor associated with the data processing task. In one configuration, the first network node 1004 can correspond to at least one of OAM, RAN, or NWDAF. The second network node 1006 can correspond to UDM. In one configuration, the second network node 1006 can store data associated with nuanced user consent controls.

[0101] At 1022, the second network node 1006 can identify the updated user consent result associated with the data processing task and the user of UE 1002 based on granular user consent control. The updated user consent result can also be based on updated first information or updated second information.

[0102] At 1024, the second network node 1006 may transmit an updated user consent result associated with the data processing task and the user of UE 1002 to the first network node 1004 based on the nuanced user consent control, and the first network node 1004 may receive the updated user consent result from the second network node 1006.

[0103] Alternatively or concurrently, at 1026, the second network node 1006 may transmit the updated user consent result to the UE 1002. In one configuration, the updated user consent result 1026 may be transmitted to the UE 1002 without tracking communication period modifications. In one configuration, the user consent result 1026 may be transmitted to the UE 1002 via at least one third network node. In one configuration, the at least one third network node may correspond to an AMF or a base station.

[0104] At 1028, the first network node 1004 can process data processing tasks based on the updated user consent result 1024.

[0105] FIG11 is a flowchart 1100 of a wireless communication method. This method can be performed by a first network node (e.g., first network node 191; subscription entity 704; first network node 1004; device 1502). At 1102, the first network node can transmit first information associated with nuanced user consent control to a second network node. The first information can also be associated with data processing tasks and the UE. For example, 1102 can be performed by the user consent element 1540 in FIG15. Referring to FIG10, at 1008, the first network node 1004 can transmit the first information associated with nuanced user consent control to the second network node 1006.

[0106] At 1104, the first network node can receive user consent results associated with the data processing task and the user of the UE from the second network node based on granular user consent control. For example, 1104 can be performed by the user consent element 1540 in FIG15. Referring to FIG10, at 1016, the first network node 1004 can receive user consent results associated with the data processing task and the user of the UE 1002 from the second network node 1006 based on granular user consent control.

[0107] At 1106, the first network node can process the data processing task based on the user's consent result. For example, 1106 can be performed by the user consent element 1540 in FIG15. Referring to FIG10, at 1020, the first network node 1004 can process the data processing task based on the user's consent result.

[0108] FIG12 is a flowchart 1200 of a wireless communication method. This method can be performed by a first network node (e.g., first network node 191; subscription entity 704; first network node 1004; device 1502). At 1202, the first network node can transmit first information associated with nuanced user consent control to a second network node. The first information can also be associated with data processing tasks and the UE. For example, 1202 can be performed by the user consent element 1540 in FIG15. Referring to FIG10, at 1008, the first network node 1004 can transmit first information associated with nuanced user consent control to the second network node 1006.

[0109] At 1204, the first network node can receive user consent results associated with the data processing task and the user of the UE from the second network node based on granular user consent control. For example, 1204 can be performed by the user consent element 1540 in FIG15. Referring to FIG10, at 1016, the first network node 1004 can receive user consent results associated with the data processing task and the user of the UE 1002 from the second network node 1006 based on granular user consent control.

[0110] At 1206, the first network node can process the data processing task based on the user's consent result. For example, 1206 can be performed by the user consent element 1540 in FIG15. Referring to FIG10, at 1020, the first network node 1004 can process the data processing task based on the user's consent result.

[0111] In one configuration, the granular user consent control may be based on at least one of the following: region, PLMN, RAT, RNC, destination region, slice, service associated with data processing task, carrier frequency, time, UE power state, available UE computed power, or UE user.

[0112] In one configuration, referring to FIG10, the user consent result may also be based on second information or first information from the UE. The first information 1008 may indicate at least one of the following: region, PLMN, RAT, RNC, destination region, or carrier frequency. The second information 1010a / 1010b / 1012 may include the UE power status or an indication of the power calculated by the available UE.

[0113] In one configuration, in order to process a data processing task based on user consent, at 1206a, the first network node can start, modify, or terminate the data processing task based on the user consent result. For example, 1206a can be performed by the user consent element 1540 in FIG15. Referring to FIG10, at 1020a, the first network node 1004 can start, modify, or terminate the data processing task based on user consent result 1016.

[0114] In one configuration, in order to process a data processing task based on user consent, at 1206b, the first network node can transmit the configuration associated with the data processing task to the UE based on the user consent result. For example, 1206b can be performed by the user consent element 1540 in FIG15. Referring to FIG10, at 1020b, the first network node 1004 can transmit the configuration associated with the data processing task to the UE 1002 based on user consent results 1016 / 1018.

[0115] In one configuration, a data processing task can be a data collection task based on a service associated with a service ID.

[0116] In one configuration, referring to FIG10, the first network node 1004 may be a subscription entity associated with a data processing task, and the subscription entity may be a data collection request entity associated with a data processing task or a data processor associated with a data processing task.

[0117] In one configuration, referring to Figure 10, the first network node 1004 may correspond to at least one of OAM, RAN, or NWDAF. The second network node 1006 may correspond to UDM.

[0118] In one configuration, at 1208, the first network node can receive an updated user consent result associated with the data processing task and the user of the UE from the second network node based on granular user consent control. For example, 1208 can be performed by the user consent element 1540 in FIG15. Referring to FIG10, at 1024, the first network node 1004 can receive an updated user consent result associated with the data processing task and the user of the UE from the second network node 1006 based on granular user consent control.

[0119] At 1210, the first network node can process the data processing task based on the updated user consent result. For example, 1210 can be performed by the user consent element 1540 in FIG15. Referring to FIG10, at 1028, the first network node 1004 can process the data processing task based on the updated user consent result 1024.

[0120] In one configuration, referring to FIG10, the transmission of first information 1008 to second network node 1006 may correspond to a request for user consent results.

[0121] In one configuration, referring to FIG10, the first network node 1004 can receive second information 1010a from UE 1002 and can forward the second information from UE 1002 to the second network node 1006 1010b.

[0122] Figure 13 is a flowchart 1300 of a wireless communication method. This method can be performed by a second network node (e.g., second network node 191'; UDM 196 / 706 / 808 / 906; second network node 1006; device 1660). At 1302, the second network node can receive first information associated with nuanced user consent control from the first network node. The first information can also be associated with data processing tasks and the UE. For example, 1302 can be performed by the user consent element 1640 in Figure 16. Referring to Figure 10, at 1008, the second network node 1006 can receive first information associated with nuanced user consent control from the first network node 1004.

[0123] At 1304, the second network node can receive second information associated with the nuanced user consent control from the first network node or the UE. The second information can also be associated with data processing tasks and the UE. For example, 1304 can be performed by the user consent element 1640 in FIG16. Referring to FIG10, at 1010b or 1012, the second network node 1006 can receive the second information associated with the nuanced user consent control from the first network node 1004 or the UE 1002.

[0124] At 1306, the second network node can identify the user consent result associated with the data processing task and the user of the UE based on granular user consent control. The user consent result can also be based on first information or second information. For example, 1306 can be performed by the user consent element 1640 in FIG16. Referring to FIG10, at 1014, the second network node 1006 can identify the user consent result associated with the data processing task and the user of UE 1002 based on granular user consent control.

[0125] At 1308, the second network node can transmit the user consent result to the first network node or the UE. For example, 1308 can be performed by the user consent element 1640 in FIG16. Referring to FIG10, at 1016 or 1018, the second network node 1006 can transmit the user consent result to the first network node 1004 or the UE 1002.

[0126] Figure 14 is a flowchart 1400 of a wireless communication method. This method can be performed by a second network node (e.g., second network node 191'; UDM 196 / 706 / 808 / 906; second network node 1006; device 1660). At 1402, the second network node can receive first information associated with nuanced user consent control from the first network node. The first information can also be associated with data processing tasks and the UE. For example, 1402 can be performed by the user consent element 1640 in Figure 16. Referring to Figure 10, at 1008, the second network node 1006 can receive first information associated with nuanced user consent control from the first network node 1004.

[0127] At 1404, the second network node can receive second information associated with the nuanced user consent control from the first network node or the UE. The second information can also be associated with data processing tasks and the UE. For example, 1404 can be performed by the user consent element 1640 in FIG16. Referring to FIG10, at 1010b or 1012, the second network node 1006 can receive the second information associated with the nuanced user consent control from the first network node 1004 or the UE 1002.

[0128] At 1406, the second network node can identify the user consent result associated with the data processing task and the user of the UE based on granular user consent control. The user consent result can also be based on first information or second information. For example, 1406 can be performed by the user consent element 1640 in FIG16. Referring to FIG10, at 1014, the second network node 1006 can identify the user consent result associated with the data processing task and the user of UE 1002 based on granular user consent control.

[0129] At 1408, the second network node can transmit the user consent result to the first network node or the UE. For example, 1408 can be performed by the user consent element 1640 in FIG16. Referring to FIG10, at 1016 or 1018, the second network node 1006 can transmit the user consent result to the first network node 1004 or the UE 1002.

[0130] In one configuration, the granular user consent control may be based on at least one of the following: region, PLMN, RAT, RNC, destination region, slice, service associated with data processing task, carrier frequency, time, UE power state, available UE computed power, or UE user.

[0131] In one configuration, referring to FIG10, the first information 1008 may include at least one of the following: region, PLMN, RAT, RNC, destination region, or carrier frequency. The second information 1010a / 1010b / 1012 may include the UE power status or an indication of the calculated power of the available UE.

[0132] In one configuration, a data processing task can be a data collection task based on a service associated with a service ID.

[0133] In one configuration, referring to FIG10, the first network node 1004 may be a subscription entity associated with a data processing task, and the subscription entity may be a data collection request entity associated with a data processing task or a data processor associated with a data processing task.

[0134] In one configuration, referring to Figure 10, the first network node 1004 may correspond to at least one of OAM, RAN, or NWDAF. The second network node 1006 may correspond to UDM.

[0135] In one configuration, at 1410, the second network node can identify the updated user consent result associated with the data processing task and the user of the UE based on granular user consent control. For example, 1410 can be performed by the user consent element 1640 in FIG16. Referring to FIG10, at 1022, the second network node 1006 can identify the updated user consent result associated with the data processing task and the user of UE 1002 based on granular user consent control.

[0136] At 1412, the second network node can transmit the updated user consent result to the first network node or the UE. For example, 1412 can be performed by the user consent element 1640 in FIG16. Referring to FIG10, at 1024 or 1026, the second network node 1006 can transmit the updated user consent result to the first network node 1004 or the UE 1002.

[0137] In one configuration, referring to FIG10, the updated user consent result 1026 can be transmitted to UE 1002 without tracking communication period modifications.

[0138] In one configuration, referring to FIG10, the user consent result 1026 can be transmitted to UE 1002 via at least one third network node.

[0139] In one configuration, the at least one third network node may correspond to an AMF or a base station.

[0140] In one configuration, referring to FIG10, the second network node 1006 may store data associated with the nuanced user consent control.

[0141] In one configuration, referring to FIG10, the first information 1008 received from the first network node 1004 may correspond to a request for user consent. The user consent result 1016 may be transmitted to the first network node 1004 based on the request for user consent.

[0142] FIG15 is a FIG1500 illustrating an example of the hardware implementation of the illustrated device 1502. The device 1502 may be a first network node, an element of a first network node, or may implement the functions of a first network node. In some embodiments, the device 1502 may include a baseband unit 1504. The baseband unit 1504 may communicate with the UE 104 via a cellular RF transceiver 1522. The baseband unit 1504 may include computer-readable media / memory. The baseband unit 1504 is responsible for general processing, including executing software stored on the computer-readable media / memory. When the software is executed by the baseband unit 1504, it causes the baseband unit 1504 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the baseband unit 1504 when executing the software. The baseband unit 1504 also includes a receiving element 1530, a communication manager 1532, and a transmitting element 1534. The communication manager 1532 includes one or more of the illustrated components. The components within the communication manager 1532 may be stored in computer-readable media / memory and / or configured as hardware within the baseband unit 1504.

[0143] The communication manager 1532 includes a user consent element 1540, which can be configured to: transmit first information associated with granular user consent control to a second network node, for example, as described in conjunction with 1102 in FIG11 and 1202 in FIG12. The user consent element 1540 can be configured to: receive user consent results associated with a data processing task and the user of the UE from the second network node based on the granular user consent control, for example, as described in conjunction with 1104 in FIG11 and 1204 in FIG12. The user consent element 1540 can be configured to: process a data processing task based on the user consent result, for example, as described in conjunction with 1106 in FIG11 and 1206 in FIG12. The user consent element 1540 can be configured to: initiate, modify, or terminate a data processing task based on the user consent result, for example, as described in conjunction with 1206a in FIG12. User consent element 1540 can be configured to: transmit configuration associated with a data processing task to the UE based on the user consent result, for example, as described in conjunction with 1206b of FIG. 12. User consent element 1540 can be configured to: receive an updated user consent result associated with the data processing task and the user of the UE from a second network node based on granular user consent control, for example, as described in conjunction with 1208 of FIG. 12. User consent element 1540 can be configured to: process a data processing task based on the updated user consent result, for example, as described in conjunction with 1210 of FIG. 12.

[0144] The device may include additional elements for each block of the flowcharts in Figures 5, 7, and 10-12 that execute the algorithms. Therefore, each block of the flowcharts in Figures 5, 7, and 10-12 can be executed by elements, and the device may include one or more of such elements. Elements may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0145] As illustrated, apparatus 1502 may include various elements configured for various functions. In one configuration, apparatus 1502 (and specifically baseband unit 1504) includes: means for transmitting first information associated with nuanced user consent control to a second network node. The first information may also be associated with a data processing task and a UE. Apparatus 1502 (and specifically baseband unit 1504) includes: means for receiving, based on nuanced user consent control, user consent results associated with the data processing task and the UE from the second network node. Apparatus 1502 (and specifically baseband unit 1504) includes: means for processing a data processing task based on the user consent results.

[0146] In one configuration, granular user consent control may be based on at least one of the following: region, PLMN, RAT, RNC, destination region, slice, service associated with the data processing task, carrier frequency, time, UE power state, available UE compute power, or the user of the UE. In one configuration, the user consent result may also be based on second information or first information from the UE. The first information may indicate at least one of region, PLMN, RAT, RNC, destination region, or carrier frequency. The second information may include the UE power state or an indication of the available UE compute power. In one configuration, for processing a data processing task based on the user consent result, device 1502 (and specifically baseband unit 1504) includes: a component for initiating, modifying, or terminating the data processing task based on the user consent result. In one configuration, for processing a data processing task based on the user consent result, device 1502 (and specifically baseband unit 1504) includes: a component for transmitting the configuration associated with the data processing task to the UE based on the user consent result. In one configuration, the data processing task can be a data collection task based on a service associated with a service ID. In one configuration, the first network node can be a data collection request entity associated with the data processing task or a data processor associated with the data processing task. In one configuration, the first network node can correspond to at least one of OAM, RAN, or NWDAF. The second network node can correspond to UDM. In one configuration, apparatus 1502 (and specifically baseband unit 1504) includes: means for receiving, based on nuanced user consent control, an updated user consent result associated with the data processing task and the user of the UE from the second network node. Apparatus 1502 (and specifically baseband unit 1504) includes: means for processing the data processing task based on the updated user consent result. In one configuration, the transmission of first information to the second network node can correspond to a request for user consent result. In one configuration, the first network node can receive second information from the UE and can forward the second information from the UE to the second network node.

[0147] Each component may be one or more elements of the device 1502 configured to perform the functions described therein.

[0148] Figure 16 is a figure 1600 illustrating an example of the hardware implementation of network entity 1660. In one example, network entity 1660 may be within core network 120. Network entity 1660 may include network processor 1612. Network processor 1612 may include on-chip memory 1612'. In some cases, network entity 1660 may also include additional memory module 1614. Network entity 1660 communicates with CU 1602 directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) via network interface 1680. On-chip memory 1612' and additional memory module 1614 can both be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Processor 1612 is responsible for general processing, including executing software stored on computer-readable storage media / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. Computer-readable media / memory can also be used to store data manipulated by the processor when executing software.

[0149] As discussed above, element 1640 may be configured to: receive first information associated with the nuanced user consent control from a first network node. The first information may also be associated with a data processing task and a UE. Element 1640 may be configured to: receive second information associated with the nuanced user consent control from a first network node or a UE. The second information may also be associated with a data processing task and a UE. Element 1640 may be configured to: identify a user consent result associated with a user of the data processing task and the UE based on the nuanced user consent control. The user consent result may also be based on the first information or the second information. Element 1640 may be configured to: transmit the user consent result to the first network node or the UE. Element 1640 may be within processor 1612. Element 1640 may be one or more hardware elements specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1660 may include various elements configured for various functions. In one configuration, network entity 1660 may include: a component for receiving first information associated with nuanced user consent control from a first network node. The first information may also be associated with a data processing task and a UE. Network entity 1660 may include: a component for receiving second information associated with nuanced user consent control from the first network node or a UE. The second information may also be associated with a data processing task and a UE. Network entity 1660 may include: a component for identifying a user consent result associated with a user of the data processing task and the UE based on the nuanced user consent control. The user consent result may also be based on either the first or second information. Network entity 1660 may include: a component for transmitting the user consent result to the first network node or the UE.

[0150] In one configuration, the granular user consent control may be based on at least one of the following: region, PLMN, RAT, RNC, destination region, slice, service associated with the data processing task, carrier frequency, time, UE power state, available UE computing power, or the user of the UE. In one configuration, the first information may include at least one of region, PLMN, RAT, RNC, destination region, or carrier frequency. The second information may include UE power state or an indication of available UE computing power. In one configuration, the data processing task may be a data collection task based on a service associated with a service ID. In one configuration, the first network node may be a data collection request entity associated with the data processing task or a data processor associated with the data processing task. In one configuration, the first network node may correspond to at least one of OAM, RAN, or NWDAF. The second network node may correspond to UDM. In one configuration, network entity 1660 may include: a component for identifying the updated user consent result associated with the data processing task and the user of the UE based on the granular user consent control. Network entity 1660 may include components for transmitting an updated user consent result to a first network node or a UE. In one configuration, the updated user consent result may be transmitted to the UE without tracking communication modifications. In one configuration, the user consent result may be transmitted to the UE via at least one third network node. In one configuration, the at least one third network node may correspond to an AMF or a base station. In one configuration, a second network node may store data associated with granular user consent control. In one configuration, first information received from the first network node may correspond to a request for a user consent result. The user consent result may be transmitted to the first network node based on the request for the user consent result.

[0151] Each component may be an element 1640 of the network entity 1660 configured to perform the functions described by each component.

[0152] Referring back to Figures 4-16, the first network node can transmit first information associated with granular user consent control to the second network node, and the second network node can receive the first information from the first network node. The first information can also be associated with a data processing task and the UE. The second network node can receive second information associated with granular user consent control from the first network node or the UE. The second information can also be associated with a data processing task and the UE. The second network node can identify the user consent result associated with the data processing task and the user based on the UE's granular user consent control for one or more specific services. The user consent result can also be based on the first information or the second information. The second network node can transmit the user consent result to the first network node, and the first network node can receive the user consent result from the second network node. Subsequently, the first network node can process the data processing task based on the user consent result. Accordingly, restrictions on data collection or processing tasks based on user consent can be implemented and enforced with fine granularity, which can provide users with greater flexibility in controlling data collection or processing tasks.

[0153] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of exemplary methods. Based on design preferences, it should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. Furthermore, some blocks can be combined or omitted. The appended method request presents the elements of the individual blocks in a sampling order, and does not imply limitation to the specific order or hierarchy presented.

[0154] The above description is provided to enable any person skilled in the art to practice the various forms described herein. Various modifications to these forms will be readily apparent to those skilled in the art, and the overall principles defined herein can be applied to other forms. Therefore, each request is not intended to limit itself to the forms shown herein, but should be given the full scope consistent with the literal request, wherein, unless specifically stated otherwise, references to singular elements are not intended to indicate "one and only one," but rather "one or more." Terms such as "if," "when," and "at" should be interpreted as meaning "under the condition of," rather than implying an immediate temporal relationship or response. That is, such phrases (e.g., "when") do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if a condition is met, without requiring a specific or immediate temporal constraint on the occurrence of that action. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any state described herein as "exemplary" need not be construed as preferred or advantageous over other states. Unless otherwise specifically stated, the term "some" means one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. A set should be interpreted as a group of elements having one or more elements. Accordingly, for a set of X, X will include one or more elements. All structural and functional equivalents of the elements of the various states described herein that are known or about to become known to a person of ordinary skill are expressly incorporated herein by reference and are intended to be included in the claim. Furthermore, nothing herein is intended to be donated to the public, whether or not such disclosure is expressly stated in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, an element of the claim should not be interpreted as a component plus a function unless the element is expressly stated using the phrase “component for…”.

[0155] The following forms are illustrative only and may be combined with other forms or teachings described herein without limitation.

[0156] Sample 1 is an apparatus for wireless communication at a first network node, comprising: at least one processor coupled to the memory and configured to: transmit to a second network node first information associated with a nuanced user consent control, the first information also associated with a data processing task and a UE; receive from the second network node, based on the nuanced user consent control, a user consent result associated with a user of the data processing task and the UE; and process the data processing task based on the user consent result.

[0157] State 2 is a device of State 1, wherein the user consent control is based on at least one of the following: region, PLMN, RAT, RNC, destination region, slice, service associated with data processing task, carrier frequency, time, UE power state, available UE compute power, or UE user.

[0158] State 3 is a device of either State 1 or 2, wherein the user consent result is also based on second information or the first information from the UE, the first information indicating at least one of region, PLMN, RAT, RNC, destination region, or carrier frequency, and the second information includes UE power status or an indication of the power of available UEs.

[0159] State 4 is an apparatus of any one of states 1 to 3, wherein, in order to process the data processing task based on the user's consent, the at least one processor is also configured to: start, modify or terminate the data processing task based on the user's consent.

[0160] State 5 is an apparatus of any one of states 1 to 4, wherein, in order to process the data processing task based on the user consent result, the at least one processor is also configured to transmit configuration associated with the data processing task to the UE based on the user consent result.

[0161] Speed ​​6 is a device of any one of Speed ​​1 to 5, wherein the data processing task is a data collection task based on a service associated with a service ID.

[0162] State 7 is an apparatus of any one of states 1 to 6, wherein the first network node is a data collection request entity associated with the data processing task or a data processor associated with the data processing task.

[0163] Speed ​​8 is an apparatus of any one of Speed ​​1 to 7, wherein the first network node corresponds to at least one of OAM, RAN or NWDAF, and the second network node corresponds to UDM.

[0164] State 9 is an apparatus of any one of states 1 to 8, and the at least one processor is also configured to: receive, based on the nuanced user consent control, an updated user consent result associated with the data processing task and the user of the UE from the second network node; and process the data processing task based on the updated user consent result.

[0165] State 10 is a device of any one of states 1 to 9, wherein the transmission of the first information to the second network node corresponds to a request for the user's consent result.

[0166] Session 11 is an apparatus of any one of modes 1 to 10, wherein the first network node receives second information from the UE and forwards the second information from the UE to the second network node.

[0167] Speed ​​12 is a device of any one of Speed ​​1 to 11, and also includes a transceiver coupled to the at least one processor.

[0168] Sample 13 is an apparatus for wireless communication at a second network node, comprising: at least one processor coupled to the memory and configured to: receive from a first network node first information associated with a nuanced user consent control, the first information also associated with a data processing task and a UE; receive from the first network node or the UE second information associated with the nuanced user consent control, the second information also associated with the data processing task and the UE; identify, based on the nuanced user consent control, a user consent result associated with a user of the data processing task and the UE, the user consent result also based on the first information or the second information; and transmit the user consent result to the first network node or the UE.

[0169] Style 14 is a device of style 13, wherein the user consent control is based on at least one of the following: region, PLMN, RAT, RNC, destination region, slice, service associated with data processing task, carrier frequency, time, UE power state, available UE computed power, or UE user.

[0170] Session 15 is an apparatus of either state 13 or 14, wherein the first information includes at least one of region, PLMN, RAT, RNC, destination region or carrier frequency, and the second information includes UE power status or an indication of the power of available UEs.

[0171] State 16 is an apparatus of any one of states 13 to 15, wherein the data processing task is a data collection task based on a service associated with a service ID.

[0172] State 17 is an apparatus of any one of states 13 to 16, wherein the first network node is a data collection request entity associated with the data processing task or a data processor associated with the data processing task.

[0173] Speed ​​18 is an apparatus of any one of Speed ​​13 to 17, wherein the first network node corresponds to at least one of OAM, RAN or NWDAF, and the second network node corresponds to UDM.

[0174] The apparatus of the form 19 is any one of the forms 13 to 18, and the at least one processor is also configured to: identify the updated user consent result associated with the user of the data processing task and the UE based on the nuanced user consent control; and transmit the updated user consent result to the first network node or the UE.

[0175] Session 20 is a device of state 19, wherein the updated user consent result is transmitted to the UE without tracking communication period modification.

[0176] State 21 is an apparatus of any one of states 13 to 20, wherein the user consent result is transmitted to the UE via at least one third network node.

[0177] State 22 is a device of state 21, wherein the at least one third network node corresponds to an AMF or a base station.

[0178] Format 23 is a device of any one of Formats 13 to 22, wherein the second network node stores data associated with the personalized user consent control.

[0179] State 24 is an apparatus of any one of states 13 to 23, wherein the first information received from the first network node corresponds to a request for the user consent result, and the user consent result is transmitted to the first network node based on the request for the user consent result.

[0180] Speed ​​25 is a device of any one of Speed ​​13 to 24, and also includes a transceiver coupled to the at least one processor.

[0181] Style 26 is a wireless communication method for implementing any of styles 1 to 25.

[0182] State 27 is a device for wireless communication, including components for implementing any one of states 1 to 25.

[0183] Format 28 is a computer-readable medium that stores computer-executable code, wherein when executed by a processor, the processor enables the processor to implement any of Formats 1 to 25. [Simplified Explanation of the Diagram]

[0009] Figure 1 is a diagram illustrating examples of various wireless communication systems and access networks according to the contents of this case.

[0010] Figure 2A is a diagram illustrating an example of the first message frame of various states according to the content of this case.

[0011] Figure 2B is a diagram illustrating an example of a DL channel within a subframe of various states according to the content of this case.

[0012] Figure 2C is a diagram illustrating an example of a second message frame according to the various states of the case.

[0013] Figure 2D is a diagram illustrating an example of a UL channel within a subframe of various states according to the content of this case.

[0014] Figure 3 is a diagram illustrating examples of base stations and user equipment (UE) in various states of an access network according to the contents of this case.

[0015] Figure 4 is a diagram illustrating exemplary user consent information stored in a unified data management (UDM) according to various forms of the content of this case.

[0016] Figure 5 is a flowchart illustrating an exemplary method for processing user consent at a subscription entity according to one or more states.

[0017] Figure 6 is a flowchart illustrating an exemplary method for processing user consent at a UDM according to one or more states.

[0018] Figure 7 is a diagram illustrating a communication flow for implementing an exemplary method for updating user consent results according to one or more states.

[0019] Figure 8 is a diagram illustrating a communication flow for implementing an exemplary method for updating user consent results according to one or more states.

[0020] Figure 9 is a diagram illustrating a communication flow for implementing an exemplary method for updating user consent results according to one or more states.

[0021] Figure 10 is a diagram illustrating the communication flow of an exemplary method of wireless communication according to various states of the present case.

[0022] Figure 11 is a flowchart of various wireless communication methods according to the contents of this case.

[0023] Figure 12 is a flowchart of various wireless communication methods according to the contents of this case.

[0024] Figure 13 is a flowchart of various wireless communication methods according to the contents of this case.

[0025] Figure 14 is a flowchart of various wireless communication methods according to the contents of this case.

[0026] Figure 15 is a diagram illustrating examples of hardware implementations for an exemplary device according to various states of the present invention.

[0027] Figure 16 is a diagram illustrating an example of hardware implementation of an exemplary device according to various states of the present invention. [Biomaterial Storage]

[0185] Domestic storage information (please note in order of storage institution, date, and number) None Foreign storage information (please note in order of storage country, institution, date, and number) None

Claims

1. An apparatus for wireless communication at a first network node, comprising: One memory; and at least one processor coupled to the memory and configured to: transmit to a second network node first information associated with a nuanced user consent control, the first information also associated with a data processing task and a user equipment (UE); receive from the second network node a user consent result associated with the data processing task and a user of the UE based on the nuanced user consent control; and process the data processing task based on the user consent result.

2. The apparatus according to claim 1, wherein the user consents to control based on at least one of the following: a region, a Public Land Mobile Network (PLMN), a Radio Access Technology (RAT), a Radio Network Controller (RNC), a destination region, a slice, a service associated with the data processing task, a carrier frequency, a time, a UE power state, available UE compute power, or the user of the UE.

3. The device according to request item 1, wherein the user consent result is also based on second information or the first information from the UE, the first information indicating at least one of the following: a region, a public terrestrial mobile network (PLMN), a radio access technology (RAT), a radio network controller (RNC), a destination area, or a carrier frequency, and the second information includes a UE power status or an indication of the power of the available UE.

4. The apparatus according to claim 1, wherein, in order to process the data processing task based on the user's consent, the at least one processor is also configured to: initiate, modify, or terminate the data processing task based on the user's consent.

5. The apparatus according to request item 1, wherein, in order to process the data processing task based on the user consent result, the at least one processor is also configured to: transmit a configuration associated with the data processing task to the UE based on the user consent result.

6. The apparatus according to request item 1, wherein the data processing task is a data collection task based on a service associated with a service identifier (ID).

7. The apparatus according to claim 1, wherein the first network node is a data collection request entity associated with the data processing task or a data processor associated with the data processing task.

8. The apparatus according to claim 1, wherein the first network node corresponds to at least one of an Operation, Administration and Maintenance (OAM), a Radio Access Network (RAN), or a Network Data Analysis Function (NWDAF), and the second network node corresponds to a Unified Data Management (UDM).

9. The apparatus according to claim 1, wherein the at least one processor is also configured to: receive, based on the nuanced user consent control, an updated user consent result associated with the data processing task and the user of the UE from the second network node; and process the data processing task based on the updated user consent result.

10. The apparatus according to request item 1, wherein the transmission of the first information to the second network node corresponds to a request for the user's consent result.

11. The apparatus according to request item 1, wherein the first network node receives second information from the UE and forwards the second information from the UE to the second network node.

12. The apparatus according to claim 1 also includes a transceiver coupled to the at least one processor.

13. A method of wireless communication at a first network node, comprising the steps of: transmitting to a second network node first information associated with a nuanced user consent control, the first information also being associated with a data processing task and a user equipment (UE); receiving from the second network node a user consent result associated with the data processing task and a user of the UE based on the nuanced user consent control; and processing the data processing task based on the user consent result.

14. The method of claim 13, wherein the user consent control is based on at least one of the following: a region, a Public Land Mobile Network (PLMN), a Radio Access Technology (RAT), a Radio Network Controller (RNC), a destination region, a slice, a service associated with the data processing task, a carrier frequency, a time, a UE power state, available UE compute power, or the user of the UE.

15. The method according to request item 13, wherein the user consent result is also based on second information or the first information from the UE, the first information indicating at least one of the following: a region, a public terrestrial mobile network (PLMN), a radio access technology (RAT), a radio network controller (RNC), a destination area, or a carrier frequency, and the second information includes a UE power status or an indication of the power of an available UE.

16. An apparatus for wireless communication at a second network node, comprising: One memory; The system includes at least one processor coupled to the memory and configured to: receive first information associated with a nuanced user consent control from a first network node, the first information also associated with a data processing task and a user equipment (UE); receive second information associated with the nuanced user consent control from the first network node or the UE, the second information also associated with the data processing task and the UE; identify a user consent result associated with a user of the data processing task and the UE based on the nuanced user consent control, the user consent result also based on the first information or the second information; and transmit the user consent result to the first network node or the UE.

17. The apparatus according to claim 16, wherein the user consent to control is based on at least one of the following: a region, a Public Land Mobile Network (PLMN), a Radio Access Technology (RAT), a Radio Network Controller (RNC), a destination region, a slice, a service associated with the data processing task, a carrier frequency, a time, a UE power state, available UE compute power, or the user of the UE.

18. The apparatus according to claim 16, wherein the first information indicates at least one of the following: an area, a public terrestrial mobile network (PLMN), a radio access technology (RAT), a radio network controller (RNC), a destination area, or a carrier frequency, and the second information includes a UE power status or an indication of the power of an available UE.

19. The apparatus according to claim 16, wherein the data processing task is a data collection task based on a service associated with a service identifier (ID).

20. The apparatus according to claim 16, wherein the first network node is a data collection request entity associated with the data processing task or a data processor associated with the data processing task.

21. The apparatus according to claim 16, wherein the first network node corresponds to at least one of an Operation, Administration and Maintenance (OAM), a Radio Access Network (RAN), or a Network Data Analysis Function (NWDAF), and the second network node corresponds to a Unified Data Management (UDM).

22. The apparatus according to claim 16, wherein the at least one processor is also configured to: identify an updated user consent result associated with the user of the data processing task and the UE based on the nuanced user consent control, the updated user consent result also being based on updated first information or updated second information; and transmit the updated user consent result to the first network node or the UE.

23. The apparatus according to claim 22, wherein the updated user consent result is transmitted to the UE without a tracking communication period modification.

24. The apparatus according to request item 16, wherein the user consent result is transmitted to the UE via at least one third network node.

25. The apparatus according to claim 24, wherein the at least one third network node corresponds to an Access and Mobility Management Function (AMF) or a base station.

26. The apparatus according to claim 16, wherein the second network node stores data associated with the personalized user consent control.

27. The apparatus according to claim 16, wherein the first information received from the first network node corresponds to a request for the user consent result, and the user consent result is transmitted to the first network node based on the request for the user consent result.

28. The apparatus according to claim 16 also includes a transceiver coupled to the at least one processor.

29. A method of wireless communication at a second network node, comprising the steps of: receiving from a first network node first information associated with a nuanced user consent control, the first information also associated with a data processing task and a user equipment (UE); receiving from the first network node or the UE second information associated with the nuanced user consent control, the second information also associated with the data processing task and the UE; identifying a user consent result associated with a user of the data processing task and the UE based on the nuanced user consent control, the user consent result also based on the first information or the second information; and transmitting the user consent result to the first network node or the UE.

30. The method of claim 29, wherein the user consent control is based on at least one of the following: a region, a Public Land Mobile Network (PLMN), a Radio Access Technology (RAT), a Radio Network Controller (RNC), a destination region, a slice, a service associated with the data processing task, a carrier frequency, a time, a UE power state, available UE compute power, or the user of the UE.

Images