# US 2023/0422158 A1 · Non-ip data delivery authorization update method and connection release method for non-ip data delivery, and device for performing the method

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

- Number: US 2023/0422158 A1
- Document ID: US20230422158A1
- Status: Published application
- Kind: A1
- Application number: 18/243,419
- Filed: 2023-09-07
- Published: 2023-12-28
- Earliest claimed: 2019-04-02
- Assignees: Electronics and Telecommunications Research Institute
- Applicants: Electronics and Telecommunications Research Institute
- Inventors: Seung-Ik LEE
- Web page: https://patentgrep.com/patent/US20230422158A1

## CPC

- H04W 48/18: Selecting a network or a communication service
- H04W 4/12: Messaging; Mailboxes; Announcements
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 8/18: Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W 76/11: Allocation or use of connection identifiers
- H04W 80/10: adapted for {application} session management, e.g. SIP [Session Initiation Protocol] {(connection management H04W76/00; arrangements for session management H04L67/14)}
- H04W 76/12: Setup of transport tunnels
- H04W 88/14: Backbone network devices
- H04W 88/16: Gateway arrangements
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Disclosed are a non-IP data delivery (NIDD) authorization update method and connection release method for the non-IP data delivery and device for performing the method. The NIDD authorization update method is initiated by a UDM device, and the connection release method between a SMF device and a NEF device is initiated by the SMF device or the NEF device.

## Claims

### Claim 1

A method of Non-IP Data Delivery (NIDD) configuration, the method comprising:
transmitting a first message including a first identifier and a second identifier for asking second request message requesting NIDD configuration to an UE (user equipment)
receiving the second request message; and
transmitting a response message in response to the second request message
wherein the second request message includes a third identifier based on a setting value of Requested Action.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first identifier is for a Network Exposure Function (NEF) and the second identifier is for an Application Function (AF).

### Claim 3 (depends on 1)

The method of claim 1, wherein third identifier is T8 Long Term Transaction Reference ID (TLTRI) T8 Long Term Transaction Reference ID (TLTRI).

### Claim 4 (depends on 1)

The method of claim 1, wherein the setting value of Requested Action is set to “Update”.

### Claim 5 (depends on 1)

The method of claim 1, wherein the setting value of Requested Action is set to “Cancel”.

### Claim 6 (depends on 1)

The method of claim 1, wherein the second request message includes Generic Public Subscription Identifier (GPSI), External Group Identifier, AF device Identify (ID), NIDD Duration, T8 Destination Address, Reliable Data Service Configuration or Machine Type Communication (MTC) Provider Information, and
wherein the response message includes TLTRI, Maximum Packet Size, Reliable Data Service Indication, or Cause.