Edge enabler client identification authentication procedures

US12323793B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12323793-B2
Application numberUS-202117759877-A
CountryUS
Kind codeB2
Filing dateAug 6, 2021
Priority dateAug 6, 2021
Publication dateJun 3, 2025
Grant dateJun 3, 2025

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

An edge enabler server of an edge data network is configured to receive a verification request comprising an edge enabler client identification (EEC ID), wherein the EEC ID uniquely identifies an edge enabler client (EEC), determine whether the EEC ID is an authorized EEC ID and provide a verification response based on whether the EEC ID is authorized.

First claim

Opening claim text (preview).

What is claimed is: 1. An edge enabler server of an edge data network configured to perform operations comprising: receiving, from an edge configuration server (ECS) of the edge data network, a verification request comprising an edge enabler client identification (EEC ID), wherein the EEC ID uniquely identifies an edge enabler client (EEC); determining whether the EEC ID is an authorized EEC ID based on an authorized list of EEC IDs stored remotely from the edge enabler server; and providing a verification response to the ECS based on whether the EEC ID is authorized. 2. The edge enabler server of claim 1 , wherein the verification request is received from an Authentication and Key Management for Applications (AKMA) anchor function (AAnF) of a core network to which the edge data network is communicatively coupled. 3. The edge enabler server of claim 1 , wherein the verification response indicates a success when the EEC ID is authorized. 4. The edge enabler server of claim 1 , wherein the verification response indicates a failure when the EEC ID is not authorized. 5. An edge configuration server of an edge data network configured to perform operations comprising: receiving an application registration request from an edge enabler client (EEC) instantiated on a user equipment (UE), the application registration request comprising an EEC identification (EEC ID), wherein the EEC ID uniquely identifies the EEC; sending a verification request to an edge enabler server (EES) of the edge data network to request authentication of the EEC ID; and receiving a verification response from the EES based on whether the EEC ID is authorized. 6. The edge configuration server of claim 5 , wherein the edge configuration server locally stores an authorized list of EEC IDs and wherein the verifying the EEC ID comprises querying the locally stored authorized list of EEC IDs. 7. The edge configuration server of claim 5 , further configured to perform operations comprising: when the EEC ID is authorized, sending an authentication verification to an Authentication and Key Management for Applications (AKMA) anchor function (AAnF) of a core network to which the edge data network is communicatively coupled, the authentication verification comprising the EEC ID and other information used to authenticate the EEC; receiving an authentication response from the AAnF; and when the authentication response indicates a successful authentication of the EEC, accepting the application registration request from the EEC. 8. The edge configuration server of claim 7 , wherein the other information used to authenticate the EEC includes at least a MAC EEC . 9. The edge configuration server of claim 7 , wherein the other information used to authenticate the EEC includes at least an AKMA key identifier (A-KID). 10. The edge configuration server of claim 5 , further configured to perform operations comprising: when the EEC ID is not authorized, sending an authentication verification response failure message based on the authentication procedure to the edge configuration server. 11. An Authentication and Key Management for Applications (AKMA) anchor function (AAnF) of a core network configured to perform operations comprising: receiving an authentication verification request from an edge configuration server (ECS) of an edge data network, the authentication verification request comprising an edge enabler client (EEC) identification (EEC ID) and other information used to authenticate an EEC; sending a verification request to an edge enabler server (EES) of the edge data network to request authentication of the EEC ID; and receiving a verification response from the EES based on whether the EEC ID is authorized. 12. The AAnF of claim 11 , further configured to perform operations comprising: when the EEC ID is authorized, performing an authentication procedure using the EEC ID and the other information to authenticate the EEC; and sending an authentication verification response based on the authentication procedure to the edge configuration server. 13. The AAnF of claim 11 , further configured to perform operations comprising: storing a K AKMA and an AKMA key identifier (A-KID) that were independently generated. 14. The AAnF of claim 13 , wherein generating the K AKMA and the AKMA key is based on a K AUSF key. 15. The AAnF of claim 13 , wherein the K AKMA and the AKMA key were generated using the AKMA procedure as described in 3GPP TS 33.535. 16. The AAnF of claim 13 , further configured to perform operations comprising: retrieving the K AKMA using the A-KID. 17. The AAnF of claim 16 , further configured to perform operations comprising: calculating a KEDGE from the K AKMA . 18. The AAnF of claim 17 , further configured to perform operations comprising: verifying the MAC EEC using the KEDGE and the EEC ID. 19. The AAnF of claim 11 , wherein the verification response indicates a success when the EEC ID is authorized. 20. The AAnF of claim 11 , wherein the verification response indicates a failure when the EEC ID is not authorized.

Assignees

Inventors

Classifications

  • Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration · CPC title

  • Self-organising networks, e.g. ad-hoc networks or sensor networks · CPC title

  • Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

  • for accessing one among a plurality of replicated servers · CPC title

  • including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials} · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12323793B2 cover?
An edge enabler server of an edge data network is configured to receive a verification request comprising an edge enabler client identification (EEC ID), wherein the EEC ID uniquely identifies an edge enabler client (EEC), determine whether the EEC ID is an authorized EEC ID and provide a verification response based on whether the EEC ID is authorized.
Who is the assignee on this patent?
Apple Inc
What technology area does this patent fall under?
Primary CPC classification H04W12/06. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jun 03 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).