# US 2026/0313030 A1 · Automated relationship management of service layer entities in a communications network

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

- Number: US 2026/0313030 A1
- Document ID: US20260313030A1
- Status: Published application
- Kind: A1
- Application number: 19/714,659
- Filed: 2026-06-22
- Published: 2026-10-08
- Earliest claimed: 2018-08-02
- Assignees: Ipla Holdings Inc.
- Applicants: IPLA Holdings Inc.
- Inventors: Dale N. SEED; Catalina Mihaela MLADIN; Quang LY; Zhuo CHEN; William Robert FLYNN, IV; Lu LIU; Jiwan NINGLEKHU; Michael F. STARSINIC; Chonggang WANG
- Web page: https://patentgrep.com/patent/US20260313030A1

## CPC

- H04L 67/125: involving control of end-device applications over a network
- H04L 41/0894: Policy-based network configuration management
- H04W 4/38: for collecting sensor information
- H04W 4/50: Service provisioning or reconfiguring
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)}
- H04W 72/04: Wireless resource allocation
- H04W 84/18: Self-organising networks, e.g. ad-hoc networks or sensor networks
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Systems and methods are described to automate managing of relationships between IoT entities (e.g., devices, apps, users) and offloading the burden of managing these relationships from users. A Relationship Management Service (RM Service) is described herein for the autonomous establishment, modification, and tear-down of relationships between IoT entities.

## Claims

### Claim 1

An apparatus comprising a processor and a memory, the apparatus being connected to a communications network, the apparatus further including computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, cause the apparatus to implement a service layer entity on the communications network and cause the service layer entity to:
register a first apparatus connected to the communications network;
receive first metadata from the first apparatus;
register a second apparatus connected to the communications network;
receive second metadata from the second apparatus;
determine, based on the first metadata received from the first apparatus and the second metadata received from the second apparatus, a trigger condition of a Relationship Management (RM) policy is met to establish a machine-to-machine (M2M)/Internet of Things (IoT) entity relationship between the first apparatus and the second apparatus;
establish, between the first apparatus and the second apparatus, the relationship corresponding to the trigger condition; and
perform an action based on the relationship between the first apparatus and the second apparatus wherein the action comprises performing one or more requests on behalf of the first apparatus or of the second apparatus.
