Revoking and modifying user consent

Abstract

Apparatuses, systems, and methods are provided for revoking and / or modifying user consent in mobile edge computing (MEC). A user equipment device (UE) can determine that user consent needs to be updated. The user consent can be associated with MEC. Additionally, the UE can transmit a user consent modification request to a network, e.g., an edge application server of an edge data network, via an application layer of the UE. The user consent modification request can be carried in application data traffic. The user consent modification request can be indicated via a Nnef_ParameterProvision_Update service operation. The user consent modification request is indicated via a Nnef_ParameterProvision_Update service operation.

Description

Technical Field

[0001] This invention relates to wireless communication, and more particularly to apparatus, systems, and methods for revoking and / or modifying user consent in edge computing (MEC), for example, in 5G NR systems and later versions.

[0002] Related technical descriptions

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can operate complex applications that utilize these capabilities.

[0004] Long Term Evolution (LTE) is currently the technology of choice for most wireless network operators worldwide, providing mobile broadband data and high-speed internet access to their user base. LTE was first proposed in 2004 and first standardized in 2008. Since then, with the exponential growth in the use of wireless communication systems, the demand for wireless network operators has increased to support higher capacity for a higher density of mobile broadband users. Therefore, research into new radio access technologies began in 2015, and in 2017, the first version of 5G New Radio (5G NR) was standardized.

[0005] Compared to LTE, 5G-NR (also known as NR) offers higher capacity for higher density mobile broadband users, while also supporting ultra-reliable and massive machine-type communication between devices, as well as lower latency and / or lower battery consumption. Furthermore, NR allows for more flexible UE scheduling compared to current LTE. Therefore, efforts are underway to leverage the potentially higher throughput at higher frequencies in the ongoing development of 5G-NR. Summary of the Invention

[0006] The implementation scheme relates to wireless communication, and more specifically to apparatus, systems, and methods for revoking and / or modifying user consent in edge computing (MEC), for example, in 5G NR systems and later versions.

[0007] For example, in some implementations, a user equipment (UE), such as UE 106, may be configured to determine that user consent needs to be updated. This determination may be based on various factors, such as indications of changes in user preferences, periodic updates of user preferences, and / or various other factors. User consent may be associated with edge computing (MEC). Additionally, the UE may be configured to transmit a user consent modification request via the UE's application layer to an edge application server in a network, such as an edge data network. The user consent modification request may be carried in application data traffic. In some implementations, the user consent modification request may be indicated via the Nnef_ParameterProvision_Update service operation.

[0008] For example, an Edge Application Server (EAS), such as EAS 834, can be configured to receive user consent modification requests from the UE. User consent modification requests may be associated with the MEC. User consent modification requests may be carried in application data traffic. Additionally, the EAS can be configured to deliver (e.g., send and / or transmit) user consent modification requests to an Edge Enabler Server (EES). User consent modification requests can be indicated via the Nnef_ParameterProvision_Update service operation.

[0009] For example, an Edge Enabler Server (EES), such as EES 844, can be configured to receive user consent modification requests for the UE from the EAS. User consent may be associated with the MEC. Additionally, the EES can be configured to notify the Home Public Land Mobile Network (HPLMN) associated with the UE of the user consent modification.

[0010] For example, a network entity such as the network's AMF can be configured to receive a request for an updated user consent status from the network's PCF. The AMF can be configured to transmit the updated user consent status request to the UE. Furthermore, the AMF can be configured to receive the updated user consent status from the UE and forward the updated user consent status to the PCF.

[0011] For example, a network entity such as the network's SMF can be configured to trigger (e.g., initiate) an EAS relocation and can receive user consent modification requests from the network's AF. Additionally, the SMF can be configured to implement (e.g., execute) a PDU session modification process to update user consent.

[0012] For example, a network entity such as the network's SMF can be configured to receive a user consent update request from the network's AMF via a PDU update message. Additionally, the SMF can be configured to send a PDU response to the AMF that may include a confirmation of the user consent update and to receive the user consent update from the AMF. The PDU response can be an Nsmf_PDUSession_UpdateSMContext response.

[0013] The techniques described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to any one of the following computing devices: unmanned aerial vehicles (UAVs), unmanned controllers (UACs), UTM servers, base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, and various other computing devices.

[0014] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0015] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:

[0016] Figure 1A An exemplary wireless communication system according to some implementation schemes is shown.

[0017] Figure 1B Examples of base stations and access points communicating with user equipment (UE) devices according to some implementation schemes are shown.

[0018] Figure 2 An exemplary block diagram of a base station according to some implementation schemes is shown.

[0019] Figure 3 An exemplary block diagram of a server according to some implementation schemes is shown.

[0020] Figure 4 An exemplary block diagram of a UE according to some implementation schemes is shown.

[0021] Figure 5 An example block diagram of a cellular communication circuit according to some implementation schemes is shown.

[0022] Figure 6AExamples of 5G network architectures according to some implementation schemes are shown, which combine 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to 5G CN.

[0023] Figure 6B Examples of 5G network architectures according to some implementation schemes are shown, which combine dual 3GPP (e.g., LTE and 5G NR) access to 5G CN as well as non-3GPP access.

[0024] Figure 7 An example of a baseband processor architecture for a UE according to some implementation schemes is shown.

[0025] Figure 8 An example of updating user consent in an edge network is shown, according to some implementation schemes.

[0026] Figure 9 An example of signaling used by the PCF, according to some implementation schemes, to initiate a UE configuration update to trigger a user consent update process is shown.

[0027] Figure 10 An example of signaling used by the SMF, according to some implementation schemes, to initiate a UE configuration update to trigger a user consent update process is shown.

[0028] Figure 11 An example of signaling used by a UE to initiate a UE configuration update to trigger a user consent update process, according to some implementation schemes, is shown.

[0029] Figure 12A An example of a method for user consent modification initiated by a UE, according to some implementation schemes, is shown.

[0030] Figure 12B An example of another method for user consent modification initiated by the UE, according to some implementation schemes, is shown.

[0031] Figure 12C An example of yet another method for user consent modification initiated by the UE, according to some implementation schemes, is shown.

[0032] Figure 13 An example of a method for user consent modification initiated by the AMF, according to some implementation schemes, is shown.

[0033] Figure 14 An example of a method for user consent modification initiated by an SMF, according to some implementation schemes, is shown.

