Patent Description:
Wireless communication systems are rapidly growing in usage. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS), and are capable of operating sophisticated applications that utilize these functionalities.

Long Term Evolution (LTE) is currently the technology of choice for the majority of wireless network operators worldwide, providing mobile broadband data and high-speed Internet access to their subscriber base. LTE was first proposed in <NUM> and was first standardized in <NUM>. Since then, as usage of wireless communication systems has expanded exponentially, demand has risen for wireless network operators to support a higher capacity for a higher density of mobile broadband users. Thus, in <NUM> study of a new radio access technology began and, in <NUM>, a first release of Fifth Generation New Radio (<NUM> NR) was standardized.

<NUM>-NR, also simply referred to as NR, provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to-device, ultra-reliable, and massive machine type communications with lower latency and/or lower battery consumption. Further, NR may allow for more flexible UE scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of <NUM>-NR to take advantage of higher throughputs possible at higher frequencies. <CIT> discloses transmitting a user consent update request to the network via an edge enabler client, the network is implemented as including an edge computer server.

Various aspects relate to wireless communications, and more particularly to apparatuses, systems, and methods for revocation and/or modification of user consent in Edge Computing (MEC), e.g., in <NUM> NR systems and beyond.

For example, in some embodiments, a user equipment device (UE), such as UE <NUM>, may be configured to determine that user consent needs to be updated. The determination may be based on various factors, such as an indicated change in user preference, a periodic update of user preference, and/or various other factors. The user consent may be associated with Edge Computing (MEC). Additionally, the UE may be configured to transmit, via an application layer of the UE, a user consent modification request to an edge application server of a network, e.g., of an edge data network. The user consent modification request may be carried in application data traffic. In some embodiments, the user consent modification request may be indicated via an Nnef_ParameterProvision_Update service operation. In some embodiments, the user consent modification request is indicated via an Nnef_ParameterProvision Update service operation.

As another example, an edge application server (EAS), such as EAS <NUM>, may be configured to receive, from a UE, a user consent modification request. The user consent modification request may be associated with MEC. The user consent modification request may be carried in application data traffic. Additionally, the EAS may be configured to deliver (e.g., send and/or transmit), to an edge enabler server (EES), the user consent modification request. The user consent modification request may be indicated via an Nnef_ParameterProvision Update service operation.

As a further example, an edge enabler server (EES), such as EES <NUM>, may be configured to receive, from an EAS, a user consent modification request for a UE. The user consent may be associated with MEC. Additionally, the EES may be configured to notify a home public land mobile network (HPLMN) associated with the UE of a user consent modification.

As a further example, a network entity, such as an AMF of a network, may be configured to receive, from a PCF of the network, a request to update a user consent status. The AMF may be configured to transfer, to a UE the request to update the user consent status. Further, the AMF may be configured to receive, from the UE, an updated user consent status and forward, to the PCF, the updated user consent status.

As yet a further example, a network entity, such as an SMF of a network, may be configured to trigger (e.g., initiate) an EAS relocation and may receive, from an AF of the network, a user consent modification request. Additionally, the SMF may be configured to execute (e.g., perform) a PDU session modification procedure to update user consent. As another example, a network entity, such as SMF of a network, may be configured to may receive, from an AMF of the network, a user consent update request via a PDU update message. Additionally, the SMF may be configured to send, to the AMF, a PDU response that may include a user consent update acknowledge and receive, from the AMF, a user consent update. The PDU response may be a Nsmf_PDUSession_UpdateSMContext response.

The techniques described herein may be implemented in and/or used with a number of different types of devices, including but not limited to unmanned aerial vehicles (UAVs), unmanned aerial controllers (UACs), a UTM server, base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, and any of various other computing devices.

Accordingly, it will be appreciated that the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter described herein in any way.

In the following, the invention is best understood in view of <FIG>. The remaining embodiments, aspects, or examples are included in order to help the reader better understand the invention.

While the features described herein may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to be limiting to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims.

Various components may be described as "configured to" perform a task or tasks.

The communication area (or coverage area) of the base station may be referred to as a "cell. " The base station 102A and the UEs <NUM> may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), <NUM> new radio (<NUM> NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if the base station 102A is implemented in the context of LTE, it may alternately be referred to as an 'eNodeB' or 'eNB'. Note that if the base station 102A is implemented in the context of <NUM> NR, it may alternately be referred to as 'gNodeB' or 'gNB'.

In some embodiments, base station 102A may be a next generation base station, e.g., a <NUM> New Radio (<NUM> NR) base station, or "gNB". In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs).

Note that a UE <NUM> may be capable of communicating using multiple wireless communication standards. For example, the UE <NUM> may be configured to communicate using a wireless networking (e.g., Wi-Fi) and/or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) 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, <NUM> NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). The UE <NUM> may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., 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, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

<FIG> illustrates user equipment <NUM> (e.g., one of the devices 106A through 106N) in communication with a base station <NUM> and an access point <NUM>, according to some embodiments. The UE <NUM> may be a device with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a handheld device, a computer or a tablet, or virtually any type of wireless device.

