# US 2025/0159025 A1 · Method, apparatus and computer program

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

- Number: US 2025/0159025 A1
- Document ID: US20250159025A1
- Status: Published application
- Kind: A1
- Application number: 18/938,738
- Filed: 2024-11-06
- Published: 2025-05-15
- Earliest claimed: 2023-11-13
- Assignees: Nokia Technologies Oy
- Applicants: Nokia Technologies Oy
- Inventors: Saurabh KHARE; Rainer LIEBHART; Alexander MILINSKI
- Web page: https://patentgrep.com/patent/US20250159025A1

## CPC

- H04L 65/1069: Session establishment or de-establishment
- H04L 65/1016: IP multimedia subsystem [IMS]
- H04L 65/1063: Application servers providing network services (systems providing special services to telephonic subscribers H04M3/42)
- H04L 65/1073: Registration or de-registration
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

There is provided a method performed by a home subscriber server or unified data management function, the method comprising: receiving one or more internet protocol multimedia subsystem, IMS, profiles from one or more IMS application servers, IMS ASs, each IMS profile comprising IMS AS identifying information and one or more parameters of a respective IMS AS of the one or more IMS ASs; storing the received one or more IMS profiles; receiving, from a consumer network function, a second message comprising a discovery request indicating a target network function type as IMS AS and one or more target parameters; and sending, to the consumer network function, an IMS profile comprising one or more parameters matching the one or more target parameters.

## Claims

### Claim 1

An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform:
receiving one or more internet protocol multimedia subsystem, IMS, profiles from one or more IMS application servers, IMS ASs, each IMS profile comprising IMS AS identifying information and one or more parameters of a respective IMS AS of the one or more IMS ASs;
storing the received one or more IMS profiles;
receiving, from a consumer network function, a second message comprising a discovery request indicating a target network function type as IMS AS and one or more target parameters; and
sending, to the consumer network function, an IMS profile comprising one or more parameters matching the one or more target parameters.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the one or more parameters comprise at least one of the following:
information indicating one or more IMS services provided by the IMS AS;
information indicating one or more users for which the IMS AS supports IMS services;
information indicating one or more groups of users for which the IMS AS supports IMS services;
information indicating one or more user categories for which the IMS AS supports IMS services; or
information indicating one or more events and services that can be exposed by the IMS AS.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the IMS AS identifying information comprises at least one of the following:
an IMS AS instance identifier or IMS AS set identifier;
a session initiation protocol uniform resource identifier via which the IMS AS can be reached; or
an IMS AS diameter address of the IMS AS.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the one or more IMS profiles are stored at the home subscriber server or unified data management function and associated to one or more user identifiers.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the one or more target parameters comprises at least one of the following:
information indicating one or more target IMS services provided by an IMS AS;
information indicating one or more target users for which an IMS AS supports IMS services;
information indicating one or more target groups of users for which an IMS AS supports IMS services; or
information indicating one or more target events and services exposed by an IMS AS.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the first message and/or second message comprises one of: a diameter protocol message or a service based interface message.

### Claim 7 (depends on 6)

The apparatus of claim 6, wherein the first message is a diameter protocol message and comprises a profile update request or a server assignment request.

### Claim 8 (depends on 1)

The apparatus of claim 1, wherein the apparatus is further caused to perform:
determining that no IMS profile comprising one or more parameters matching the one or more target parameters is stored at the home subscriber server or unified data management function;
creating a subscription associated with the consumer network function based on the one or more target parameters;
receiving a further IMS profile from an IMS AS, wherein the further IMS profile comprises one or more parameters matching the one or more target parameters; and
sending a notification message to the consumer network function including the IMS profile comprising one or more parameters matching the one or more target parameters.

### Claim 9

An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform:
sending, to a home subscriber server or unified data management function, a second message comprising a discovery request indicating a target network function type as internet protocol multimedia subsystem application server, IMS AS, and one or more filter parameters defining one or more target parameters;
receiving, from the home subscriber server or unified data management function, an IMS profile based on the one or more filter parameters; and
connecting to the IMS AS based on the received IMS profile.