[0034] Figure 15 An example of another method for user consent modification initiated by SMF, according to some implementation schemes, is shown.

[0035] While the features described herein may be subject to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and the detailed description thereof are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0036] acronym

[0037] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms that may appear throughout this disclosure are as follows:

[0038] 3GPP: Third Generation Partnership Project

[0039] UE: User Equipment

[0040] RF: Radio Frequency

[0041] ·BS: Base Station

[0042] DL: Downlink

[0043] ·UL: Uplink

[0044] LTE: Long Term Evolution

[0045] NR: New Radio

[0046] ·5GS: 5G system

[0047] ·5GMM: 5GS Mobility Management

[0048] ·5GC / 5GCN: 5G Core Network

[0049] ·IE: Information Elements

[0050] ·CE: Control element

[0051] MAC: Media Access Control

[0052] •SSB: Synchronization Signal Block

[0053] • CSI-RS: Channel State Information Reference Signal

[0054] • PDCCH: Physical Downlink Control Channel

[0055] • PDSCH: Physical Downlink Shared Channel

[0056] •RRC: Radio Resource Control

[0057] • RRM: Radio Resource Management

[0058] • CORESET: Control Resource Set

[0059] •TCI: Transport Configuration Indicator

[0060] • DCI: Downlink Control Indicator

[0061] the term

[0062] The following is a glossary of terms used in this disclosure:

[0063] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems connected via a network, for example. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0064] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).

[0065] Programmable hardware elements encompass a variety of hardware devices that include multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0066] Computer system (or computer) — any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0067] User equipment (UE) (or “UE device”) — any of a variety of computer system devices that are mobile or portable and perform wireless communications. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM Telephones), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM Laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as encompassing any electronic, computing, and / or telecommunications equipment (or combination of equipment) that is easily transportable by the user and capable of wireless communication.

[0068] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and is used for communication as part of a wireless telephone system or radio system.

[0069] Edge computing (MEC) refers to the infrastructure that enables software-only mobility or Software-as-a-Service (SaaS) applications to operate entirely within a standardized virtualization platform deployed at or near the network edge. The MEC architecture can comprise two functional areas: host and management. The management layer includes host and system-level management entities.

[0070] Network Exposure Function (NEF) - refers to the function that provides a mechanism for securely exposing the services and capabilities provided by 3GPP network functions.

[0071] A processing element (or processor) is a component or combination of components capable of performing the functions of a device such as user equipment or cellular network equipment. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0072] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0073] Frequency band – The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which channels are used or reserved for the same purpose.

[0074] Wi-Fi—The term “Wi-Fi” (or WiFi) encompasses the full range of its common meaning and includes at least wireless communication networks or RATs that are served by and provide connectivity to the Internet through wireless LAN (WLAN) access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” Wi-Fi (WLAN) networks are distinct from cellular networks.

[0075] 3GPP access refers to access technologies (e.g., radio access technologies) specified by 3GPP standards. These access technologies include, but are not limited to, GSM / GPRS, LTE, LTE-A, and / or 5G NR. Generally speaking, 3GPP access refers to various types of cellular access technologies.

[0076] Non-3GPP access refers to any access technology (e.g., radio access technologies) not specified by 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP access can be categorized into two types: "trusted" and "untrusted." Trusted non-3GPP access can interact directly with the Evolved Packet Core (EPC) and / or 5G Core (5GC), while untrusted non-3GPP access interoperates with the EPC / 5GC via network entities such as Evolved Packet Data Gateways and / or 5G NR Gateways. Generally speaking, non-3GPP access refers to various types of non-cellular access technologies.

[0077] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0078] Approximately—means a value close to the correct or precise value. For example, approximately can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, “approximately” may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.

[0079] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0080] Various components can be described as being "configured" to perform one or more tasks. In such contexts, "configured" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently switched on. Typically, the circuit forming the structure corresponding to "configured" can include hardware circuitry.

[0081] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0082] Figure 1A and 1B Communication system

[0083] Figure 1A A simplified exemplary wireless communication system according to some implementation schemes is shown. It should be noted that... Figure 1A The system described herein is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0084] As shown in the figure, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.

[0085] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”), and may include hardware that enables wireless communication with UE 106A to UE 106N.

[0086] The communication area (or coverage area) of a base station can be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-A Advanced, 5G New Radio (5G NR), HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location can be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR environment, its alternative location can be referred to as a "gNodeB" or "gNB".

[0087] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services.

[0088] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-N and similar devices over a geographical area via one or more cellular communication standards.

[0089] Therefore, although base station 102A can act as the "serving cell" for UEs 106A-N as shown in Figure 1, each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-N and / or any other base station), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. Such cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing service area size. For example, base stations 102A to 102B shown in Figure 1 may be macro cells, while base station 102N may be a pico cell. Other configurations are also possible.

[0090] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a "gNB". In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to a new radio communication core (NRC) network. Furthermore, the gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0091] It should be noted that UE 106 can communicate using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, UE 106 can also or alternatively be configured to communicate using one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0092] Figure 1B User equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 and access point 112 according to some embodiments is shown. UE 106 can be a device with cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0093] UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 may execute any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as a field-programmable gate array (FPGA) configured to execute any of the method embodiments of the present invention or any portion thereof.

[0094] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / Advanced LTE, or 5G NR and / or GSM, LTE, Advanced LTE, or 5G NR using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.

[0095] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communication using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0096] Figure 2 Block diagram of a base station

[0097] Figure 2 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 3 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 204 capable of executing program instructions specific to base station 102. Processor 204 may also be coupled to memory management unit (MMU) 240 or other circuitry or devices, which may be configured to receive addresses from processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0098] Base station 102 may include at least one network port 270. Network port 270 may be configured to be coupled to a telephone network and provide access rights as described above in Figure 1 and... Figure 2 The telephone network as described herein includes multiple devices (such as UE device 106).

[0099] Network port 270 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 270 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0100] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5GNR) base station, or "gNB". In such implementations, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0101] Base station 102 may include at least one antenna 234 and possibly multiple antennas. The at least one antenna 234 may be configured to function as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 230. Antenna 234 communicates with radio component 230 via communication link 232. Communication link 232 may be a receive link, a transmit link, or both. Radio component 230 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0102] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0103] As further described herein, base station 102 may include hardware and software components for implementing or supporting embodiments of the features described herein. The processor 204 of base station 102 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 204 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 230, 232, 234, 240, 250, 260, 270, the processor 204 of base station 102 may be configured to implement or support some or all of the features described herein.