The UE <NUM> may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE <NUM> may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE/LTE-Advanced, or <NUM> NR using a single shared radio and/or GSM, LTE, LTE-Advanced, or <NUM> NR using the single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE <NUM> may share one or more parts of a receive and/or transmit chain between multiple wireless communication technologies, such as those discussed above.

The network port <NUM> may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices <NUM>, access to the telephone network as described above in <FIG> and <FIG>.

<FIG> illustrates an example block diagram of a server <NUM>, according to some embodiments. It is noted that the server of <FIG> is merely one example of a possible server. As shown, the server <NUM> may include processor(s) <NUM> which may execute program instructions for the server <NUM>.

The server <NUM> may be configured to provide a plurality of devices, such as base station <NUM>, UE devices <NUM>, and/or UTM <NUM>, access to network functions, e.g., as further described herein.

In some embodiments, the server <NUM> may be part of a radio access network, such as a <NUM> New Radio (<NUM> NR) radio access network. In some embodiments, the server <NUM> may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.

As described further subsequently herein, the server <NUM> may include hardware and software components for implementing or supporting implementation of features described herein. The processor <NUM> of the server <NUM> may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition) the processor <NUM> of the server <NUM>, in conjunction with one or more of the other components <NUM>, <NUM>, and/or <NUM> may be configured to implement or support implementation of part or all of the features described herein.

<FIG> illustrates an example simplified block diagram of a communication device <NUM>, according to some embodiments. It is noted that the block diagram of the communication device of <FIG> is only one example of a possible communication device. According to embodiments, communication device <NUM> 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, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and/or a combination of devices, among other devices. As shown, the communication device <NUM> may include a set of components <NUM> configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOC), which may include portions for various purposes. Alternatively, this set of components <NUM> may be implemented as separate components or groups of components for the various purposes. The set of components <NUM> may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device <NUM>.

Note that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC(s) cards <NUM>, one or more eUICCs, one or more eSIMs, either removable or embedded, etc. In some embodiments, the UE <NUM> 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 may be embedded, e.g., may be soldered onto a circuit board in the UE <NUM>, or each SIM <NUM> may be implemented as a removable smart card. Thus, the SIM(s) may be one or more removable smart cards (such as UICC cards, which are sometimes referred to as "SIM cards"), and/or the SIMs <NUM> may be one or more embedded cards (such as embedded UICCs (eUICCs), which are sometimes referred to as "eSIMs" or "eSIM cards"). In some embodiments (such as when the SIM(s) include an eUICC), one or more of the SIM(s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM(s) may execute multiple SIM applications. Each of the SIMs may include components such as a processor and/or a memory; instructions for performing SIM/eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the UE <NUM> may include a combination of removable smart cards and fixed/non-removable smart cards (such as one or more eUICC cards that implement eSIM functionality), as desired. For example, the UE <NUM> may comprise two embedded SIMs, two removable SIMs, or a combination of one embedded SIMs and one removable SIMs. Various other SIM configurations are also contemplated.

As noted above, in some embodiments, the UE <NUM> may include two or more SIMs. The inclusion of two or more SIMs in the UE <NUM> may allow the UE <NUM> to support two different telephone numbers and may allow the UE <NUM> to communicate on corresponding two or more respective networks. For example, a first SIM may support a first RAT such as LTE, and a second SIM <NUM> support a second RAT such as <NUM> NR. Other implementations and RATs are of course possible. In some embodiments, when the UE <NUM> comprises two SIMs, the UE <NUM> may support Dual SIM Dual Active (DSDA) functionality. The DSDA functionality may allow the UE <NUM> to be simultaneously connected to two networks (and use two different RATs) at the same time, or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks. The DSDA functionality may also allow the UE <NUM> to simultaneously receive voice calls or data traffic on either phone number. In certain embodiments the voice call may be a packet switched communication. In other words, the voice call may be received using voice over LTE (VoLTE) technology and/or voice over NR (VoNR) technology. In some embodiments, the UE <NUM> may support Dual SIM Dual Standby (DSDS) functionality. The DSDS functionality may allow either of the two SIMs in the UE <NUM> to be on standby waiting for a voice call and/or data connection. In DSDS, when a call/data is established on one SIM, the other SIM is no longer active. In some embodiments, DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUICC) that executes multiple SIM applications for different carriers and/or RATs.

As shown, the SOC <NUM> may include processor(s) <NUM>, which may execute program instructions for the communication device <NUM> and display circuitry <NUM>, which may perform graphics processing and provide display signals to the display <NUM>. The processor(s) <NUM> may also be coupled to memory management unit (MMU) <NUM>, which may be configured to receive addresses from the processor(s) <NUM> and translate those addresses to locations in memory (e.g., memory <NUM>, read only memory (ROM) <NUM>, NAND flash memory <NUM>) and/or to other circuits or devices, such as the display circuitry <NUM>, short to medium range wireless communication circuitry <NUM>, cellular communication circuitry <NUM>, connector I/F <NUM>, and/or display <NUM>. The MMU <NUM> may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU <NUM> may be included as a portion of the processor(s) <NUM>.

