# US 2023/0276231 A1 · Authentication Between Wireless Devices and Edge Servers

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0276231 A1
- Document ID: US20230276231A1
- Status: Published application
- Kind: A1
- Application number: 17/916,960
- Filed: 2021-10-28
- Published: 2023-08-31
- Earliest claimed: 2021-10-28
- Assignees: Apple Inc.
- Applicants: Apple Inc.
- Inventors: Shu Guo; Dawei Zhang; Huarui Liang; Haijing Hu
- Web page: https://patentgrep.com/patent/US20230276231A1

## CPC

- H04W 12/041: Key generation or derivation
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04W 12/0431: Key distribution or pre-distribution; Key agreement
- H04W 12/06: Authentication
- H04W 12/69: Identity-dependent
- H04W 60/04: using triggered events
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

This disclosure relates to techniques for performing wireless communications including authentication between user equipment and edge computing servers. One or more edge enabler client(s) operating at a user equipment may authenticate with one or more edge computing server(s). The authentication may use generic bootstrapping architecture, among various possibilities.

## Claims

### Claim 1

A method, comprising:
at a user equipment (UE):
performing a first bootstrapping procedure with a first edge server, the first bootstrapping procedure including generating a first key;
generating a first authentication code for a first edge enabler client (EEC) operating at the UE, wherein the first authentication code is for use with the first edge server;
transmitting a first registration request for the first EEC to the first edge server, the first registration request including the first authentication code;
receiving, from the first edge server, a first registration success message comprising first information for authenticating with a second edge server;
generating a second authentication code for the first EEC, wherein the second authentication code is for use with the second edge server;
transmitting a second registration request for the first EEC to the second edge server, the second registration request including the second authentication code;
receiving, from the second edge server, a second registration success message comprising second information for discovery of a third edge server; and
discovering the third edge server using the second information.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first authentication code is based on the first key and an identifier of the first EEC.

### Claim 3 (depends on 1)

The method of claim 1, wherein at least one of the first authentication code and the second authentication code is generated using a SHA-256 hashing algorithm.

### Claim 4 (depends on 1)

The method of claim 1, wherein the first edge server comprises an edge configuration server, the second edge server comprises an edge enabler server, and the third edge server comprises an edge application server.

### Claim 5 (depends on 1)

The method of claim 1, further comprising exchanging application data of an application associated with the first EEC with the third edge server.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
establishing communication with a cellular network;
performing a primary authentication with the cellular network;
receiving a UE identifier from the cellular network after the primary authentication, wherein the UE identifier is one of an IP multimedia private identity (IMPI) or temporary IMPI (TMPI); and
including the UE identifier as a username for the first bootstrapping procedure, wherein the first bootstrapping procedure comprises a generic bootstrapping architecture (GBA) procedure.

### Claim 7 (depends on 1)

The method of claim 1, wherein the method further comprises:
performing a second bootstrapping procedure with the second edge server using the first information for authentication with the second edge server, the second bootstrapping procedure including generating a second key.

### Claim 8 (depends on 7)

The method of claim 7, wherein the second authentication code is based on the second key and an identifier of the first EEC.

### Claim 9 (depends on 7)

The method of claim 7, wherein the method further comprises:
generating a third authentication code for a second EEC operating at the UE, wherein the third authentication code is for use with the first edge server;
transmitting a third registration request for the second EEC to the first edge server, the third registration request including the third authentication code;
receiving, from the first edge server, a third registration success message comprising third information for authenticating with a fourth edge server;
generating a fourth authentication code for the second EEC, wherein the fourth authentication code is for use with the fourth edge server;
transmitting a fourth registration request for the second EEC to the fourth edge server, the fourth registration request including the fourth authentication code; and
receiving, from the fourth edge server, a fourth registration success message.

### Claim 10 (depends on 9)

The method of claim 9, wherein the fourth edge server is the same as the second edge server.

### Claim 11 (depends on 9)

The method of claim 9, wherein the fourth edge server is different from the second edge server.

### Claim 12 (depends on 9)

The method of claim 9, wherein the third authentication code is based on the first key and an identifier of the second EEC.

### Claim 13 (depends on 1)

The method of claim 1, wherein the first information for authenticating with the second edge server comprises a first token.

### Claim 14 (depends on 13)

The method of claim 13, wherein the second registration request further includes the first token.

### Claim 15 (depends on 14)

The method of claim 14, wherein the method further comprises:
generating a third authentication code for a second EEC operating at the UE, wherein the third authentication code is for use with the first edge server;
transmitting a third registration request for the second EEC to the first edge server, the third registration request including the third authentication code;
receiving, from the first edge server, a third registration success message comprising third information for authenticating with a fourth edge server;
generating a fourth authentication code for the second EEC, wherein the fourth authentication code is for use with the fourth edge server;
transmitting a fourth registration request for the second EEC to the fourth edge server, the fourth registration request including the fourth authentication code; and
receiving, from the fourth edge server, a fourth registration success message.

### Claim 16 (depends on 15)

The method of claim 15, wherein the third information for authenticating with the fourth edge server comprises a second token.

### Claim 17

(canceled)

### Claim 18

A method for operating an edge configuration server, the method comprising:
establishing communication with a bootstrapping server function (BSF);
receiving, from the BSF, a first key associated with a first user equipment (UE);
establishing communication with the UE;
receiving, from a first edge enabler client (EEC) of the UE, a first application registration request comprising:
an identifier of the first EEC; and
a first message authentication code (MAC);
verifying the first MAC based on the first key and the identifier of the first EEC; and
in response to successfully verifying the identifier of the first EEC, providing, to the UE, information for authenticating an edge enablement server.

### Claim 19 (depends on 18)

The method of claim 18, wherein the information for authenticating the edge enablement server comprises a token, the method further comprising providing the token to the edge enablement server.

### Claim 20

(canceled)

### Claim 21

An apparatus, comprising:
a processor configured to cause a user equipment (UE) to:
perform a first bootstrapping procedure with a first edge server, the first bootstrapping procedure including generating a first key;
generate a first authentication code for a first edge enabler client (EEC) operating at the UE, wherein the first authentication code is for use with the first edge server;
transmit a first registration request for the first EEC to the first edge server, the first registration request including the first authentication code;
receive, from the first edge server, a first registration success message comprising first information for authenticating with a second edge server;
generate a second authentication code for the first EEC, wherein the second authentication code is for use with the second edge server;
transmit a second registration request for the first EEC to the second edge server, the second registration request including the second authentication code;
receive, from the second edge server, a second registration success message comprising second information for discovery of a third edge server; and
discover the third edge server using the second information.

### Claim 22 (depends on 21)

The apparatus of claim 21, further comprising:
a radio operably coupled to the processor.