[0104] Furthermore, as described herein, processor 204 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 204. Therefore, processor 204 may include one or more integrated circuits (ICs) configured to perform the functions of processor 204. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 204.

[0105] Additionally, as described herein, the radio component 230 may comprise one or more processing elements. In other words, one or more processing elements may be included in the radio component 230. Therefore, the radio component 230 may include one or more integrated circuits (ICs) configured to perform the functions of the radio component 230. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio component 230.

[0106] Figure 3 Server block diagram

[0107] Figure 3 An exemplary block diagram of server 104 according to some implementation schemes is shown. It should be noted that... Figure 3 The server described is merely one example of a possible server. As shown, server 104 may include processor 344 capable of executing program instructions specific to server 104. Processor 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from processor 344 and translate those addresses into locations in memory (e.g., memory 364 and read-only memory (ROM) 354) or to other circuitry or devices.

[0108] Server 104 can be configured to provide network access functionality to multiple devices, such as base station 102, UE device 106, and / or UTM 108, for example, as further described herein.

[0109] In some implementations, server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some implementations, server 104 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network.

[0110] As further described herein, server 104 may include hardware and software components for implementing or supporting the implementation of the features described herein. Processor 344 of server 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 344 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or configured as an ASIC (Application-Specific Integrated Circuit) or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 354, 364, and / or 374, processor 344 of server 104 may be configured to implement or support some or all of the features described herein.

[0111] Furthermore, as described herein, processor 344 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 344. Therefore, processor 344 may include one or more integrated circuits (ICs) configured to perform the functions of processor 344. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 344.

[0112] Figure 4 : UE block diagram

[0113] Figure 4An exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. It should be noted that... Figure 4 The block diagram of the communication device is merely one example of possible communication devices. According to the implementation, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, an unmanned aerial vehicle (UAV), a UAV controller (UAC), and / or a combination of devices, as well as other devices. As shown, the communication device 106 may include a set of components 400 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, the set of components 400 may be implemented as individual components or groups of components for various purposes. This set of components 400 may be (e.g., communicatively; directly or indirectly) coupled to various other circuits of the communication device 106.

[0114] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 410), input / output interfaces such as connector I / F 420 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 460 that may be integrated with or external to communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 429 (e.g., Bluetooth). TM (and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0115] Cellular communication circuitry 430 may be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 435 and 436 shown. Short-to-medium-range wireless communication circuitry 429 may also be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 437 and 438 shown. Alternatively, short-to-medium-range wireless communication circuitry 429 may be coupled (e.g., communicatively grounded; directly or indirectly) to antennas 437 and 438, or as an alternative, to antennas 435 and 436. Short-to-medium-range wireless communication circuitry 429 and / or cellular communication circuitry 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration.

[0116] In some embodiments, as further described below, the cellular communication circuit 430 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). Furthermore, in some embodiments, the cellular communication circuit 430 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain and a shared transmit chain.

[0117] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. User interface elements may include any of a variety of components such as a display 460 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other components capable of providing information to the user and / or receiving or interpreting user input.

[0118] The communication device 106 may also include one or more smart cards 445 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more general-purpose integrated circuit cards) 445. It should be noted that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functions, such as one or more UICC cards 445, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that can be embedded, for example, soldered to a circuit board in the UE 106, or each SIM 410 may be implemented as a removable smart card. Therefore, a SIM may be one or more removable smart cards (such as UICC cards, sometimes referred to as "SIM cards"), and / or SIM 410 may be one or more embedded cards (such as embedded UICCs (eUICCs), sometimes referred to as "eSIMs" or "eSIM cards"). In some implementations (such as when the SIM includes an eUICC), one or more SIMs within the SIM can implement embedded SIM (eSIM) functionality; in such implementations, a single SIM within the SIM can execute multiple SIM applications. Each SIM may include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality may be stored in memory and executed by the processor. In some implementations, UE 106 may include, as needed, a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards implementing eSIM functionality). For example, UE 106 may include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also envisioned.

[0119] As described above, in some implementations, UE 106 may include two or more SIMs. Including two or more SIMs in UE 106 allows UE 106 to support two different phone numbers and allows UE 106 to communicate on two or more corresponding networks. For example, the first SIM may support a first RAT such as LTE, and the second SIM 106 may support a second RAT such as 5G NR. Other implementations and RATs are also possible. In some implementations, when UE 106 includes two SIMs, UE 106 may support Dual SIM Dual Standby (DSDA) functionality. DSDA functionality allows UE 106 to connect to two networks simultaneously (and use two different RATs), or allows two connections supported by two different SIMs using the same or different RATs to be maintained simultaneously on the same or different networks. DSDA functionality also allows UE 106 to receive voice calls or data traffic simultaneously on either phone number. In some implementations, voice calls may be packet-switched communications. In other words, voice calls can be received using LTE-based Voice (VoLTE) technology and / or NR-based Voice (VoNR) technology. In some implementations, UE 106 may support Dual SIM Dual Standby (DSDS) functionality. DSDS functionality allows either of the two SIMs in UE 106 to remain in standby while awaiting a voice call and / or data connection. In DSDS, when a call / data connection is established on one SIM, the other SIM is no longer active. In some implementations, DSDx functionality (DSDA or DSDS functionality) can be implemented using a single SIM (e.g., eUICC) that performs multiple SIM applications for different carriers and / or RATs.

[0120] As shown in the figure, the SOC 400 may include a processor 402 and a display circuit 404. The processor executes program instructions for the communication device 106, and the display circuit performs graphics processing and provides display signals to the display 460. The processor 402 may also be coupled to a memory management unit (MMU) 440 (which may be configured to receive addresses from the processor 402 and translate those addresses into locations in memory (e.g., memory 406, read-only memory (ROM) 450, NAND flash memory 410)) and / or coupled to other circuitry or devices (such as the display circuit 404, short-to-medium range wireless communication circuitry 429, cellular communication circuitry 430, connector I / F 420, and / or display 460). The MMU 440 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 440 may be included as part of the processor 402.

[0121] As described above, communication device 106 can be configured to communicate using wireless and / or wired communication circuits. Communication device 106 can be configured to perform methods for revoking and / or modifying user consent in the MEC, for example, in 5G NR systems and later, as further described herein.

