# US 2026/0089507 A1 · Method and device for managing user agreement information in mobile communication system

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

- Number: US 2026/0089507 A1
- Document ID: US20260089507A1
- Status: Published application
- Kind: A1
- Application number: 19/111,024
- Filed: 2023-08-29
- Published: 2026-03-26
- Earliest claimed: 2022-09-28
- Assignees: Samsung Electronics Co., Ltd.
- Applicants: Samsung Electronics Co., Ltd.
- Inventors: Hongjin CHOI; Duckey LEE
- Web page: https://patentgrep.com/patent/US20260089507A1

## CPC

- H04W 12/082: using revocation of authorisation
- H04L 9/32: 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}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04W 12/30: Security of mobile devices; Security of mobile applications
- H04W 12/61: Time-dependent
- H04W 12/69: Identity-dependent
- 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

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transfer rate. A method performed by a terminal of a mobile communication system according to the present disclosure comprises the steps of: receiving a user authentication request for an API call from a first network entity; generating a first token to authenticate the API call; transmitting the first token to the first network entity as a response for the user authentication request; generating a first discard token for discarding the first token; and transmitting the first discard token to a second network entity.

## Claims

### Claim 1

A method performed by a terminal of a mobile communication system, the method comprising:
receiving, from a first network entity, a user authentication request for an API invocation;
generating a first token for authentication regarding the API invocation;
transmitting, to the first network entity, the first token in response to the user authentication request;
generating a first revocation token for revoking the first token; and
transmitting, to a second network entity, the first revocation token.

### Claim 2 (depends on 1)

The method of claim 1, wherein claims of the first token comprise at least one of a name of an API, information of the first network entity, a time of generation of the first token, a validity time of the first token, or information of a third network entity.

### Claim 3 (depends on 2)

The method of claim 2, wherein the generating of the first token for authentication regarding the API invocation further comprises generating first token verification information, based on the claims of the first token.

### Claim 4 (depends on 1)

The method of claim 1,
wherein claims of the first revocation token comprise at least one of a name of an API, information of the first network entity, or a time of generation of the first revocation token, and
wherein the generating of the first revocation token further comprises generating first revocation token verification information, based on the claims of the first revocation token.

### Claim 5

A method performed by a network entity of a mobile communication system, the method comprising:
receiving, from an API invoker, a first token for authentication regarding an API invocation;
receiving a first revocation token for revocation of the first token; and
revoking the first token, based on the first revocation token.

### Claim 6 (depends on 5)

The method of claim 5, wherein the revoking of the first token, based on the first revocation token, further comprises searching for the first token, based on information regarding the API invoker or API name information included in the first revocation token.

### Claim 7 (depends on 6)

The method of claim 6,
wherein the revoking of the first token, based on the first revocation token, further comprises comparing a time of generation of the first revocation token and a time of generation of the first token, and
wherein the first token is revoked in case that the time of generation of the first token precedes the time of generation of the first revocation token.

### Claim 8 (depends on 5)

The method of claim 5, further comprising:
storing the first revocation token; and
transmitting, to a second network entity, information indicating revocation of the first token.

### Claim 9

A terminal of a mobile communication system, the terminal comprising:
a transceiver; and
a controller,
wherein the controller is configured to:
receive, from a first network entity, a user authentication request for an API invocation,
generate a first token for authentication regarding the API invocation,
transmit, to the first network entity, the first token in response to the user authentication request,
generate a first revocation token for revoking the first token, and
transmit, to a second network entity, the first revocation token.

### Claim 10 (depends on 9)

The terminal of claim 9, wherein claims of the first token comprise at least one of a name of an API, information of the first network entity, a time of generation of the first token, a validity time of the first token, or information of a third network entity.

### Claim 11 (depends on 10)

The terminal of claim 10, wherein the generating of the first token for authentication regarding the API invocation further comprises generating first token verification information, based on the claims of the first token.

### Claim 12 (depends on 9)

The terminal of claim 9,
wherein claims of the first revocation token comprise at least one of a name of an API, information of the first network entity, or a time of generation of the first revocation token, and
wherein the operation of generating the first revocation token for revoking the first token further comprises generating first revocation token verification information, based on the claims of the first revocation token.

### Claim 13

A network entity of a mobile communication system, the network entity comprising:
a transceiver; and
a controller,
wherein the controller is configured:
receive, from an API invoker, a first token for authentication regarding an API invocation,
receive a first revocation token for revocation of the first token, and
revoke the first token, based on the first revocation token.

### Claim 14 (depends on 13)

The network entity of claim 13, wherein the revoking of the first token, based on the first revocation token, further comprises searching for the first token, based on information regarding the API invoker or API name information included in the first revocation token.

### Claim 15 (depends on 14)

The network entity of claim 14, wherein revoking of the first token, based on the first revocation token, further comprises comparing a time of generation of the first revocation token and a time of generation of the first token, and
wherein the first token is revoked in case that the time of generation of the first token precedes the time of generation of the first revocation token.