As noted above, the communication device <NUM> may be configured to communicate using wireless and/or wired communication circuitry. The communication device <NUM> may be configured to perform methods for revocation and/or modification of user consent in MEC, e.g., in <NUM> NR systems and beyond, as further described herein.

As described herein, the communication device <NUM> may include hardware and software components for implementing the above features for a communication device <NUM> to communicate a scheduling profile for power savings to a network. The processor <NUM> of the communication device <NUM> may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor <NUM> may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor <NUM> of the communication device <NUM>, in conjunction with one or more of the other components <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> may be configured to implement part or all of the features described herein.

Further, as described herein, cellular communication circuitry <NUM> and short to medium range wireless communication circuitry <NUM> may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry <NUM> and, similarly, one or more processing elements may be included in short to medium range wireless communication circuitry <NUM>. Thus, cellular communication circuitry <NUM> may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry <NUM>. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry <NUM>. Similarly, the short to medium range wireless communication circuitry <NUM> may include one or more ICs that are configured to perform the functions of short to medium range wireless communication circuitry <NUM>. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short to medium range wireless communication circuitry <NUM>.

<FIG> illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of <FIG> is only one example of a possible cellular communication circuit. According to embodiments, cellular communication circuitry <NUM>, which may be cellular communication circuitry <NUM>, may be included in a communication device, such as communication device <NUM> described above. As noted above, communication device <NUM> 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 and/or a combination of devices, among other devices.

The cellular communication circuitry <NUM> may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435a-b and <NUM> as shown (in <FIG>). In some embodiments, cellular communication circuitry <NUM> may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly. For example, as shown in <FIG>, cellular communication circuitry <NUM> may include a modem <NUM> and a modem <NUM>. Modem <NUM> may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem <NUM> may be configured for communications according to a second RAT, e.g., such as <NUM> NR.

In some embodiments, the cellular communication circuitry <NUM> may be configured to perform methods for revocation and/or modification of user consent in MEC, e.g., in <NUM> NR systems and beyond, as further described herein.

As described herein, the modem <NUM> may include hardware and software components for implementing the above features or for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described herein. The processors <NUM> may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor <NUM> may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor <NUM>, in conjunction with one or more of the other components <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> may be configured to implement part or all of the features described herein.

As described herein, the modem <NUM> may include hardware and software components for implementing the above features for communicating a scheduling profile for power savings to a network, as well as the various other techniques described herein. The processors <NUM> may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor <NUM> may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor <NUM>, in conjunction with one or more of the other components <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> may be configured to implement part or all of the features described herein.

In some embodiments, the <NUM> core network (CN) may be accessed via (or through) a cellular connection/interface (e.g., via a 3GPP communication architecture/protocol) and a non-cellular connection/interface (e.g., a non-3GPP access architecture/protocol such as Wi-Fi connection). <FIG> illustrates an example of a <NUM> network architecture that incorporates both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the <NUM> CN, according to some embodiments. As shown, a user equipment device (e.g., such as UE <NUM>) may access the <NUM> CN through both a radio access network (RAN, e.g., such as gNB <NUM>, which may be a base station <NUM>) and an access point, such as AP <NUM>. The AP <NUM> may include a connection to the Internet <NUM> as well as a connection to a non-3GPP inter-working function (N3IWF) <NUM> network entity. The N3IWF may include a connection to a core access and mobility management function (AMF) <NUM> of the <NUM> CN. The AMF <NUM> may include an instance of a <NUM> mobility management (<NUM> MM) function associated with the UE <NUM>. In addition, the RAN (e.g., gNB <NUM>) may also have a connection to the AMF <NUM>. Thus, the <NUM> CN may support unified authentication over both connections as well as allow simultaneous registration for UE <NUM> access via both gNB <NUM> and AP <NUM>. As shown, the AMF <NUM> may include one or more functional entities associated with the <NUM> CN (e.g., network slice selection function (NSSF) <NUM>, short message service function (SMSF) <NUM>, application function (AF) <NUM>, unified data management (UDM) <NUM>, policy control function (PCF) <NUM>, and/or authentication server function (AUSF) <NUM>). Note that these functional entities may also be supported by a session management function (SMF) 606a and an SMF 606b of the <NUM> CN. The AMF <NUM> may be connected to (or in communication with) the SMF 606a. Further, the gNB <NUM> may in communication with (or connected to) a user plane function (UPF) 608a that may also be communication with the SMF 606a. Similarly, the N3IWF <NUM> may be communicating with a UPF 608b that may also be communicating with the SMF 606b. Both UPFs may be communicating with the data network (e.g., DN 610a and 610b) and/or the Internet <NUM> and Internet Protocol (IP) Multimedia Subsystem/IP Multimedia Core Network Subsystem (IMS) core network <NUM>.