[0122] As described herein, communication device 106 may include hardware and software components for implementing the features described above to transmit a scheduling profile for power saving to a network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium), processor 402 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), processor 402 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), in conjunction with one or more of other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460, processor 402 of communication device 106 may be configured to implement some or all of the features described herein.

[0123] Furthermore, as described in this invention, processor 402 may include one or more processing elements. Therefore, processor 402 may include one or more integrated circuits (ICs) configured to perform the functions of processor 402. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 402.

[0124] Furthermore, as described herein, the cellular communication circuit 430 and the short-to-medium-range wireless communication circuit 429 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 430, and similarly, one or more processing elements may be included in the short-to-medium-range wireless communication circuit 429. Therefore, the cellular communication circuit 430 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 430. Similarly, the short-to-medium-range wireless communication circuit 429 may include one or more ICs configured to perform the functions of the short-to-medium-range wireless communication circuit 429. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-to-medium-range wireless communication circuit 429.

[0125] Figure 5 Block diagram of cellular communication circuit

[0126] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. It should be noted that... Figure 5 The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to the implementation, the cellular communication circuit 530 (which may be the cellular communication circuit 430) may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of these devices.

[0127] Cellular communication circuit 530 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( Figure 4 Antennas 435a-435b and 436 are shown in the diagram. In some embodiments, the cellular communication circuitry 530 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, as... Figure 5 As shown, the cellular communication circuit 530 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT, such as LTE or LTE-A, and the modem 520 may be configured for communication according to a second RAT, such as 5G NR.

[0128] As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some embodiments, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0129] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0130] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 530 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 530 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0131] In some implementations, the cellular communication circuit 530 may be configured to perform methods for revoking and / or modifying user consent in the MEC, for example, in 5G NR systems and later, as further described herein.

[0132] As described herein, modem 510 may include hardware and software components for implementing the features described above or for UL data used in time-division multiplexing NSA NR operation, as well as various other techniques described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 512 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), processor 512 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 550, 570, 572, 335, and 336.

[0133] Furthermore, as described herein, processor 512 may include one or more processing elements. Therefore, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0134] As described herein, modem 520 may include hardware and software components designed to implement the aforementioned features for transmitting power-saving scheduling profiles to the network, as well as various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or additionally), processor 522 may be configured to implement some or all of the features described herein by combining one or more of other components 540, 542, 544, 550, 570, 572, 335, and 336.

[0135] Furthermore, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0136] Figure 6A , Figure 6B and Figure 7 5G Core Network Architecture—Interoperability with Wi-Fi

