Seamless onboarding of AF deployed on UE enabling NEF API calls from UE application clients
The seamless onboarding of AF on UE for NEF API calls through UE operating system gatekeeping and NAS Security context-derived tokens addresses scalability and registration inefficiencies, enabling secure and efficient NEF API access.
Patent Information
- Application Number
- PCT/CN2025/094073
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing methods for invoking Network Exposure Function (NEF) API calls from UE application clients are not scalable, require offline agreements, and involve frictional AF registration processes, leading to inefficiencies and increased overhead for users.
A seamless onboarding mechanism for AF deployed on UE enables NEF API calls by utilizing the UE's operating system as a gatekeeper, deriving access tokens from the Non-Access Stratum (NAS) Security context, and employing OAuth-based authorization to ensure secure and frictionless API invocations.
This approach enhances scalability and reduces the demand on application servers while ensuring secure and efficient NEF API access, minimizing user intervention and operational overhead.
Smart Images

Figure CN2025094073_12112026_PF_FP_ABST
Abstract
Description
SEAMLESS ONBOARDING OF AF DEPLOYED ON UE ENABLING NEF API CALLS FROM UE APPLICATION CLIENTSTECHNICAL FIELD
[0001] This application relates generally to wireless communication systems, including application functions on a UE for invoking NEF API calls.BACKGROUND
[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) , 3GPP New Radio (NR) (e.g., 5G) , and Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLAN) (commonly known to industry groups as ) .
[0003] As contemplated by the 3GPP, different wireless communication systems'standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE) . 3GPP RANs can include, for example, Global System for Mobile communications (GSM) , Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN) , Universal Terrestrial Radio Access Network (UTRAN) , Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , and / or Next-Generation Radio Access Network (NG-RAN) .
[0004] Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE) , and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR) . In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.
[0005] A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) . One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB) .
[0006] A RAN provides its communication services with external entities through its connection to a core network (CN) . For example, E-UTRAN may utilize an Evolved Packet Core (EPC) while NG-RAN may utilize a 5G Core Network (5GC) .BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
[0007] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.
[0008] FIG. 1 illustrates an example protocol flow for accessing a resource according to some embodiments.
[0009] FIG. 2 illustrates an example block diagram for improving UE resident AF and NEF API calls from UE application clients in accordance with some embodiments.
[0010] FIG. 3 illustrates an example protocol flow for accessing a resource with different actors shown in FIG. 2 mapped to the OAuth steps according to some embodiments.
[0011] FIG. 4 illustrates an example call flow for token generation with input from AMF in accordance with some embodiments.
[0012] FIG. 5 illustrates an example call flow for token generation in the UE in accordance with some embodiments.
[0013] FIG. 6 illustrates a call flow for validation of a token by the NEF in accordance with some embodiments.
[0014] FIG. 7 illustrates a method for a UE in accordance with some embodiments.
[0015] FIG. 8 illustrates a method for a network node in accordance with some embodiments.
[0016] FIG. 9 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.
[0017] FIG. 10 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.DETAILED DESCRIPTION
[0018] Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.
[0019] Some embodiments herein enable Network Exposure Function (NEF) Application Programming Interface (API) calls from the UE application clients. This may allow for greater scalability of the use of the NEF API, and reduce demands on application servers.
[0020] Consider a use case of a gaming application requesting special Quality of Service (QoS) for the application traffic. One way to handle this request is for the procedure to happen in the back end (e.g., Application server acting as Application Function (AF) invokes NEF APIs) . However, this is not always practical (e.g., AFs need to know whether the UE is connecting over cellular or not and then contact the NEF) and scalable. This method may also raise charging issues (e.g., who would pay for the service, say QoS that an AF has requested) . This may require offline agreements with Application Service Providers (ASPs) and Mobile Network Operators (MNOs) .
[0021] There are scenarios where application clients in the UE may want to invoke Core network services (e.g. 5GC services) offered through NEF APIs. The app clients may know whether traffic is over a cellular network and when it is appropriate to invoke a 5GS service. The MNO can inform the UE about NEF services are available.
[0022] Edge Application (EDGEAPP) is one example, where Edge Enabler Client (EEC) (UE hosted) (acting in support of an application client) can make use of NEF APIs. However, in this case, Edge Enabler Server (EES) (network-side hosted) acts as a proxy for EECs since it is the EES, acting as an AF, that invokes NEF APIs. This approach is easier for MNOs to manage the AF on-boarding, but this requires an application layer interaction between UEs and an AF that can invoke NEF APIs. This may not be an easy process for users to make use of NEF APIs.
[0023] The Rel-18 Feature Resource owner-aware Northbound API Access (RNAA) has enabled an application client in the UE (the API invoker in this context) to invoke NEF APIs. In some embodiments, an API invoker can be an AF deployed on the UE. The UE resident AF can invoke NEF APIs, making use of Common API Framework (CAPIF) (for 3GPP northbound APIs) for onboarding. However, this is not a friction-less process. AF registration by MNOs is an offline task prior to onboarding. It will be an overhead for a subscriber to enter into agreement with MNOs for enabling UE resident application clients to invoke NEF services
[0024] Described herein are embodiments for a more seamless onboarding of AF deployed on a UE. This may enable NEF API calls from UE application clients.
[0025] The following definitions are intended to clarify the terminology used in the present disclosure and are not intended to be limiting.
[0026] "CAPIF" refers to Common API Framework (for 3GPP northbound APIs) .
[0027] "EAS" refers to Edge Application Server (UE hosted) .
[0028] "EEC" refers to Edge Enabler Client (UE hosted) .
[0029] "EES" refers to Edge Enabler Server (network-side hosted) .
[0030] "NEF" refers to Network Exposure Function (exposing 5G core network capabilities) .
[0031] "RNAA" refers to Resource owner-aware Northbound API Access.
[0032] FIG. 1 illustrates an example protocol flow 102 for accessing a resource according to some embodiments. For RNAA, CAPIF supports OAuth based approach to authorize an API invocation. CAPIF Core Function offers the authorization server functionality in this case.
[0033] As shown in the protocol flow 102, in a first step (e.g., message A (authorization request 108) and message B (authorization grant 110) ) the client 104 authorizes itself with the Resource owner 106 (either directly, or via the Authorization Server as an intermediary) . As shown, the client 104 may send an authorization request 108 to the resource owner 106 and the resource owner 106 may send the authorization grant 110. For example, the client 104 may present an appropriate username / password, and obtain authorization grant 110. The authorization grant 110 is a credential representing authorization from the resource owner 106 to access its resources hosted by the resource server 118.
[0034] In a second step (e.g., message C and message D) , the authorization grant 110 is presented to the authorization server 116 to obtain an access token 112. As shown, the client 104 may send the authorization grant 110 to the authorization server 116. In response to receiving the authorization grant 110 from the client 104, the authorization server 116 may send the access token 112 to the client 104.
[0035] In a third step (e.g., message E and message F) , the access token 112 is presented to the resource server 118 to access the protected resource 114. As shown, the client 104 may send the access token 112 to the resource server 118. In response to receiving the access token 112 from the client 104, the resource server 118 may send the protected resource 114 to the client 104.
[0036] In the illustrated protocol flow 102, the application client 104 (acting as an AF) in the UE can be registered and onboarded in a similar manner to an AF deployed on the network. MNOs and subscribers can enter into offline agreements to allow access for specific applications for specific resources. However, such, registration, onboarding, and offline agreements may present a scalability issue.
[0037] FIG. 2 illustrates an example block diagram 202 for improving UE resident AF and NEF API calls from UE application clients in accordance with some embodiments. The illustrated signaling reduces the scalability issues of the OAuth based approach illustrated in FIG. 1, and make onboarding AF deployed on the UE more seamless.
[0038] The application client may know when it has to invoke a NEF API for QoS. The operating system 204 of the UE 212 acts as the gate keeper (on behalf of the user 214) to ensure applications (e.g., gaming application 210 in the illustrated use case) have the right privilege to access UE related services in the cellular network 216. The operating system 204 settings may allow the capture of user preferences and intentions. The operating system 204 may decide whether applications get access to the Token (e.g., access token 218) generated / derived from the Non-Access Stratum (NAS) Security context 220.
[0039] The User 214 may have a trusted relationship with the MNO 208 (e.g., due to the fact that user has a subscription with the MNO 208) . By using the Access token 112 derived from the 5G AKA to invoke a NEF API, user 214 authorizes MNO 208 to charge the subscriber for API invocation. The operating system 204 and the application 210 may ensure that the Access token 218 is not compromised (e.g., through hacking or a malicious App client) .
[0040] For example, in the illustrated embodiment, the mobility management 206 of the UE 212 may obtain NAS Security context 220 for the cellular network 216 at the time of registration. The NAS Security context 220 may allow the UE 212 to generate access tokens for using the network's service APIs. As the NAS Security context 220 has been established, the UE 212 is trusted by the network. Further, the operating system 204 and the application 210 may share a trust 222 relation because the operating system has allowed the application 210 to be executed or installed. Further, the user 214 has trust 226 toward the operating system and trust 222 toward the MNO 208.
[0041] The user 214 may tell the operating system 204 that the user 214 accepts certain application clients accessing some information from the cellular network 216 on their behalf. The operating system 204 may act as a gate keeper that authorizes 224 applications to receive an access token 218. The access token 218 may be derived based on the NAS Security context 220. When the access token 218 is generated, the application 210 can invoke the network API with that access token 218. The cellular network 216 can resolve this access token 112 corresponds to a particular subscriber because of the NAS Security context 220 and determine that the application 210 is allowed to invoke certain APIs and / or access certain resources for this user. Accordingly, the UE resident AF may use the NAS Security context 220 to get the access token 218, and present the access token 218 to the network to access the server.
[0042] FIG. 3 illustrates an example protocol flow 302 for accessing a resource with different actors shown in FIG. 2 mapped to the OAuth steps according to some embodiments. As shown in the protocol flow 302, in a first step (e.g., message A (authorization request 308) and message B (authorization grant 310) ) the client 304 authorizes itself with the resource owner 306 (either directly, or via the Authorization Server as an intermediary) . As shown, the client 104 may send an authorization request 308 to the resource owner 306 and the resource owner 306 may send the authorization grant 310. For example, the client 304 may present an appropriate username / password, and obtain authorization grant 310. The authorization grant 310 is a credential representing authorization from the resource owner 306 to access its resources hosted by the resource server 318. As shown, the resource owner 306 may comprise the high level operating system (HL OS 320) .
[0043] In a second step (e.g., message C and message D) , the authorization grant 310 is presented to the authorization server 316 to obtain an access token 312. As shown, the client 304 may send the authorization grant 310 to the authorization server 316. In response to receiving the authorization grant 310 from the client 304, the authorization server 316 may send the access token 312 to the client 304. As shown, the authorization server 316 may comprise the UE Mobility Management &Access and Mobility Management Function (UE MM / AMF 322) .
[0044] In a third step (e.g., message E and message F) , the access token 312 is presented to the resource server 318 to access the protected resource 314. As shown, the client 304 may send the access token 312 to the resource server 318. In response to receiving the access token 312 from the client 304, the resource server 318 may send the protected resource 314 to the client 304. As shown, the resource server 318 may comprise the Network Exposure Function / Core Network (NEF / CN 324) .
[0045] Some embodiments may attempt to make API invocation from an AF deployed on the UE as friction-less as possible. For example, a UE that has authenticated with the Core Network (e.g., 5GC or 6GC) will have a NAS security context that is specific to its credential in USIM. Establishing such context may ensure the integrity and confidentiality of NAS messages and protects sensitive user information during network interactions, specifically between the UE and AMF. A token generated from this NAS security context may help the operator to trust a UE hosted AF’s (i.e., API invoker) identity and authorization to obtain the requested service.
[0046] In some embodiments, a process similar to token generation and validation in OAuth may be used. For example, an Access Token may be generated from the UE NAS security context. The Access Token may be generated for authorized clients from the NAS security context. For instance, an Access Token may be derived from Key Access and Mobility Management Function (Kamf) or Key for Authentication Server Function (Kausf) (as discussed with more details herein) . An access token may identify that it has been generated by the Universal Subscriber Identity Module (USIM) based on the credential in USIM of the subscriber that is the subject of the API call. In some embodiments, the access token may also restrict the resource (e.g., the purpose of the API -parameter provisioning, influence traffic routing, provide session QoS requirements) the API invoker is entitled to. This may be possible as per OAuth RFC (e.g., data + signature approach for a token) .
[0047] In some embodiments, the access token may be derived from keys in the UE. For example, the access token may be derived from Kamf in the UE (decentralized Authorization Server approach) . As another option, the access token may be derived from Kausf. The access token may be generated by the UE at the time of API invocation. Tokens may be for one-time use only with a limited validity time. Network (AMF or AuSF or a new dedicated NF) may verify that token for identity and entitlement. This approach may lead to less UE-Network signaling.
[0048] In some embodiments, the access token may be derived from Kamf or Kausf with input parameter from the network. The input parameter may be passed to the UE through NAS signaling at the time of invocation. This may allow for network control of token generation.
[0049] Note the following regarding potential misuse of Access Token. An Access Token generated based on the UE NAS Security context, may resolve it back to the subscriber identifier (SUPI) . This may enable simpler friction-less API invocation by any application function that has the Access Token. But this may also present the security issue that if the Access Token is intercepted by another application than the one originally intended, the subscriber whose security context had generated the Access Token is still going to be responsible.
[0050] An alternative approach to add another layer of security is to use an identifier for the application function in the UE (AFue) to be included as part of Access Token. This may enable the NEF to verify that the AF that presents Access Token is the one that originally got it from the UE. Identifier for the AFue could be either HLOS Application Identifier or an MNO assigned AF specific UE Identifier. However, this approach may bring back some amount of AF onboarding overhead.
[0051] FIG. 4 illustrates an example call flow 402 for token generation with input from AMF 408 in accordance with some embodiments. The call flow 402 provides Authentication and Key Agreement (AKA) based token for NEF API invocation. In some embodiments token generation may be in the UE 406.
[0052] In the illustrated embodiment, the UE 406 is registered normally with the network and has a NAS security context established 412. For example, in the illustrated embodiment, the UE 406 corresponds with the AMF 408 to register and establish NAS security context.
[0053] An application in the UE AFUE 404 has a desire to invoke 414 NEF API for UE parameter provisioning. The AFUE 404 is authorized 416 by the UE 406 for getting an access token for this NEF API. AF authorization can be implicit or guaranteed by the OS.This authorization allows the application access to a token based on NAS security context. The authorization can be a guarantee by the HL OS.
[0054] The AFUE 404 can invoke a request 418 to get an access token. For example, as show, the AFUE 404 may invoke the UE 406 to send a request 418 to get an access token from the AMF 408. The UE 406 may send the request 418 to the AMF 408. The input parameters of the get access token request can include the NEF service that is requested. Further, the request may optionally include an Identifier for the AFUE 404 (e.g., AFue ID) . The identifier for the AFUE 404 may be an application ID provided by the HL OS, or it may be an identifier assigned by the MNO.
[0055] The UE 406 may send the request via NAS signaling 420 towards the AMF 408. The AMF 408 may generate 422 a parameter (e.g., input) for token derivation using Kamf and the provided input parameters (e.g., parameters in the request 418) . In some embodiments, the token may be self-encoded (e.g., similar to JSON Web Token) .
[0056] The generated parameter may be passed by the AMF 408 to the UE 406 in NAS signaling. For example, the AMF 408 may send the UE 406 an access token response 424 that includes a fresh parameter for token generation. The UE 406 may generate 426 an access token based on the parameter from the AMF 408. The UE 406 may provide the AFUE 404 with the access token 428.
[0057] The AFUE 404 may get the access token. The AFUE 404 can use this access token for invoking NEF API (e.g., Nnef_ParameterProvision 430) . The NEF 410 validates 432 the token with AMF 408. For example, the API could identify UE 406 using an IP address. In some cases NEF 410 may use BSF to map the UE 406 to a SUPI and contact that AMF 408 for validating the token. Validation of the token can involve validating the identity of the invoker (SUPI) (optionally, also the identity of the AFUE 404) and validating the access privilege for the requested service. In some embodiments, if the token is self-encoded, NEF 410 can validate the token based on the public key for the PLMN.
[0058] During the validation, the NEF 410 may resolve the requesting UE Identifier, and verify the service is allowed to be invoked by the requesting AFUE 404 for this subscriber. If validation is successful, NEF 410 proceeds with fulfilment of the requested service. If validation fails, API can be rejected with suitable cause.
[0059] FIG. 5 illustrates an example call flow 502 for token generation in the UE 506 in accordance with some embodiments. The call flow 502 provides AKA based token for NEF API invocation. In some embodiments token generation may be in the UE 506. This may avoid additional UE and AMF signaling shown in FIG. 4.
[0060] In the illustrated embodiment, the UE 506 is registered normally with the network and has a NAS security context established 512. For example, in the illustrated embodiment, the UE 506 corresponds with the AMF 508 to register and establish NAS security context.
[0061] An application in the UE AFUE 504 has a desire to invoke 514 NEF API for UE parameter provisioning. The AFUE 504 is authorized 516 by the UE 506 for getting an access token for this NEF API. AF authorization can be implicit or guaranteed by the OS.This authorization allows the application access to a token based on NAS security context. The authorization can be a guarantee by the HL OS.
[0062] The AFUE 504 can invoke a request 518 to get an access token. The input parameters of the get access token request can include the NEF service that is requested. Further, the request may optionally include an Identifier for the AFUE 504 (e.g., AFue ID) . The identifier for the AFUE 504 may be an application ID provided by the HL OS, or it may be an identifier assigned by the MNO.
[0063] The UE 506 may generate 520 the access token based on Kamf and the provided input parameters (e.g., parameters in the request 518) . In some embodiments, the token may be self-encoded (e.g., similar to JSON Web Token) . The UE 506 may provide the AFUE 504 with the access token 522.
[0064] The AFUE 504 may get the access token. The AFUE 504 can use this access token for invoking NEF API (e.g., Nnef_ParameterProvision 524) . The NEF 510 validates 526 the token with AMF 508. For example, the API could identify UE 506 using an IP address. In some cases NEF 510 may use BSF to map the UE 506 to a SUPI and contact that AMF 508 for validating the token. Validation of the token can involve validating the identity of the invoker (SUPI) (optionally, also the identity of the AFUE 504) and validating the access privilege for the requested service. In some embodiments, if the token is self-encoded, NEF 510 can validate the token based on the public key for the PLMN.
[0065] During the validation, the NEF 510 may resolve the requesting UE Identifier, and verify the service is allowed to be invoked by the requesting AFUE 504 for this subscriber. If validation is successful, NEF 510 proceeds with fulfilment of the requested service. If validation fails, API can be rejected with suitable cause.
[0066] FIG. 6 illustrates a call flow 602 for validation of a token by the NEF 612 in accordance with some embodiments. The call flow 602 may be for AKA based token for NEF API invocation. This call flow 602 may be used for the step of validating the token (e.g., validate 432 in FIG. 4 and validate 526 in FIG. 5) . This call flow 602 may be used if network address translation (NAT) -ing is used.
[0067] As shown, the AFUE 604 may use an access token for invoking NEF API (e.g., Nnef_ParameterProvision 614) . As shown, the AFUE 604 may send the NEF 612 a Nnef_ParameterProvision 614. The Nnef_ParameterProvision 614 may include the access token, API parameters, and UE IP address) .
[0068] If the UE is identified by its IP address in the API, and if the UE IP Address is NAT-ed by the network, the NEF 612 can use the user plane function (UPF) service to retrieve the private IP address of the UE. The NEF 612 can use Binding Support Function (BSF 610) to get the UE’s SUPI from its private IP address. For example, in the illustrated embodiment, the NEF 612, to the BSF 610) sends a Nbsf_Management_DiscoveryReq 616 comprising the UE IP address. The BSF 610 may MAP IP address to SUPI 618, and send a Nbsf_Management_DiscoveryRspq 620 comprising the UE SUPI to the NEF 612.
[0069] The NEF 612 can invoke Unified Data Management (UDM 608) UECM_Get service to obtain the AMF ID. For example, the NEF 612 may send a Nudm_UECM_Get Request 622 to the UDM 608. The Nudm_UECM_Get Request 622 may include a SUPI and Get AMF ID request. The UDM 608 may determine the AMF ID, and respond by sending the NEF 612 a Nudm_UECM_Get Response that includes the AMF ID. If the access token is derived from the Kausf, NEF 612 can obtain the AUSF to be contacted.
[0070] The NEF 612 can invoke a new service for token validation. The input parameters may include Token and the Requested service. As response, NEF 612 can get the result of token validation. For example, the NEF 612 may send a Namf_Validate Access Token to an AMF, AUSF, or a new network function 606 that includes the SUPI, the token, and the requested service. The AMF, AUSF, or a new network function 606 may validate 626 whether the token is generated by the UE of the identified SUPI, and send the result to the NEF 612. If the Token validation is successful, NEF 612 proceeds with the requested service.
[0071] In some embodiments, token generation may involve one or more of the following attributes and derivation methods. Attributes of the token may be as follows. The token may be generated from the root key of the NAS security context (e.g., Kamf) . The token can be validated to have been generated using the Kamf for the given subscriber, and grant privilege for requesting the service associated with the API.
[0072] Token derivation methods may include the following. Key Derivation Function (KDF) may be defined as in Annex B. 2.0 in 3GPP TS 33.220. In a first option, the key may be derived from Kamf in the UE (e.g., Token = KDF (kamf, app ID, random number) ) . In a second option the key may be derived from Kausf in the UE (e.g., Token = KDF (kausf, app ID, random number) ) . In the first option and the second option, the random number may be also passed along with the token for the NEF to validate the token. In a third option, the key may be derived from Kamf in the UE with input from AMF (e.g., Token = KDF (kamf, app ID, fresh parameter) ) . In a fourth option, the key may be derived from Kausf in the UE with input from AUSF (e.g., Token = KDF (kausf, app ID, fresh parameter) ) .
[0073] FIG. 7 illustrates a method 700 for a UE in accordance with some embodiments. The illustrated method 700 includes establishing 702 NAS security context with an AMF. The method 700 further includes deriving 704 an access token from the NAS security context. The method 700 further includes providing 706 the access token to an AFue. The method 700 further includes invoking 708, via the AFue, an NEF API using the access token.
[0074] In some embodiments of the method 700, deriving the access token from the NAS security context comprises: sending a request to the AMF indicating a requested NEF service, and receiving a response from the AMF comprising a parameter for the access token derivation, wherein the access token is derived based on both the NAS security context and the parameter from the AMF.
[0075] In some embodiments of the method 700, deriving the access token from the NAS security context comprises: receiving a request from the AFue indicating a requested NEF service, and generating the access token based on the NAS security context and the request.
[0076] In some embodiments of the method 700, the access token is generated by the UE when invoking the NEF API.
[0077] In some embodiments of the method 700, the access token is for one-time use with a limited validity time.
[0078] In some embodiments of the method 700, the token is self-encoded.
[0079] In some embodiments of the method 700, deriving the access token from the NAS security context comprises using a Key Derivation Function with inputs including a Kamf, an application ID, and a random number,
[0080] wherein the random number is passed along with the access token to a NEF to validate the access token.
[0081] In some embodiments of the method 700, deriving the access token from the NAS security context comprises using a Key Derivation Function with inputs including a Kausf, an application ID, and a random number, wherein the random number is passed along with the access token to a NEF to validate the access token.
[0082] In some embodiments of the method 700, deriving the access token from the NAS security context comprises using a Key Derivation Function with inputs including a Kamf, an application ID, and a parameter from an AMF.
[0083] In some embodiments of the method 700, deriving the access token from the NAS security context comprises using a Key Derivation Function with inputs including a Kausf, an application ID, and a parameter from an AUSF.
[0084] In some embodiments of the method 700, invoking the NEF API using the access token comprises sending a UE parameter provisioning message to the NEF that includes the access token and API parameters.
[0085] FIG. 8 illustrates a method 800 for a network node in accordance with some embodiments. The illustrated method 800 includes establishing 802 NAS security context between a UE and an AMF. The method 800 further includes receiving 804, from an AFue via an NEF, an NEF API invocation comprising an access token derived based on the NAS security context. The method 800 further includes validating 806 the access token. The method 800 further includes proceeding 808 with a service requested by the NEF API invocation in response to the access token being valid.
[0086] In some embodiments, the method 800 further comprises receiving a request, from the user equipment via the AMF, indicating a requested NEF service, and sending a response, via the AMF, comprising a parameter for the access token derivation, wherein the access token is derived based on both the NAS security context and the parameter.
[0087] In some embodiments of the method 800, the access token is for one-time use with a limited validity time.
[0088] In some embodiments of the method 800, the token is self-encoded.
[0089] In some embodiments of the method 800, the NEF API invocation further comprises API parameters.
[0090] In some embodiments of the method 800, validating the access token comprises mapping an IP address associated with the NEF API invocation to a SUPI. In some such embodiments, validating the access token comprises verifying, via the AMF, an AUSF, or a new network function, whether the access token was generated by the UE of the identified SUPI.
[0091] In some embodiments, the method 800 further comprises invoking a UDM UECM_Get service to obtain an AMF ID associated with the access token.
[0092] In some embodiments of the method 800, the NEF API invocation comprises the access token, API parameters, and a UE IP address.
[0093] FIG. 9 illustrates an example architecture of a wireless communication system 900, according to embodiments disclosed herein. The following description is provided for an example wireless communication system 900 that operates in conjunction with the LTE system standards and / or 5G or NR system standards as provided by 3GPP technical specifications.
[0094] As shown by FIG. 9, the wireless communication system 900 includes UE 902 and UE 904 (although any number of UEs may be used) . In this example, the UE 902 and the UE 904 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) , but may also comprise any mobile or non-mobile computing device configured for wireless communication.
[0095] The UE 902 and UE 904 may be configured to communicatively couple with a RAN 906. In embodiments, the RAN 906 may be NG-RAN, E-UTRAN, etc. The UE 902 and UE 904 utilize connections (or channels) (shown as connection 908 and connection 910, respectively) with the RAN 906, each of which comprises a physical communications interface. The RAN 906 can include one or more base stations (such as base station 912 and base station 914) that enable the connection 908 and connection 910.
[0096] In this example, the connection 908 and connection 910 are air interfaces to enable such communicative coupling, and may be consistent with RAT (s) used by the RAN 906, such as, for example, an LTE and / or NR.
[0097] In some embodiments, the UE 902 and UE 904 may also directly exchange communication data via a sidelink interface 916. The UE 904 is shown to be configured to access an access point (shown as AP 918) via connection 920. By way of example, the connection 920 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 918 may comprise a router. In this example, the AP 918 may be connected to another network (for example, the Internet) without going through a CN 924.
[0098] In embodiments, the UE 902 and UE 904 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 912 and / or the base station 914 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications) , although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.
[0099] In some embodiments, all or parts of the base station 912 or base station 914 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 912 or base station 914 may be configured to communicate with one another via interface 922. In embodiments where the wireless communication system 900 is an LTE system (e.g., when the CN 924 is an EPC) , the interface 922 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 900 is an NR system (e.g., when CN 924 is a 5GC) , the interface 922 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 912 (e.g., a gNB) connecting to 5GC and an eNB, and / or between two eNBs connecting to 5GC (e.g., CN 924) .
[0100] The RAN 906 is shown to be communicatively coupled to the CN 924. The CN 924 may comprise one or more network elements 926, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 902 and UE 904) who are connected to the CN 924 via the RAN 906. The components of the CN 924 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
[0101] In embodiments, the CN 924 may be an EPC, and the RAN 906 may be connected with the CN 924 via an S1 interface 928. In embodiments, the S1 interface 928 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 912 or base station 914 and a serving gateway (S-GW) , and the S1-MME interface, which is a signaling interface between the base station 912 or base station 914 and mobility management entities (MMEs) .
[0102] In embodiments, the CN 924 may be a 5GC, and the RAN 906 may be connected with the CN 924 via an NG interface 928. In embodiments, the NG interface 928 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 912 or base station 914 and a user plane function (UPF) , and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 912 or base station 914 and access and mobility management functions (AMFs) .
[0103] Generally, an application server 930 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 924 (e.g., packet switched data services) . The application server 930 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc. ) for the UE 902 and UE 904 via the CN 924. The application server 930 may communicate with the CN 924 through an IP communications interface 932.
[0104] FIG. 10 illustrates a system 1000 for performing signaling 1034 between a wireless device 1002 and a network device 1018, according to embodiments disclosed herein. The system 1000 may be a portion of a wireless communications system as herein described. The wireless device 1002 may be, for example, a UE of a wireless communication system. The network device 1018 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.
[0105] The wireless device 1002 may include one or more processor (s) 1004. The processor (s) 1004 may execute instructions such that various operations of the wireless device 1002 are performed, as described herein. The processor (s) 1004 may include one or more baseband processors implemented using, for example, a central processing unit (CPU) , a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0106] The wireless device 1002 may include a memory 1006. The memory 1006 may be a non-transitory computer-readable storage medium that stores instructions 1008 (which may include, for example, the instructions being executed by the processor (s) 1004) . The instructions 1008 may also be referred to as program code or a computer program. The memory 1006 may also store data used by, and results computed by, the processor (s) 1004.
[0107] The wireless device 1002 may include one or more transceiver (s) 1010 that may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that use the antenna (s) 1012 of the wireless device 1002 to facilitate signaling (e.g., the signaling 1034) to and / or from the wireless device 1002 with other devices (e.g., the network device 1018) according to corresponding RATs.
[0108] The wireless device 1002 may include one or more antenna (s) 1012 (e.g., one, two, four, or more) . For embodiments with multiple antenna (s) 1012, the wireless device 1002 may leverage the spatial diversity of such multiple antenna (s) 1012 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect) . MIMO transmissions by the wireless device 1002 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 1002 that multiplexes the data streams across the antenna (s) 1012 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream) . Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain) .
[0109] In certain embodiments having multiple antennas, the wireless device 1002 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna (s) 1012 are relatively adjusted such that the (joint) transmission of the antenna (s) 1012 can be directed (this is sometimes referred to as beam steering) .
[0110] The wireless device 1002 may include one or more interface (s) 1014. The interface (s) 1014 may be used to provide input to or output from the wireless device 1002. For example, a wireless device 1002 that is a UE may include interface (s) 1014 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 1010 / antenna (s) 1012 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., and the like) .
[0111] The wireless device 1002 may include an Access Token module 1016. The Access Token module 1016 may be implemented via hardware, software, or combinations thereof. For example, the Access Token module 1016 may be implemented as a processor, circuit, and / or instructions 1008 stored in the memory 1006 and executed by the processor (s) 1004. In some examples, the Access Token module 1016 may be integrated within the processor (s) 1004 and / or the transceiver (s) 1010. For example, the Access Token module 1016 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 1004 or the transceiver (s) 1010.
[0112] The Access Token module 1016 may be used for various aspects of the present disclosure, for example, aspects of FIG. 1, FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6, and FIG. 7. The Access Token module 1016 may be configured to cause the wireless device 1002 to establish NAS security context with an AMF. The Access Token module 1016 may be configured to further cause the wireless device 1002 to derive an access token from the NAS security context. The Access Token module 1016 may be configured to further cause the wireless device 1002 to provide the access token to an AFue. The Access Token module 1016 may be further configured to further cause the wireless device 1002 to invoke, via the AFue, an NEF API using the access token.
[0113] The network device 1018 may include one or more processor (s) 1020. The processor (s) 1020 may execute instructions such that various operations of the network device 1018 are performed, as described herein. The processor (s) 1020 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0114] The network device 1018 may include a memory 1022. The memory 1022 may be a non-transitory computer-readable storage medium that stores instructions 1024 (which may include, for example, the instructions being executed by the processor (s) 1020) . The instructions 1024 may also be referred to as program code or a computer program. The memory 1022 may also store data used by, and results computed by, the processor (s) 1020.
[0115] The network device 1018 may include one or more transceiver (s) 1026 that may include RF transmitter circuitry and / or receiver circuitry that use the antenna (s) 1028 of the network device 1018 to facilitate signaling (e.g., the signaling 1034) to and / or from the network device 1018 with other devices (e.g., the wireless device 1002) according to corresponding RATs.
[0116] The network device 1018 may include one or more antenna (s) 1028 (e.g., one, two, four, or more) . In embodiments having multiple antenna (s) 1028, the network device 1018 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.
[0117] The network device 1018 may include one or more interface (s) 1030. The interface (s) 1030 may be used to provide input to or output from the network device 1018. For example, a network device 1018 that is a base station may include interface (s) 1030 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 1026 / antenna (s) 1028 already described) that enables the base station to communicate with other equipment in a core network, and / or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.
[0118] The network device 1018 may include an Access Token module 1032. The Access Token module 1032 may be implemented via hardware, software, or combinations thereof. For example, the Access Token module 1032 may be implemented as a processor, circuit, and / or instructions 1024 stored in the memory 1022 and executed by the processor (s) 1020. In some examples, the Access Token module 1032 may be integrated within the processor (s) 1020 and / or the transceiver (s) 1026. For example, the Access Token module 1032 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 1020 or the transceiver (s) 1026.
[0119] The Access Token module 1032 may be used for various aspects of the present disclosure, for example, aspects of FIG. 1, FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6, and FIG. 8. The Access Token module 1032 may be configured to cause the network device 1018 to establish NAS security context between a UE and an AMF. The Access Token module 1032 may be configured to further cause the network device 1018 to receive, from an AFue via an NEF, an NEF API invocation comprising an access token derived based on the NAS security context. The Access Token module 1032 may be configured to further cause the network device 1018 to validate the access token. The Access Token module 1032 may be configured to further cause the network device 1018 to proceed with a service requested by the NEF API invocation in response to the access token being valid.
[0120] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 700. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1002 that is a UE, as described herein) .
[0121] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 700. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 1006 of a wireless device 1002 that is a UE, as described herein) .
[0122] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 700. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1002 that is a UE, as described herein) .
[0123] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 700. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1002 that is a UE, as described herein) .
[0124] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 700.
[0125] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method 700. The processor may be a processor of a UE (such as a processor (s) 1004 of a wireless device 1002 that is a UE, as described herein) . These instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 1006 of a wireless device 1002 that is a UE, as described herein) .
[0126] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 800. This apparatus may be, for example, an apparatus of a base station (such as a network device 1018 that is a base station, as described herein) .
[0127] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 800. This non-transitory computer-readable media may be, for example, a memory of a base station (such as a memory 1022 of a network device 1018 that is a base station, as described herein) .
[0128] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 800. This apparatus may be, for example, an apparatus of a base station (such as a network device 1018 that is a base station, as described herein) .
[0129] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 800. This apparatus may be, for example, an apparatus of a base station (such as a network device 1018 that is a base station, as described herein) .
[0130] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 800.
[0131] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of the method 800. The processor may be a processor of a base station (such as a processor (s) 1020 of a network device 1018 that is a base station, as described herein) . These instructions may be, for example, located in the processor and / or on a memory of the base station (such as a memory 1022 of a network device 1018 that is a base station, as described herein) .
[0132] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
[0133] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments) , unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
[0134] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices) . The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.
[0135] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.
[0136] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
[0137] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims
1.A method for a user equipment (UE) , the method comprising:establishing Non-Access Stratum (NAS) security context with an access and mobility management function (AMF) ;deriving an access token from the NAS security context;providing the access token to an application function in the UE (AFue) ; andinvoking, via the AFue, a Network Exposure Function (NEF) Application Programming Interface (API) using the access token.2.The method of claim 1, wherein deriving the access token from the NAS security context comprises:sending a request to the AMF indicating a requested NEF service; andreceiving a response from the AMF comprising a parameter for the access token derivation, wherein the access token is derived based on both the NAS security context and the parameter from the AMF.3.The method of claim 1, wherein deriving the access token from the NAS security context comprises:receiving a request from the AFue indicating a requested NEF service; andgenerating the access token based on the NAS security context and the request.4.The method of claim 1, wherein the access token is generated by the UE when invoking the NEF API.5.The method of claim 1, wherein the access token is for one-time use with a limited validity time.6.The method of claim 1, wherein the token is self-encoded.7.The method of claim 1, wherein deriving the access token from the NAS security context comprises using a Key Derivation Function with inputs including a Key for Access and Mobility Management Function (Kamf) , an application ID, and a random number,wherein the random number is passed along with the access token to the NEF to validate the access token.8.The method of claim 1, wherein deriving the access token from the NAS security context comprises using a Key Derivation Function with inputs including a Key for Authentication Server Function (Kausf) , an application ID, and a random number,wherein the random number is passed along with the access token to a NEF to validate the access token.9.The method of claim 1, wherein deriving the access token from the NAS security context comprises using a Key Derivation Function with inputs including a Key for Access and Mobility Management Function (Kamf) , an application ID, and a parameter from an access and mobility management function (AMF) .10.The method of claim 1, wherein deriving the access token from the NAS security context comprises using a Key Derivation Function with inputs including a Key for Authentication Server Function (Kausf) , an application ID, and a parameter from an AUSF.11.The method of claim 1, wherein invoking the NEF API using the access token comprises sending a UE parameter provisioning message to the NEF that includes the access token and API parameters.12.A method for a network node, the method comprising:establishing Non-Access Stratum (NAS) security context between a user equipment (UE) and an access and mobility management function (AMF) ;receiving, from an application function in the UE (AFue) via a Network Exposure Function (NEF) , a Network Exposure Function (NEF) Application Programming Interface (API) invocation comprising an access token derived based on the NAS security context;validating the access token; andproceeding with a service requested by the NEF API invocation in response to the access token being valid.13.The method of claim 12, further comprising receiving a request, from the user equipment via the AMF, indicating a requested NEF service; andsending a response, via the AMF, comprising a parameter for the access token derivation, wherein the access token is derived based on both the NAS security context and the parameter.14.The method of claim 12, wherein the access token is for one-time use with a limited validity time.15.The method of claim 12, wherein the token is self-encoded.16.The method of claim 12, wherein the NEF API invocation further comprises API parameters.17.The method of claim 12, wherein validating the access token comprises mapping an IP address associated with the NEF API invocation to a subscriber identifier (SUPI) .18.The method of claim 17, wherein validating the access token comprises verifying, via the AMF, an AUSF, or a new network function, whether the access token was generated by the UE of the identified SUPI.19.The method of claim 12, further comprising invoking a UDM UECM_Get service to obtain an AMF ID associated with the access token.20.The method of claim 12, wherein the NEF API invocation comprises the access token, API parameters, and a UE IP address.21.An apparatus comprising means to perform the method of any of claim 1 to claim 20.22.A computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform the method of any of claim 1 to claim 20.23.An apparatus comprising logic, modules, or circuitry to perform the method of any of claim 1 to claim 20.24.A baseband processor for a user equipment (UE) configured to perform the method of any of claim 1 to claim 11.