<FIG> illustrates an example of a <NUM> network architecture that incorporates both dual 3GPP (e.g., LTE and <NUM> NR) access and non-3GPP access to the <NUM> CN, according to some embodiments. As shown, a user equipment device (e.g., such as UE <NUM>) may access the <NUM> CN through both a radio access network (RAN, e.g., such as gNB <NUM> or eNB <NUM>, which may be a base station <NUM>) and an access point, such as AP <NUM>. The AP <NUM> may include a connection to the Internet <NUM> as well as a connection to the N3IWF <NUM> network entity. The N3IWF may include a connection to the AMF <NUM> of the <NUM> CN. The AMF <NUM> may include an instance of the <NUM> MM function associated with the UE <NUM>. In addition, the RAN (e.g., gNB <NUM>) may also have a connection to the AMF <NUM>. Thus, the <NUM> CN may support unified authentication over both connections as well as allow simultaneous registration for UE <NUM> access via both gNB <NUM> and AP <NUM>. In addition, the <NUM> CN may support dual-registration of the UE on both a legacy network (e.g., LTE via eNB <NUM>) and a <NUM> network (e.g., via gNB <NUM>). As shown, the eNB <NUM> may have connections to a mobility management entity (MME) <NUM> and a serving gateway (SGW) <NUM>. The MME <NUM> may have connections to both the SGW <NUM> and the AMF <NUM>. In addition, the SGW <NUM> may have connections to both the SMF 606a and the UPF 608a. As shown, the AMF <NUM> may include one or more functional entities associated with the <NUM> CN (e.g., NSSF <NUM>, SMSF <NUM>, AF <NUM>, UDM <NUM>, PCF <NUM>, and/or AUSF <NUM>). Note that UDM <NUM> may also include a home subscriber server (HSS) function and the PCF may also include a policy and charging rules function (PCRF). Note further that these functional entities may also be supported by the SMF606a and the SMF 606b of the <NUM> CN. The AMF <NUM> may be connected to (or in communication with) the SMF 606a. Further, the gNB <NUM> may in communication with (or connected to) the UPF 608a that may also be communication with the SMF 606a. Similarly, the N3IWF <NUM> may be communicating with a UPF 608b that may also be communicating with the SMF 606b. Both UPFs may be communicating with the data network (e.g., DN 610a and 610b) and/or the Internet <NUM> and IMS core network <NUM>.

Note that in various embodiments, one or more of the above-described network entities may be configured to perform methods to improve security checks in a <NUM> NR network, including mechanisms for revocation and/or modification of user consent in MEC, e.g., in <NUM> NR systems and beyond, e.g., as further described herein.

<FIG> illustrates an example of a baseband processor architecture for a UE (e.g., such as UE <NUM>), according to some embodiments. The baseband processor architecture <NUM> described in <FIG> may be implemented on one or more radios (e.g., radios <NUM> and/or <NUM> described above) or modems (e.g., modems <NUM> and/or <NUM>) as described above. As shown, the non-access stratum (NAS) <NUM> may include a <NUM> NAS <NUM> and a legacy NAS <NUM>. The legacy NAS <NUM> may include a communication connection with a legacy access stratum (AS) <NUM>. The <NUM> NAS <NUM> may include communication connections with both a <NUM> AS <NUM> and a non-3GPP AS <NUM> and Wi-Fi AS <NUM>. The <NUM> NAS <NUM> may include functional entities associated with both access stratums. Thus, the <NUM> NAS <NUM> may include multiple <NUM> MM entities <NUM> and <NUM> and <NUM> session management (SM) entities <NUM> and <NUM>. The legacy NAS <NUM> may include functional entities such as short message service (SMS) entity <NUM>, evolved packet system (EPS) session management (ESM) entity <NUM>, session management (SM) entity <NUM>, EPS mobility management (EMM) entity <NUM>, and mobility management (MM)/ GPRS mobility management (GMM) entity <NUM>. In addition, the legacy AS <NUM> may include functional entities such as LTE AS <NUM>, UMTS AS <NUM>, and/or GSM/GPRS AS <NUM>.

Thus, the baseband processor architecture <NUM> allows for a common <NUM>-NAS for both <NUM> cellular and non-cellular (e.g., non-3GPP access). Note that as shown, the <NUM> MM may maintain individual connection management and registration management state machines for each connection. Additionally, a device (e.g., UE <NUM>) may register to a single PLMN (e.g., <NUM> CN) using <NUM> cellular access as well as non-cellular access. Further, it may be possible for the device to be in a connected state in one access and an idle state in another access and vice versa. Finally, there may be common <NUM>-MM procedures (e.g., registration, de-registration, identification, authentication, as so forth) for both accesses.

Note that in various embodiments, one or more of the above-described functional entities of the <NUM> NAS and/or <NUM> AS may be configured to perform methods for revocation and/or modification of user consent in MEC, e.g., in <NUM> NR systems and beyond, e.g., as further described herein.

In current implementations, e.g., as defined by TR <NUM> V4. <NUM>, a <NUM> system (5GS) is required to specify mechanisms to allow a user to change and/or add consent for a service. User consent may be collected at the beginning of a service, for example, in Edge Computing (MEC), an Edge Application Server (EAS) may require user consent when the UE registers the service. Thus, the user may confirm the consent in the beginning, however, at some point during the service, the user may change their consent from agreeing to share user sensitive information (e.g., such as UE location) to not agreeing to not share user sensitive information. Hence, it may be necessary to provide a procedure for a UE to modify and/or revoke user consent.