[0137] In some implementations, access to the 5G core network (CN) can be made via (or through) cellular connections / interfaces (e.g., via 3GPP communication architectures / protocols) and non-cellular connections / interfaces (e.g., non-3GPP access architectures / protocols such as Wi-Fi connections). Figure 6AAn example of a 5G network architecture according to some implementation schemes is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN. As shown, a user equipment device (e.g., such as UE 106) can access the 5G CN via both a radio access network (RAN, such as gNB 604, which may be base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to a non-3GPP Interoperability Function (N3IWF) 603 network entity. N3IWF may include a connection to the core access and mobility management function (AMF) 605 of the 5G CN. AMF 605 may include an instance of 5G mobility management (5G MM) functions associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register for access simultaneously via gNB 604 and AP 612. As shown, AMF 605 may include one or more functional entities associated with the 5G CN (e.g., Network Slice Selection Function (NSSF) 620, Short Message Service Function (SMSF) 622, Application Function (AF) 624, Unified Data Management (UDM) 626, Policy Control Function (PCF) 628, and / or Authentication Server Function (AUSF) 630). It should be noted that these functional entities can also be supported via the 5G CN's Session Management Functions (SMF) 606a and SMF 606b. AMF 605 can connect to (or communicate with) SMF 606a. Furthermore, gNB 604 can communicate with (or connect to) User Plane Function (UPF) 608a, which can also communicate with SMF 606a. Similarly, the N3IWF 603 can communicate with the UPF 608b, which in turn can communicate with the SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and the Internet Protocol (IP) Multimedia Subsystem / IP Multimedia Core Network Subsystem (IMS) Core Network 610.

[0138] Figure 6BAn example of a 5G network architecture according to some implementation schemes is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to the 5GCN as well as non-3GPP access. As shown, a user equipment device (e.g., such as UE 106) can access the 5G CN via both a radio access network (RAN, such as gNB 604 or eNB 602, which may be base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to the N3IWF 603 network entity. N3IWF may include a connection to the AMF 605 of the 5G CN. AMF 605 may include an instance of 5G MM functionality associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 612. Additionally, the 5G CN can support dual registration of the UE on both a legacy network (e.g., LTE via eNB 602) and a 5G network (e.g., via gNB 604). As shown, eNB 602 may have connections to both Mobility Management Entity (MME) 642 and Service Gateway (SGW) 644. MME 642 may have connections to both SGW 644 and AMF 605. Furthermore, SGW 644 may have connections to both SMF 606a and UPF 608a. As shown, AMF 605 may include one or more functional entities associated with the 5G CN (e.g., NSSF 620, SMSF 622, AF 624, UDM 626, PCF 628, and / or AUSF 630). Note that UDM 626 may also include Home Subscriber Server (HSS) functionality, and PCF may also include Policy and Charging Rules (PCRF) functionality. It should also be noted that these functional entities can also be supported by the 5G CN's SMF 606a and SMF 606b. The AMF 606 can connect to (or communicate with) the SMF 606a. Furthermore, the gNB 604 can communicate with (or connect to) the UPF 608a, which in turn can communicate with the SMF 606a. Similarly, the N3IWF 603 can communicate with the UPF 608b, which in turn can communicate with the SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and the IMS core network 610.

[0139] It should be noted that, in various implementations, one or more of the network entities described above may be configured to perform methods for improving security checks in 5G NR networks, including mechanisms for revoking and / or modifying user consent in the MEC, for example, in 5G NR systems and later versions, as further described herein.

[0140] Figure 7 An example of a baseband processor architecture for a UE (e.g., such as UE 106) according to some implementation schemes is shown. Figure 7 The baseband processor architecture 700 described herein may be implemented on one or more radio components (e.g., radio components 429 and / or 430) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum (NAS) 710 may include a 5G NAS 720 and a traditional NAS 750. The traditional NAS 750 may include a communication connection with a traditional access stratum (AS) 770. The 5G NAS 720 may include communication connections with a 5G AS 740 and a non-3GPP AS 730, as well as a Wi-Fi AS 732. The 5G NAS 720 may include functional entities associated with both access strata. Therefore, the 5G NAS 720 may include multiple 5G MM entities 726 and 728 and 5G session management (SM) entities 722 and 724. The traditional NAS 750 may include functional entities such as Short Message Service (SMS) entity 752, Evolved Packet System (EPS) Session Management (ESM) entity 754, Session Management (SM) entity 756, EPS Mobility Management (EMM) entity 758, and Mobility Management (MM) / GPRS Mobility Management (GMM) entity 760. Furthermore, the traditional AS 770 may include functional entities such as LTE AS 772, UMTS AS 774, and / or GSM / GPRS AS 776.

[0141] Therefore, the baseband processor architecture 700 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access) networks. It's important to note that, as shown in the figure, the 5G MM can maintain separate connection management and registration management state machines for each connection. Furthermore, a device (e.g., UE 106) can register to a single PLMN (e.g., 5GCN) using both 5G cellular and non-cellular access. Additionally, a device can be in a connected state in one access and an idle state in another, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0142] It should be noted that, in various implementations, one or more of the aforementioned functional entities of the 5G NAS and / or 5G AS may be configured to perform methods for revoking and / or modifying user consent in the MEC, for example, in 5G NR systems and later, as further described herein.

[0143] Revoke / Modify User Consent

[0144] In a current implementation, such as that defined by TR 33.867V4.0, a 5G system (5GS) is required to specify a mechanism that allows users to change and / or add consent to services. User consent could be collected, for example, at the start of service in edge computing (MEC), where the edge application server (EAS) could request user consent when the UE registers for the service. Thus, the user can confirm consent at the start; however, at some point during service, the user can change their consent from agreeing to share sensitive user information (such as UE location) to disagreeing to not share sensitive user information. Therefore, a process for the UE to modify and / or withdraw user consent may be necessary.

[0145] The implementation schemes described herein provide systems, methods, and mechanisms to support the revocation and / or modification of user consent in the MEC, including systems, methods, and mechanisms for modifying / revoking user consent via Network Exposure Function (NEF), periodically updating user consent, and UE-initiated user consent modifications. In some implementations, user consent can be collected at the application layer and / or 3GPP layer of the UE, such as UE 106. For example, when user consent is collected at the UE's application layer, modification / revocation can also be sent through the application layer. Therefore, to update the status of user consent in the Mobile Network Operator (MNO) network, the application server can send a notification to the MNO domain (e.g., a Unified Data Management (UDM) server and / or other network entities) through the interface with the NEF. It should be noted that the way the application server obtains the new status of user consent can be determined by the specific implementation of the particular UE. Again, when user consent is collected at the UE's 3GPP layer, modification / revocation can also be sent through the 3GPP layer.

[0146] For example, a UE such as UE 106 can send a user's consent modification / revocation request to an application server through the UE's application layer. The application server can then send the update to the user's consent to the MNO network via an interface with the NEF. For example, as... Figure 8As shown, the edge enabler server (EES) 844 of the edge data network 832 can serve edge applications running on the edge data network, such as edge applications running on the edge application server 834 via the edge-3 interface. EES 844 can be configured to expose application programming interfaces (APIs) such as location services and / or UE identifiers (e.g., Common Public Subscription Identifier (GPSI), and other APIs) to EAS 834. Furthermore, Public Land Mobile Network (PLMN) network functions (NFs) can also be configured to expose APIs to EES 844. Therefore, if EAS 834 requests user consent to use sensitive information from the PLMN (e.g., 3GPP CN 812) for services, such as location, GPSI, etc., and the services are provided to UE 106, user consent can be collected from the user. Then, when UE 106 (e.g., the user) needs to modify and / or revoke user consent, UE 106 can send a user consent modification request to EAS 834 via application data traffic 850. For example, application client 816 executing on UE 106 can send a user consent modification request to EAS 834 via application data traffic 850. 834 may subsequently deliver a user consent modification request (which may, for example, modify and / or revoke previously provided user consent) to EES 844, for example, via the Edge-3 interface. Furthermore, EES 844 may deliver the user consent modification request to the Evolved Charging Suite (ECS) executing on an edge configuration server such as Edge Configuration Server 854 via the Edge-6 interface, and to the UE 106's home PLMN (HPLMN) (e.g., 3GPP CN 812) via the Edge-2 interface. Additionally, EES 844 may interact with the Edge Enabler Client 826 via the Edge-1 interface. Furthermore, Edge Configuration Server 854 may interact with the home PLMN via the Edge-8 interface and with the Edge Enabler Client 826 via the Edge-4 interface. It should be noted that EES 844 may also maintain interaction with the HPLMN, for example, via the Edge-2 interface, and with the UE via the Edge-1 interface. The interaction is performed on the edge-enabled client 826 at 106. It should also be noted that the edge-enabled client 826 can interact with the application client 816 via the edge-5 interface. Additionally, UE 106 can be considered as data body 800, where the HPLMN (e.g., 3GPP CN 812) can be considered as part of the data controller 810. Furthermore, the edge network 832 and EES 844 can be considered as part of the data controller 820, which includes the data processor 830, as shown in the figure.

[0147] It should be noted that the above mechanism can be applied to MEC and other use cases. It should also be noted that Edge-3 and Edge-6 are in Edge Network 832, while Edge-2 is not. Therefore, for Edge-2, the Nnef_ParameterProvision_Update service operation (e.g., according to Section 5.2.6.4.2 of 3GPP TS23.502) can be used for user consent modification request transmission. For example, in some implementations, Nnef_ParameterProvision_Update can be modified to include user consent updates, such as those including other UE-related information such as expected UE behavior, network configuration parameters, and location privacy indication parameters.

[0148] In some implementations, the network (e.g., a network entity) can trigger a user consent update process. For example, a Policy Control Function (PCF) can initiate a UE configuration update to trigger the user consent update process. The UE configuration update process can be used to provide UE Routing Policy (URSP) rules, which the UE can use to establish an appropriate Protocol Data Unit (PDU) session before edge access stratum (AS) discovery. Therefore, the UE configuration update process can be (re)used to deliver user consent update requests from the core network (e.g., from the PCF).

[0149] For example, Figure 9 An example of signaling used by a PCF, according to some implementation schemes, to initiate a UE configuration update to trigger a user consent update process is shown. Among other things, Figure 9 The signaling shown can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown may be executed concurrently in a different order than that shown, or may be omitted. Additional signaling may also be executed as needed. As shown in the figure, the signaling can follow the following flow.

[0150] At 902, a PCF such as PCF 628 may determine to update the UE policy and / or update the user consent status based on triggering conditions (such as UE policy and / or the user consent status of the UE, such as UE 106). Triggering conditions may include initial registration, registration with the 5GS when the UE moves from an evolved packet system (EPS) to a 5G system (5GS), and / or the need to update the UE policy.

[0151] In response to triggering conditions, the PCF may send a User Consent Update Request Message 904 to the AMF, such as AM 605. In some cases, the User Consent Update Request Message 904 may invoke the Namf_Communication_N1N2MessageTransfer service operation provided by the AMF. The User Consent Update Request Message 904 may include a Subscription Permanent Identifier (SUPI), a UE policy container, and / or a User Consent Update Request. It should be noted that the User Consent Update Request Message 904 may indicate whether the User Consent Update Request is for a specific service (such as MEC) or for the entire set of sensitive information.

[0152] At 906, the AMF can transmit the UE policy container and / or user consent update request received in the user consent update request message 904 (transparently) to the UE via a network-triggered service request.

[0153] Additionally or alternatively, if and / or when the UE is in a CM connected state via 3GPP access and / or non-3GPP access, the AMF may transparently transmit the UE policy container (e.g., including UE access selection and / or PDU session selection related policy information) received from the PCF and / or the user consent update request received from the PCF to the UE via UE policy delivery message 908.

[0154] Then, the UE can update the UE policy provided by the PCF and can send the user consent update to the AMF via the UE policy delivery response message 910.

[0155] The AMF can then forward the UE's response (including the user consent update) to the PCF via the User Consent Update Request Response Message 912. In some implementations, the AMF can forward the UE's response (including the user consent update) to the PCF using the Namf_Communication_N1MessageNotify service.

[0156] For example, the network's SMF can initiate a PDU session modification to trigger a user consent update process. The PDU session modification process (e.g., as defined in section 4.3.3.2 of 3GPP TS23.502) is used by the SMF to instruct the UE to rediscover the EAS based on information provided by the AF or based on the SMF's local configuration. However, since the UE will initiate a new PDU session establishment process after this PDU session modification process, this process can be used to allow the user consent update. In some implementations, the user consent request may be included in (e.g., carried in) the Nsmf_PDUSession_UpdateSMContext response during the PDU session modification process. In some implementations, the user consent update process may be initiated periodically by the core network or application server. The period can be configurable. Alternatively and / or additionally, the user consent update process may be initiated by the network on demand, such as based on events and / or triggers.

[0157] For example, Figure 10 An example of signaling used by an SMF (System Configuration Function) according to some implementation schemes to initiate a UE configuration update to trigger a user consent update process is shown. Among other things, Figure 10 The signaling shown can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown may be executed concurrently in a different order than that shown, or may be omitted. Additional signaling may also be executed as needed. As shown in the figure, the signaling can follow the following flow.

[0158] At 1002, due to UE mobility (e.g., the mobility of UE 106), SMFs such as SMF 606 can trigger L-PSA insertion, modification, and / or removal of the PDU session.

[0159] At 1004, the AF is notified that user plane management events such as AF 624 can trigger EAS relocation. Note whether and / or when the AF triggers EAS. Additionally, the UE can trigger user consent modification / revocation via the application layer for relocation and / or UE-related updates, such as due to EAS load balancing or maintenance. The UE can also inform the SMF of relevant information. The SMF can then execute a PDU session modification procedure for a network request as defined in Clause 4.3.3.2 of 3GPP TS23.502 and further described below with reference to signaling 1006 to 1024. Note that the signaling described below may include modifications to the PDU session modification procedure as defined in Clause 4.3.3.2 of 3GPP TS23.502. In some cases, the SMF may decide to instruct the UE to rediscover EAS based on information provided by the AF and / or based on the SMF's local configuration. Therefore, the SMF can send a PDU session modification command (EAS rediscovery indication, [impact field], user consent update request) to the UE. In some implementations, the impact field can be used to identify which EASs need to be rediscovered. Therefore, if and / or when the impact field is not included, it can indicate that all EASs associated with the PDU session need to be rediscovered. Note that if and / or when EAS rediscovery is only used for user consent updates, the "EAS Rediscovery Indication" and "impact field" can be the same and / or set to a fixed value (e.g., 0). Additionally, if and / or when EAS rediscovery is only used for regular discovery, the "User Consent Update Request" field can be set to empty. Furthermore, note that the user consent update request can be carried along with EAS relocation, for example, sent whenever an EAS relocation occurs. In at least some implementations, the user consent update request can also be sent according to the mobile network operator (MNO) policy.

[0160] continue Figure 10 In signaling at 1006, the SMF can utilize the AMF, such as AMF 605, to perform PDU update message transmission. For example, for modifications requested by the SMF, the SMF can invoke the Namf_Communication_N1N2MessageTransfer service. The SMF can send various information as part of the service to the AMF, such as information currently defined by Clause 4.3.3.2 of 3GPP TS23.502. Furthermore, as part of the service, the SMF can send user consent update requests to the AMF.

[0161] The AMF may then send the N2 message 1008 to a radio access network (RAN) such as (R)AN 604, which may include sending the N2 message to a base station such as base station 604. This message may include a user consent update request and information as defined in Clause 4.3.3.2 of 3GPP TS23.502.

[0162] At point 1010, the RAN can issue UE access network (AN) specific signaling exchanges related to information received from the SMF. For example, RRC connection reconfiguration may occur. Additionally, the UE can update user consent.

[0163] Additionally, the RAN may send an N2 response message 1012 to the AMF, which may include various information as defined in Clause 4.3.3.2 of 3GPP TS 23.502. In at least some implementations, the N2 response message may include user consent to the update.

[0164] At point 1014, the AMF can utilize the SMF to perform PDU update message transmission. The AMF can send various information to the SMF, including information as defined in Clause 4.3.3.2 of 3GPP TS23.502. Furthermore, in at least some implementations, the PDU update message may include user consent to the update.

[0165] At position 1016, SMF can utilize UPFs such as UPF 608 to perform the N4 modification process.

[0166] In addition, the UE can confirm the PDU session modification command by sending a PDU modification confirmation message 1018 to the RAN. The PDU modification confirmation message 1018 can be a NAS message that may include user consent to the update and other information.

[0167] The RAN can forward the PDU modification confirmation message to the AMF via the N2 NAS update message 1020. The N2 NAS update message 1020 may include user consent to the update and other information.

[0168] At position 1022, the AMF can forward the user consent update to the SMF. The user consent update can be included in the N1 SM container, which may also include user location information received from the RAN.

[0169] At 1024, the AMF can utilize UPFs such as UPF 608 to perform the N4 modification process, for example, to use a UPF to update user consent.

[0170] For example, Figure 11 An example of signaling used by a UE to initiate a UE configuration update to trigger a user consent update process, according to some implementation schemes, is shown. Among other devices, Figure 11The signaling shown can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown may be executed concurrently in a different order than that shown, or may be omitted. Additional signaling may also be executed as needed. As shown in the figure, the signaling can follow the following flow.

[0171] At 1102, a UE such as UE 106 can initiate a PDU session modification procedure by transmitting a NAS message to an access network (AN) such as radio AN ((R)AN) 604. This may include sending a NAS message to a base station such as base station 604. The NAS message may include various information as defined in Clause 4.3.3.2 of 3GPP TS23.502. Furthermore, the NAS message may include a user consent update request.

[0172] At 1104, the AN can forward NAS messages to the AMF, such as AMF 605. NAS messages may include various information as defined in Clause 4.3.3.2 of 3GPP TS 23.502. Additionally, NAS messages may include user consent update requests. In some implementations, NAS messages may be forwarded to the AMF along with indications of user location information.

[0173] At 1106, the SMF can utilize the AMF, such as AMF 605, to perform PDU update message transmission. For example, the SMF can receive various information from the AMF, such as information currently defined by Clause 4.3.3.2 of 3GPP TS23.502. Furthermore, as part of the service, the SMF can receive user consent update requests from the AMF.

[0174] At 1107, the SMF can report certain subscription events to the PCF, such as PCF 628, by executing an SMF-initiated SM policy association modification process.

[0175] At 1108, for modifications initiated by the UE (and / or AN), the SMF can respond to the AMF via a PDU response such as the Nsmf_PDUSession_UpdateSMContext response. This response may include confirmation of user consent to the update.

[0176] The AMF may then send the N2 message 1109 to a radio access network (RAN) such as (R)AN 604, which may include sending the N2 message to a base station such as base station 604. This message may include a user consent update request and information as defined in Clause 4.3.3.2 of 3GPP TS23.502.

[0177] At 1110, the RAN can issue UE access network (AN) specific signaling exchanges related to information received from the SMF. For example, RRC connection reconfiguration may occur. Additionally, the UE can update user consent.

[0178] Additionally, the RAN may send an N2 response message 1112 to the AMF, which may include various information as defined in Clause 4.3.3.2 of 3GPP TS 23.502. In at least some implementations, the N2 response message may include user consent to the update.

[0179] At point 1114, the AMF can utilize the SMF to perform PDU update message transmission. The AMF can send various information to the SMF, including information as defined in Clause 4.3.3.2 of 3GPP TS23.502. Furthermore, in at least some implementations, the PDU update message may include user consent to the update.

[0180] At 1116, SMF can utilize UPFs such as UPF 608 to perform the N4 modification process.

[0181] In addition, the UE can confirm the PDU session modification command by sending a PDU modification confirmation message 1118 to the RAN. The PDU modification confirmation message 1118 can be a NAS message that may include user consent to the update and other information.

[0182] The RAN can forward the PDU modification confirmation message to the AMF via N2 NAS update message 1120. N2 NAS update message 1120 may include user consent to the update and other information.

[0183] At point 1122, the AMF can forward the user consent update to the SMF. The user consent update can be included in the N1 SM container, which may also include user location information received from the RAN.

[0184] At 1124, the AMF can utilize UPFs such as UPF 608 to perform the N4 modification process, for example, to use a UPF to update user consent.

[0185] Figure 12A , Figure 12B , Figure 12C , Figure 13 , Figure 14 and Figure 15 Examples of various methods for obtaining user consent to modifications are shown according to some implementation schemes. The methods illustrated in these figures can be used in conjunction with any system, method, or device shown in the figures, as well as other devices. In various implementations, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed.

[0186] Go to Figure 12A , Figure 12A An example of a method for user consent modification initiated by a UE, according to some implementation schemes, is shown. Figure 12A The method shown can be used in conjunction with any system, method, or device shown in the figure, as well as other devices. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown in the figure, the method operates as follows.

[0187] At 1202, a user equipment (UE), such as UE 106, may determine that user consent needs to be updated. This determination may be based on various factors, such as indications of changes in user preferences, periodic updates of user preferences, and / or various other factors. User consent may be associated with edge computing (MEC).

[0188] At 1204, the UE can transmit a user consent modification request via its application layer to an edge application server (such as EAS 834) of the network (e.g., an edge data network, such as edge network 832). The user consent modification request can be carried in the application data traffic. In some implementations, the user consent modification request can be indicated via the Nnef_ParameterProvision_Update service operation. In some implementations, the user consent modification request is a revocation of user consent. In some implementations, the edge application server can deliver the request to an edge enabler server.

[0189] In some implementations, the UE can receive confirmation of user consent to the update from the edge enabler server. This confirmation can be received via the edge-4 interface with the edge enabler server.

[0190] Go to Figure 12B , Figure 12B An example of another method for user consent modification initiated by the UE, according to some implementation schemes, is shown. Figure 12B The method shown can be used in conjunction with any system, method, or device shown in the figure, as well as other devices. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown in the figure, the method operates as follows.

[0191] At 1212, an Edge Application Server (EAS), such as EAS 834, can receive a user consent modification request from a UE, such as UE 106. The user consent modification request may be associated with edge computing (MEC). The user consent modification request may be carried in application data traffic. In some implementations, user consent modification may be a revocation of user consent.

[0192] At 1214, EAS can deliver (e.g., send and / or transmit) a user consent modification request to an Edge Enabler Server (EES) such as EES 844. The user consent modification request can be indicated via the Nnef_ParameterProvision_Update service operation. Furthermore, this request can be delivered via the Edge-3 interface with the Edge Enabler Server.

[0193] Go to Figure 12C , Figure 12C An example of yet another method for user consent modification initiated by the UE, according to some implementation schemes, is shown. Figure 12C The method shown can be used in conjunction with any system, method, or device shown in the figure, as well as other devices. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown in the figure, the method operates as follows.

[0194] At 1222, an edge enabler server (EES) such as EES 844 can receive a user consent modification request for a UE such as UE 106 from an edge application server such as EAS 834. User consent may be associated with edge computing (MEC). Furthermore, the EAS can receive user consent modification requests in application data traffic. User consent modification can be a revocation of user consent.

[0195] At point 1224, the EES can notify the Home Public Land Mobile Network (HPLMN) associated with the UE of the user's consent to the modification. In some implementations, the notification to the HPLMMN associated with the UE can be made via the Edge-2 interface.

[0196] In some implementations, the EES may deliver (e.g., send and / or transmit) a request to an edge configuration server (ECS), such as an ECS 854. This request may be delivered via an edge-6 interface with the edge configuration server.

[0197] Go to Figure 13 , Figure 13 Examples of methods for user consent modifications initiated by the AMF, according to some implementation schemes, are shown. Among other things, Figure 13The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0198] At 1302, the network's AMF, such as AMF 605, may receive a request to update the user consent state from the network's PCF, such as PCF 628. In some embodiments, the request to update the user consent state may be based at least in part on any, any combination, and / or all (e.g., one or more and / or at least one) of the following: initial registration, registration with the 5GS when the UE moves from the Evolved Packet Core (EPS) system to the 5GS system, and / or a request to update the UE policy. In some embodiments, the user consent state may be associated with edge computing (MEC).