### Claim 10 (depends on 9)

The apparatus of claim 9, wherein the one or more target parameters comprises at least one of the following:
information indicating one or more target IMS services provided by an IMS AS;
information indicating one or more target users for which an IMS AS supports IMS services;
information indicating one or more target groups of users for which an IMS AS supports IMS services;
or
information indicating one or more target events and services exposed by an IMS AS.

### Claim 11 (depends on 9)

The apparatus of claim 9, wherein the received IMS profile comprises at least one of the following:
IMS AS identifying information;
information indicating one or more IMS services provided by the IMS AS;
information indicating one or more users for which the IMS AS supports IMS services;
information indicating one or more groups of users for which the IMS AS supports IMS services;
information indicating one or more user categories for which the IMS AS supports IMS services; and
information indicating one or more events and services exposed by the IMS AS.

### Claim 12 (depends on 11)

The apparatus of claim 11, wherein the IMS AS identifying information comprises at least one of the following:
an IMS AS instance identifier or IMS AS set identifier;
a session initiation protocol uniform resource identifier via which the IMS AS can be reached; or
an IMS AS diameter address of the IMS AS.

### Claim 13 (depends on 12)

The apparatus of claim 12, wherein the IMS AS identifying information comprises the IMS AS instance identifier or the IMS AS set identifier, and wherein the apparatus is further caused to perform:
sending, to a network repository function, a third message comprising a further discovery request indicating the IMS AS instance identifier or IMS AS set identifier;
receiving, from the network repository function, an IMS AS address based on the third message; and
connecting to the IMS AS based on the received IMS AS address.

### Claim 14 (depends on 13)

The apparatus of claim 13, wherein the further discovery request further comprises at least one of the following:
an indication that service exposure via a network exposure function is supported;
information indicating the supported capabilities of the IMS AS;
information identifying one or more users of the IMS AS;
information identifying one or more groups of users of the IMS AS; or
information indicating one or more user categories supported by the IMS AS.

### Claim 15

An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform:
providing IMS services to one or more users or one or more groups of users; and
sending, to a home subscriber server or unified data management function, a first message comprising an IMS profile of the IMS AS.

### Claim 16 (depends on 15)

The apparatus of claim 15, wherein the first message comprises one of: a diameter protocol message or a service based interface message.

### Claim 17 (depends on 16)

The apparatus of claim 16, wherein the diameter protocol message comprises a profile update request or a server assignment request.

### Claim 18 (depends on 16)

The apparatus of claim 16, wherein the IMS profile comprises at least one of the following:
IMS AS identifying information;
information indicating one or more IMS services provided by the IMS AS;
information indicating one or more users for which the IMS AS supports IMS services;
information indicating one or more groups of users for which the IMS AS supports IMS services;
information indicating one or more user categories for which the IMS AS supports IMS services; or
information indicating one or more events and services exposed by the IMS AS.

### Claim 19 (depends on 18)

The apparatus of claim 18, wherein the IMS AS identifying information comprises at least one of the following:
an IMS AS instance identifier or IMS AS set identifier;
a session initiation protocol uniform resource identifier via which the IMS AS can be reached; or
an IMS AS diameter address of the IMS AS.

### Claim 20 (depends on 16)

The apparatus of claim 16, wherein the apparatus is further caused to perform:
sending, to a network repository function, a registration message comprising at least one of the following:
information indicating whether the IMS AS supports service exposure via a network exposure function;
information indicating one or more IMS services provided by the IMS AS;
information indicating one or more users for which the IMS AS supports IMS services;
information indicating one or more groups of users for which the IMS AS supports IMS services;
information indicating one or more user categories for which the IMS AS supports IMS services; or
information indicating one or more events and services exposed by the IMS AS.