Embodiments described herein provide systems, methods, and mechanisms to support revocation and/or modification of user consent in MEC, including systems, methods, and mechanisms for modification/revocation of user consent through a Network Exposure Function (NEF), periodic updates of user consent, and UE initiated modification of user consent. In some embodiments, user consent may be collected in an application layer and/or 3GPP layer of a UE, such as UE <NUM>. For example, when user consent is collected in the application layer of the UE, modification/revocation may also be sent through the application layer. Thus, to update a state of the user consent in the Mobile Network Operator (MNO) network, the application server may send a notification to the MNO domain (e.g., such a unified data management (UDM) server and/or other network entities) through interfaces with the NEF. Note that how the application server gets the new state of user consent may be left to specific UE implementation. As another example, when user consent is collected in the 3GPP layer of a UE, modification/revocation may also be sent through the 3GPP layer.

As an example, a UE, such as UE <NUM>, sends a user consent modification/revocation request to an application server through an application layer of the UE. Then, the application server may send an update to the user consent to an MNO network through interfaces with a NEF. For example, as illustrated by <FIG>, an edge enabler server (EES) <NUM> of an edge data network <NUM> caters to edge applications running at the edge data network, e.g., running on edge application server(s) <NUM> via an EDGE-<NUM> interface. The EES <NUM> may be configured to expose application program interfaces (APIs) (e.g., such as a location service and/or a UE identifier (e.g., Generic Public Subscription Identifier (GPSI)), among other APIs) to the EAS <NUM>. In addition, public land mobile network (PLMN) network functions (NFs) may also be configured to expose the APIs to the EES <NUM>. Thus, if the EAS <NUM> requests user consent for use of sensitive information from the PLMN (e.g., such as 3GPP CN <NUM>, for a service, e.g., such as location, GPSI, and so forth, and the service is provided to the UE <NUM>, user consent may be collected from the user. Then, when the UE <NUM> (e.g., user) needs to modify and/or revoke user consent, the UE <NUM> may send a user consent modification request through the application data traffic <NUM> to the EAS <NUM>, e.g., an application client <NUM> executing on UE <NUM> may send the user consent modification request through the application data traffic <NUM> to the EAS <NUM>. The EAS <NUM> may then deliver the user consent modification request (which may, e.g., modify and/or revoke a previously provided user consent) to the EES <NUM>, e.g., via the EDGE-<NUM> interface. Further, the EES <NUM> may deliver the user consent modification request to an Evolved Charging Suite (ECS) executing on an edge configuration server, such as edge configuration server <NUM>, via an EDGE-<NUM> interface and to a home PLMN (HPLMN) (e.g., 3GPP CN <NUM>) of the UE <NUM> via an EDGE-<NUM> interface. In addition, EES <NUM> may interface with the edge enabler client <NUM> via an EDGE-<NUM> interface. Additionally, edge configuration server <NUM> may interface with the home PLMN via an EDGE-<NUM> interface and with the edge enabler client <NUM> via an EDGE-<NUM> interface. Note that the EES <NUM> may also maintain interfaces with the HPLMN, e.g., via an EDGE-<NUM> interface and an EDGE enabler client <NUM> executing on the UE <NUM> via an EDGE-<NUM> interface. Note further that the edge enabler client <NUM> may interface with the application client <NUM> via an EDGE-<NUM> interface. Additionally, the UE <NUM> may be considered a data subject <NUM> wherein as the HPLMN (e.g., 3GPP CN <NUM>) may be considered part of a data controller <NUM>. Further, EDGE network <NUM> and EES <NUM> may be considered part of a data controller <NUM> that may include data processor <NUM>, as shown.

Note that the above mechanism may be applied to MEC as well as other use cases. Note that EDGE-<NUM> and EDGE-<NUM> are in the EDGE network <NUM> whereas EDGE-<NUM> is outside of the EDGE network <NUM>. Thus, for EDGE-<NUM>, an Nnef_ParameterProvision Update service operation (e.g., per 3GPP TS <NUM> section <NUM>. <NUM>) may be used for user consent modification request transmission. For example, in some embodiments, the Nnef_ParameterProvision_Update may be modified to include a user consent update, e.g., in addition to including other UE related information such as expected UE behavior, network configuration parameters, location privacy indication parameters, and so forth.

In some embodiments, a network (e.g., a network entity) may trigger a user consent update procedure. For example, a policy control function (PCF) may initiate a UE configuration update to trigger the user consent update procedure. The UE configuration update procedure may be used to provision UE route selection policy (URSP) rules, which may be used for the UE to establish an appropriate protocol data unit (PDU) session prior to edge access stratum (AS) discovery. Thus, the UE configuration update procedure may be (re)used to deliver the user consent update request from the core network (e.g., from the PCF).

For example, <FIG> illustrates an example of signaling for a PCF to initiate a UE configuration update to trigger a user consent update procedure, according to some embodiments. The signaling shown in <FIG> may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired. As shown, this signaling may flow as follows.

At <NUM>, a PCF, such as PCF <NUM> may determine to update UE policies and/or update a user consent status based on triggering conditions, e.g., UE policies and/or user consent status of a UE, such as UE <NUM>. The triggering conditions may include an initial registration, registration with a <NUM> system (5GS) when the UE <NUM> moves from an evolved packet system (EPS) to 5GS, and/or a need for updating UE policy.

In response to the triggering condition, the PCF may send a user consent update request message <NUM> to an AMF, such as AM <NUM>. In some instances, the user consent update request message <NUM> may invoke a Namf_Communication_N1N2MessageTransfer service operation provided by the AMF. The user consent update request message <NUM> message may include a Subscription Permanent Identifier (SUPI), a UE Policy Container and/or a user consent update request. Note that whether the user consent update request is for one specific service (e.g., such as MEC) or for all the sensitive information collection, may be indicated in the user consent update request message <NUM>.

At <NUM>, the AMF may transfer (transparently) the UE Policy container and/or user consent update request received in the user consent update request message <NUM> to the UE via a network triggered service request.

Additionally and/or alternatively, if and/or when the UE is in a CM-CONNECTED over 3GPP access and/or non-3GPP access, the AMF may transfer transparently 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 form the PCF to the UE via UE policy delivery message <NUM>.

Then, the UE may update the UE policy provided by the PCF and may send the user consent update to the AMF via UE policy delivery response message <NUM>.

The AMF may then forward the response of the UE (including the user consent update) to the PCF via user consent update request response message <NUM>. In some embodiments, the AMF may forward the response of the UE (including the user consent update) to the PCF via a using Namf_Communication_N1MessageNotify service.

As another example an SMF of the network may initiate a PDU session modification to trigger the user consent update procedure. The PDU session modification procedure (e.g., as defined in section <NUM>. <NUM> of 3GPP TS <NUM>) is used for the SMF to indicate the EAS rediscovery to the UE based on information provided by AF or based on SMF's local configuration. However, since the UE will initiate a new PDU session establishment procedure after this PDU session modification procedure, this procedure may be leveraged to allow for a user consent update. In some embodiments, the user consent request may be included in (e.g., carried in) an Nsmf_PDUSession_UpdateSMContext Response in the PDU session modification procedure. In some embodiments, the user consent update procedure may be initiated by the core network or the application server periodically. The period may be configurable. Alternatively, and/or in addition, the user consent update procedure may be initiated by the network on demand, e.g., event and/or trigger based.

For example, <FIG> illustrates an example of signaling for an SMF to initiate a UE configuration update to trigger a user consent update procedure, according to some embodiments. The signaling shown in <FIG> may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired. As shown, this signaling may flow as follows.

At <NUM>, due to UE mobility (e.g., mobility of UE <NUM>), an SMF, such as SMF <NUM>, may trigger an L-PSA insertion, change and/or removal for a PDU Session.

At <NUM>, a user plane management event notifying an AF, such as AF <NUM>, may trigger EAS relocation. Note that if and/or when the AF triggers the EAS. Additionally, relocation and/or UE related update, e.g., due to EAS load balance or maintenance, the UE may trigger user consent modification/revocation through an application layer. Additionally, the UE may inform the SMF of related information. Then, the SMF may execute a network requested PDU Session Modification procedure as defined in clause <NUM>. <NUM> of 3GPP TS <NUM> and further described below in reference to signaling <NUM>-<NUM>. Note that the signaling described below may include modifications to the PDU Session Modification procedure as defined in clause <NUM>. <NUM> of 3GPP TS <NUM>. In some instances, the SMF may make the decision to indicate the EAS rediscovery to the UE based on information provided by the AF and/or based on SMF's local configuration. Thus, the SMF may send a PDU Session Modification Command (EAS rediscovery indication, [impact field], user consent update request) to UE. In some embodiments, the impact field may be used to identify which EAS(s) needs to be rediscovered. Thus, if and/or when the impact field is not included may indicate that all EAS(s) associated with this PDU Session need to be rediscovered. Note that if and/or when the EAS rediscovery is only for user consent update, then the "EAS rediscovery indication" and "impact field" may be the same and/or set as a fixed value (e.g., <NUM>. Additionally, if and/or when the EAS rediscovery is only for regular discovery, the "user consent update request" field may be set as null. In addition, note that the user consent update request may be carried together with the EAS relocation, e.g., whenever the EAS relocation takes place, the user consent update request may be sent. The user consent update request may also be sent according to the mobile network operator (MNO) policy, at least in some embodiments.

Continuing with the signaling of <FIG>, at <NUM>, the SMF may perform PDU update messaging with an AMF, such as AMF <NUM>. For example, for an SMF requested modification, the SMF may invoke a Namf_Communication_N1N2MessageTransfer service. The SMF may send various information to the AMF as part of the service, e.g., as currently defined by clause <NUM>. <NUM> of 3GPP TS <NUM>. In addition, as part of the service, the SMF may send a user consent update request to the AMF.

The AMF may then send an N2 message <NUM> to a radio access network (RAN), such as (R)AN <NUM>, which may include sending the N2 message to a base station, such as base station <NUM>. The message may include the user consent update request as well as information as defined by clause <NUM>. <NUM> of 3GPP TS <NUM>.

At <NUM>, the RAN may issue an access network (AN) specific signaling exchange with the UE that is related with the information received from SMF. For example, RRC Connection Reconfiguration may take place. Additionally, the UE may update user consent.

Additionally, the RAN may send an N2 reply message <NUM> to the AMF, which may include various information as defined by clause <NUM>. <NUM> of 3GPP TS <NUM>. The N2 reply message may include the user consent update, at least in some embodiments.

At <NUM>, the AMF may perform PDU update messaging with an SMF. The AMF may send various information to the SMF, including various information as defined by clause <NUM>. <NUM> of 3GPP TS <NUM>. In addition, the PDU update message may include the user consent update, at least in some embodiments.

At <NUM>, the SMF may perform an N4 modification procedure with a UPF, such as UPF <NUM>.

Further, the UE may acknowledge the PDU Session Modification Command by sending a PDU modification acknowledgement message <NUM> to the RAN. The PDU modification acknowledgement message <NUM> may be a NAS message that may include the user consent update, among other information.

The RAN may forward the PDU modification acknowledgement message to the AMF via an N2 NAS update message <NUM>. The N2 NAS update message <NUM> may include the user consent update, among other information.

At <NUM>, the AMF may forward the user consent update to the SMF. The user consent update may be included in an N1 SM container which may also include User Location Information received from the RAN.

At <NUM>, the AMF may perform an N4 modification procedure with a UPF, such as UPF <NUM>, e.g., to update user consent with the UPF.

For example, <FIG> illustrates an example of signaling for a UE to initiate a UE configuration update to trigger a user consent update procedure, according to some embodiments. The signaling shown in <FIG> may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired. As shown, this signaling may flow as follows.

At <NUM>, a UE, such as UE <NUM>, may initiate a PDU Session Modification procedure by transmitting a NAS message to an access network (AN), such as radio AN ((R)AN) <NUM>, which may include sending the NAS message to a base station, such as base station <NUM>. The NAS message may include various information as defined by clause <NUM>. <NUM> of 3GPP TS <NUM>. In addition, the NAS message may include a user consent update request.

At <NUM>, the AN may forward the NAS message to an AMF, such as AMF <NUM>. The NAS message may include various information as defined by clause <NUM>. <NUM> of 3GPP TS <NUM>. In addition, the NAS message may include a user consent update request. In some embodiments, the NAS message may be forwarded to the AMF with an indication of user location information.

At <NUM>, the SMF may perform PDU update messaging with an AMF, such as AMF <NUM>. For example, the SMF may receive various information from the AMF, e.g., as currently defined by clause <NUM>. <NUM> of 3GPP TS <NUM>. In addition, as part of the service, the SMF may receive a user consent update request from the AMF.

At <NUM>, the SMF may report some subscribed event to a PCF, such as PCF <NUM> by performing an SMF initiated SM Policy Association Modification procedure.

At <NUM>, for the UE (and/or) AN initiated modification, the SMF may respond to the AMF through a PDU response, e.g., such as Nsmf_PDUSession_UpdateSMContext Response. The response may include a user consent update acknowledge.

<FIG>, <FIG>, <FIG>, and <FIG> illustrate examples of various methods for user consent modification, according to some embodiments. The method shown in these Figures may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.

Turning to <FIG> illustrates an example of a method for user consent modification initiated by a UE, according to some embodiments. The method shown in <FIG> may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At <NUM>, a user equipment device (UE), such as UE <NUM>, may determine that user consent needs to be updated. The determination may be based on various factors, such as an indicated change in user preference, a periodic update of user preference, and/or various other factors. The user consent may be associated with Edge Computing (MEC).

At <NUM>, the UE may transmit, via an application layer of the UE, a user consent modification request to an edge application server, such as EAS <NUM> of a network, e.g., of an edge data network such as EDGE network <NUM>. The user consent modification request may be carried in application data traffic. In some embodiments, the user consent modification request may be indicated via an Nnef_ParameterProvision Update service operation. In some embodiments, the user consent modification request is indicated via an Nnef_ParameterProvision Update service operation. In some embodiments, the user consent modification is a revocation of user consent. In some embodiments, the edge application server may deliver the request to an edge enabler server.

In some embodiments, the UE may receive from the edge enabler server, an acknowledgment of user consent update. The acknowledgement may be received via an EDGE-<NUM> interface with the edge enabler server.

Turning to <FIG> illustrates an example of another method for user consent modification initiated by a UE, according to some embodiments. The method shown in <FIG> may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At <NUM>, an edge application server (EAS), such as EAS <NUM>, may receive, from a UE, such as UE <NUM>, a user consent modification request. 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 embodiments, the user consent modification may be a revocation of user consent.

At <NUM>, the EAS may deliver (e.g., send and/or transmit), to an edge enabler server (EES), such as EES <NUM>, the user consent modification request. The user consent modification request may be indicated via an Nnef_ParameterProvision Update service operation. In addition, the request may be delivered via an EDGE-<NUM> interface with the edge enabler server.

Turning to <FIG> illustrates an example of yet another method for user consent modification initiated by a UE, according to some embodiments. The method shown in <FIG> may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At <NUM>, an edge enabler server (EES), such as EES <NUM>, may receive, from an edge application server, such as EAS <NUM>, a user consent modification request for a UE, such as UE <NUM>. The user consent may be associated with Edge Computing (MEC). In addition, the user consent modification request may be received by the EAS in application data traffic. The user consent modification may be a revocation of user consent.

At <NUM>, the EES may notify a home public land mobile network (HPLMN) associated with the UE of a user consent modification. In some embodiments, the HPLMN associated with the UE may be notified via an EDGE-<NUM> interface.

In some embodiments, the EES may deliver (e.g., send and/or transmit) the request to an edge configuration server (ECS), such as ECS <NUM>. The request may be delivered via an EDGE-<NUM> interface with the edge configuration server.

Turning to <FIG> illustrates an example of a method for user consent modification initiated by an AMF, according to some embodiments. The method shown in <FIG> may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At <NUM>, an AMF, such as AMF <NUM>, of a network may receive, from a PCF, such as PCF <NUM>, of the network, a request to update a user consent status. In some embodiments, the request to update the user consent status may be based, at least in part, on any, any combination of, and/or all of (e.g., one or more of and/or at least one of) an initial registration, a registration with a Fifth Generation System (5GS) when the UE moves from an evolved packet core system (EPS) to the 5GS, and/or a requirement to update UE policy. In some embodiments, the user consent status may be associated with Edge Computing (MEC).

At <NUM>, the AMF may transfer, to a UE, such as UE <NUM>, the request to update the user consent status. In some embodiments, the UE may be in a CM-CONNECTED state over one of 3GPP access (e.g., cellular access) or non-3GPP access (e.g., non-cellular access).

At <NUM>, the AMF may receive, from the UE, an updated user consent status. In some embodiments, the updated user consent status may be indicated by Namf_Communication_N1MessageNotify. In some embodiments, the updated user consent status may indication revocation of user consent.

At <NUM>, the AMF may forward, to the PCF, the updated user consent status.

Turning to <FIG> illustrates an example of a method for user consent modification initiated by an SMF, according to some embodiments. The method shown in <FIG> may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At <NUM>, an SMF, such as SMF <NUM>, of a network may trigger (e.g., initiate) an EAS relocation.

At <NUM>, the SMF may receive, from an AF, such as AF <NUM>, of the network, a user consent modification request. In some embodiments, the user consent modification request may be a request to revoke user consent.

At <NUM>, the SMF may execute (e.g., perform) a PDU session modification procedure to update user consent. In some embodiments, a PDU session modification command sent by the SMF as part of the PDU session modification procedure may include a user consent update request field. In some embodiments, a PDU session modification command sent by the SMF as part of the PDU session modification procedure may include an impact field. The impact field may identify one or more EASs to be rediscovered. In some embodiments, a PDU session modification command sent by the SMF as part of the PDU session modification procedure may indicate all EASs are to be rediscovered. In some embodiments, a PDU session modification command sent by the SMF as part of the PDU session modification procedure may include an EAS rediscovery indication field and impact field and, if and/or when the EAS rediscovery indication field and impact field are set to same value, EAS rediscovery may be a user consent update only. In some embodiments, a PDU session modification command sent by the SMF as part of the PDU session modification procedure may include an EAS rediscovery indication field and impact field and, if and/or when the EAS rediscovery indication field and impact field are set to a fixed value, EAS rediscovery may be a user consent update only. In some embodiments, the fixed value may be <NUM>.

Turning to <FIG> illustrates an example of another method for user consent modification initiated by an SMF, according to some embodiments. The method shown in <FIG> may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At <NUM>, an SMF, such as SMF <NUM>, of a network may receive, from an AMF, such as AMF <NUM>, of the network, a user consent update request via a PDU update message. In some embodiments, the user consent update request may be triggered by a UE, such as UE <NUM>, associated with the user consent.

At <NUM>, the SMF may send, to the AMF, a PDU response that may include a user consent update acknowledge. The PDU response may be a Nsmf_PDUSession_UpdateSMContext response.

At <NUM>, the SMF may receive, from the AMF, a user consent update. In some embodiments, the user consent update may be a revocation of user consent. The user consent update may be received via an N1 SM container. In some embodiments, user location information may be received with the user consent update.

In some embodiments, a device (e.g., a UE <NUM>) may be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets). The device may be realized in any of various forms.

Claim 1:
A method for user consent modification initiated by a user equipment device, UE, (<NUM>), comprising:
the UE (<NUM>),
determining (<NUM>) that user consent needs to be updated; and
transmitting (<NUM>) via an application client (<NUM>) executing on the UE (<NUM>), a user consent modification request through application data traffic (<NUM>) to an edge application server (<NUM>), wherein the edge application server (<NUM>) delivers the request to an edge enabler server (<NUM>) via an EDGE-<NUM> interface; and
receiving, from the edge enabler server (<NUM>) via an edge enabler client (<NUM>) executing on the UE (<NUM>), an acknowledgement of user consent updated via an EDGE-<NUM> interface.