[0199] At 1304, the AMF may transmit a request to the UE, such as UE 106, to update the user consent state. In some implementations, the UE may be in a CM connected state via either 3GPP access (e.g., cellular access) or non-3GPP access (e.g., non-cellular access).

[0200] At 1306, the AMF can receive an updated user consent status from the UE. In some implementations, the updated user consent status may be indicated by Namf_Communication_N1MessageNotify. In some implementations, the updated user consent status may indicate the revocation of user consent.

[0201] At point 1308, the AMF can forward the updated user consent status to the PCF.

[0202] Go to Figure 14 , Figure 14 Examples of methods for user consent modifications initiated by an SMF, according to some implementation schemes, are shown. Among other things, Figure 14 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0203] At 1402, network SMFs such as SMF 606 can trigger (e.g., initiate) EAS relocation.

[0204] At position 1404, the SMF can receive a user consent modification request from an AF on the network, such as AF 624. In some implementations, the user consent modification request may be a request to revoke the user's consent.

[0205] At 1406, the SMF may implement (e.g., execute) a PDU session modification process to update user consent. In some embodiments, the PDU session modification command sent by the SMF as part of the PDU session modification process may include a user consent update request field. In some embodiments, the PDU session modification command sent by the SMF as part of the PDU session modification process may include an impact field. The impact field may identify one or more EASs to be rediscovered. In some embodiments, the PDU session modification command sent by the SMF as part of the PDU session modification process may indicate that all EASs will be rediscovered. In some embodiments, the PDU session modification command sent by the SMF as part of the PDU session modification process may include an EAS rediscovery indication field and an impact field, and EAS rediscovery may be user consent update only if and / or when the EAS rediscovery indication field and the impact field are set to the same value. In some implementations, the PDU session modification command sent by the SMF as part of the PDU session modification process may include an EAS rediscovery indication field and an effect field, and EAS rediscovery may be a user-consent-only update if and / or when the EAS rediscovery indication field and effect field are set to fixed values. In some implementations, the fixed value may be 0.

