# US 11,451,953 B2 · Methods, network function nodes and computer readable media for event subscription management

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

- Number: US 11,451,953 B2
- Document ID: US11451953B2
- Status: Granted
- Kind: B2
- Application number: 16/482,541
- Filed: 2019-06-13
- Published: 2021-10-28
- Granted: 2022-09-20
- Earliest claimed: 2018-11-16
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Hongxia Long
- Web page: https://patentgrep.com/patent/US11451953B2

## CPC

- H04W 8/18: Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04L 41/082: the condition being updates or upgrades of network functionality
- H04W 88/18: Service support devices; Network management devices
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- 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 provides methods for event subscription management in a network comprising a set of NF nodes, and corresponding NF nodes. The method comprises receiving a subscription request of an event for a user from an event subscriber, in response to receipt of the subscription request, transmitting, to a second network function node, a query request for querying whether the event for the user has been subscribed; and if a response to the query request from the second network function node indicates that the event for the user has been subscribed, transmitting, to the second network function node, an updating request for updating a subscriber list of the event for the user by the second network function node to include the event subscriber into the subscriber list. The present disclosure further discloses a corresponding method which comprises receiving a query request from a first network function node for querying whether an event for a user has been subscribed, in response to reception of the query request, checking whether an indicator indicating the event for the user has been subscribed has been set, and transmitting a check result to the first network function node. The present disclosure further provides corresponding computer readable medium.

## Claims

### Claim 1

A method implemented at a first network function node for managing event subscription, comprising:
receiving a subscription request of an event for a user from an event subscriber,
in response to receipt of the subscription request, transmitting, to a second network function node, a query request for querying whether the event for the user has been subscribed; and
if a response to the query request from the second network function node indicates that the event for the user has been subscribed, transmitting, to the second network function node, an updating request for updating a subscriber list of the event for the user by the second network function node to include the event subscriber into the subscriber list.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
initiating subscription of the event for the user with a serving node if the response to the query request indicates that the event for the user has not been subscribed; and
transmitting a creating request with identification information of the event subscriber for creating the subscriber list for the event of the user and including the event subscriber in the created subscriber list by the second network node.

### Claim 3 (depends on 1)

The method of claim 1 wherein the first network function node is one of a Unified Data Management (UDM), a Network Exposure Function (NEF), and an Access and Mobility Management Function (AMF).

### Claim 4 (depends on 1)

The method of claim 1, wherein the second network function node is a Unified Data Repository (UDR).

### Claim 5

A method implemented at a second network function node for managing event subscription, comprising:
receiving a query request from a first network function node for querying whether an event for a user has been subscribed,
in response to reception of the query request, checking whether an indicator indicating the event for the user has been subscribed has been set, and
transmitting a check result to the first network function node.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
receiving an updating request for updating a subscriber list of the event for the user with an event subscriber to the event from the first network function node, and
in response to reception of the updating request, updating a subscriber list of the event for the user to include the event subscriber.

### Claim 7 (depends on 5)

The method of claim 5, further comprising:
receiving a creating request with identification information of the event subscriber to subscribe the event for the user from the first network function node,
in response to reception of the creating request, setting the indicator; and
creating the subscriber list of the event for the user and including the event subscriber into the subscriber list of the event for the user.

### Claim 8 (depends on 7)

The method of claim 7, wherein the indicator is set in a table stored in the second network function node that describes event subscription of the user.

### Claim 9 (depends on 7)

The method of claim 7, wherein the subscriber list is created in a table stored in the second network function node that describes subscription of the event for the user.

### Claim 10 (depends on 5)

The method of claim 5, wherein the first network function node is one of a Unified Data Management (UDM), a Network Exposure Function (NEF), and an Access and Mobility Management Function (AMF).

### Claim 11 (depends on 5)

The method of claim 5, wherein the second network function node is a Unified Data Repository (UDR).

### Claim 12

A method implemented at a first network function node for managing event un-subscription, comprising:
receiving an un-subscription request of an event for a user from an event subscriber to un-subscribe the event,
in response to reception of the un-subscription request, transmitting, to a second network function node, a query request for querying whether the event subscriber is a last subscriber for the event of the user in a subscriber list of the event for the user; and
if a response to the query request from the second network function node indicates that the event subscriber is not the last subscriber for the event of the user, transmitting a removing request to the second network function node, for removing, by the second network function node, the event subscriber from the subscriber list of the event for the user.

### Claim 13 (depends on 12)

The method of claim 12, wherein the removing request includes identification information of the event subscriber.

### Claim 14 (depends on 12)

The method of claim 12, further comprising:
if the response to the query request indicates that the event subscriber is the last subscriber for the event of the user, transmitting an event removing request to the second network function node for removing the subscriber list by the second network function node; and
initiating un-subscription of the event for the user with a serving node.

### Claim 15 (depends on 12)

The method of claim 12, wherein the first network function node is one of a Unified Data Management (UDM), a Network Exposure Function (NEF), and an Access and Mobility Management Function (AMF).

### Claim 16 (depends on 12)

The method of claim 12, wherein the second network function node is a Unified Data Repository (UDR).

### Claim 17

A method implemented at a second network function node for managing event un-subscription, comprising:
receiving a query request for an event subscriber to un-subscribe an event for a user, from a first network function node for querying whether the event subscriber is a last subscriber for the event of the user in a subscriber list of the event for the user,
in response to reception of the query request, checking whether the event subscriber is the last subscriber in the subscriber list of the event for the user, and
transmitting a check result to the first network function node.

### Claim 18 (depends on 17)

The method of claim 17, further comprising:
receiving a removing request from the first network function node for removing the event subscriber from the subscriber list of the event for the user, and
in response to reception of the removing request, removing the event subscriber from the subscriber list of the event for the user.

### Claim 19 (depends on 18)

The method of claim 18, wherein the removing request includes identification information of the event subscriber to un-subscribe the event.

### Claim 20 (depends on 17)

The method of claim 17, further comprising:
receiving an event removing request for removing the subscriber list from the first network function node, and
in response to reception of the event removing request, removing the subscriber list of the event for the user.

### Claim 21 (depends on 20)

The method of claim 20, further comprising:
removing an indicator indicating the event of the user has been subscribed.

### Claim 22 (depends on 21)

The method of claim 21, wherein the removing the indicator comprises removing the indicator from a table stored in the second network function node that describes event subscription of the user.

### Claim 23 (depends on 20)

The method of claim 20, wherein the removing the subscriber list comprises removing the subscriber list from a table stored in the second network function node that describes subscription of the event for the user.