[0206] Go to Figure 15 , Figure 15 An example of another method for modifying user consent initiated by an SMF, according to some implementation schemes, is shown. Among other devices, Figure 15 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0207] At 1502, the network's SMF, such as SMF 606, can receive a user consent update request from the network's AMF, such as AMF 605, via a PDU update message. In some implementations, the user consent update request can be triggered by a UE associated with the user consent, such as UE 106.

[0208] At position 1504, the SMF may send a PDU response to the AMF that may include confirmation of user consent to the update. The PDU response may be an Nsmf_PDUSession_UpdateSMContext response.

[0209] At position 1506, the SMF can receive user consent updates from the AMF. In some implementations, the user consent update may be a revocation of user consent. The user consent update may be received via the N1 SM container. In some implementations, user location information may be received along with the user consent update.

[0210] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0211] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0212] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any method embodiment of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0213] In some implementations, the device (e.g., UE 106) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and the processor is configured to read from and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method implementations described herein (or any combination of method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets). The device may be implemented in any of a variety of forms.

[0214] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.

[0215] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A user equipment device (UE), comprising: at least one antenna; at least one radio, wherein the at least one radio is configured to perform cellular communication using at least one radio access technology (RAT); one or more processors coupled to the at least one radio, wherein the one or more processors and the at least one radio are configured to perform communications; wherein the one or more processors are configured to cause the UE to: determine that a user consent needs to be updated; and transmit, via an application client running on the UE, a user consent modification request to an edge application server over application data traffic, wherein the edge application server delivers the request to an edge enabler server via an edge-3 interface; and receive, via an edge enabler client running on the UE, confirmation of the updated user consent from the edge enabler server over an edge-4 interface.

2. The UE of claim 1, wherein the user consent is associated with edge computing (MEC).

3. The UE of claim 1, wherein the user consent modification is a revocation of the user consent.

4. The UE of claim 1, wherein the user consent modification request is indicated via an Nnef ParameterProvision_Update service operation.

5. A method performed by a user equipment device (UE), comprising: determining that a user consent needs to be updated; and transmitting, via an application client running on the UE, a user consent modification request to an edge application server over application data traffic, wherein the edge application server delivers the request to an edge enabler server via an edge-3 interface; and receiving, via an edge enabler client running on the UE, confirmation of the updated user consent from the edge enabler server over an edge-4 interface.

6. The method of claim 5, wherein the user consent is associated with edge computing (MEC).

7. The method of claim 5, wherein the user consent modification is a revocation of the user consent.

8. The method of claim 5, wherein the user consent modification request is indicated via an Nnef ParameterProvision_Update service operation.

9. A non-transitory computer-readable memory medium storing program instructions executable by processing circuitry to cause a user equipment device (UE) to perform the method of any of claims 5-8.

Images