# US 2021/0243067 A1 · Apparatus and method for handling managed object priorities in 5g network

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

- Number: US 2021/0243067 A1
- Document ID: US20210243067A1
- Status: Published application
- Kind: A1
- Application number: 17/269,796
- Filed: 2018-08-24
- Published: 2021-08-05
- Earliest claimed: 2018-08-24
- Assignees: Nokia Solutions and Networks Oy
- Applicants: Nokia Solutions and Networks Oy
- Inventors: Jing PING; Anatoly ANDRIANOV; Olaf POLLAKOWSKI
- Web page: https://patentgrep.com/patent/US20210243067A1

## CPC

- H04L 41/0233: Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 41/0896: Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76)
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04W 28/16: Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W 72/56: based on priority criteria
- 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, methods, apparatuses, and computer program products for handling managed object priorities in a network, such as 5G are provided. One method includes receiving a constraint on a priority of a managed object, assigning a priority value satisfying the received constraint to an instance of the managed object, identifying a supporting resource for the managed object with the assigned priority value, and assigning a priority for the supporting resource, using the assigned priority value as a constraint.

## Claims

### Claim 1

An apparatus, comprising:
at least one processor; and
at least one memory comprising computer program code,
the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to
receive a constraint on a priority of a managed object;
assign a priority value satisfying the received constraint to an instance of the managed object;
identify a supporting resource for the managed object with assigned priority value; and
assign a priority for the supporting resource using the assigned priority value as a constraint.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to:
identify dependent managed objects of the managed object based on an object containment relationship in an object structure including the managed object;
assign priority values to instances of the identified dependent managed objects using the assigned priority value as a constraint.

### Claim 3 (depends on 1)

The apparatus according to claim 1, wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to
calculate the priority value for the managed object.

### Claim 4 (depends on 1)

The apparatus according to claim 1, wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to
receive the priority for the managed object from a management function which manages the managed object.

### Claim 5 (depends on 1)

The apparatus according to claim 1, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to
monitor the supporting resource using the priority value of the managed object as a constraint.

### Claim 6 (depends on 1)

The apparatus according to claim 1, wherein the managed object comprises at least one of:
a 3GPP Managed Function;
a 3GPP Managed Element;
a 3GPP Sub Network;
a 3GPP Network Slice;
a 3GPP Network Slice Subnet;
an ETSI NFV NS;
an ETSI NFV VNF;
an ETSI NFV VNFC; or
an ETSI NFV VR.

### Claim 7 (depends on 1)

The apparatus according to claim 1, wherein, when the managed object comprises a root managed object, the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:
derive the priority value based on at least one of a service level agreement, communication service type, and customer type.

### Claim 8 (depends on 1)

The apparatus according to claim 1, wherein, when the managed object comprises a child managed object, the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:
derive the priority value based on at least one of a priority of one or more parent managed objects, a priority of one or more child managed objects, a weight of the priority of the one or more child managed objects, a weight of the priority of the one or more parent managed objects, the number of the one or more child managed objects, and the number of the one or more parent managed objects.

### Claim 9 (depends on 1)

The apparatus according to claim 1, wherein the priority of the managed object is exchanged inside a management function, or between management functions of a same management domain, or between management domains.

### Claim 10 (depends on 1)

The apparatus according to claim 1, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus to recursively perform the steps of assigning, identifying and assigning for each managed object.

### Claim 11

(canceled)

### Claim 12

A method, comprising:
receiving a constraint on a priority of a managed object;
assigning a priority value satisfying the received constraint to an instance of the managed object;
identifying a supporting resource for the managed object with the assigned priority value; and
assigning a priority for the supporting resource, using the assigned priority value as a constraint.

### Claim 13 (depends on 12)

The method according to claim 12, further comprising:
identifying dependent managed objects of the managed object based on an object containment relationship in an object structure including the managed object; and
assigning priority values to instances of the identified dependent managed objects using the assigned priority value as a constraint.

### Claim 14 (depends on 12)

The method according to claim 12, wherein assigning the priority value comprises:
calculating the priority value for the managed object.

### Claim 15 (depends on 12)

The method according to claim 12, wherein assigning the priority value comprises:
receiving the priority for the managed object from a management function which manages the managed object.

### Claim 16 (depends on 12)

The method according to claim 12, further comprising:
monitoring the supporting resource using the priority value of the managed object as a constraint.

### Claim 17 (depends on 12)

The method according to claim 12, wherein the managed object comprises at least one of:
a 3GPP Managed Function;
a 3GPP Managed Element;
a 3GPP Sub Network;
a 3GPP Network Slice;
a 3GPP Network Slice Subnet;
an ETSI NFV NS;
an ETSI NFV VNF;
an ETSI NFV VNFC; or
an ETSI NFV VR.

### Claim 18 (depends on 12)

The method according to claim 12, wherein, when the managed object comprises a root managed object, assigning the priority value comprises:
deriving the priority value based on at least one of a service level agreement, communication service type, and customer type.

### Claim 19 (depends on 12)

The method according to claim 12, wherein, when the managed object comprises a child managed object, assigning the priority value comprises:
deriving the priority value based on at least one of a priority of one or more parent managed objects, a priority of one or more child managed objects, a weight of the priority of the one or more child managed objects, a weight of the priority of the one or more parent managed objects, the number of the one or more child managed objects, and the number of the one or more parent managed objects.

### Claim 20 (depends on 12)

The method according to claim 12, wherein the priority of the managed object is exchanged inside a management function, or between management functions of a same management domain, or between management domains.

### Claim 21

(canceled)

### Claim 22 (depends on 12)

A computer program embodied on a non-transitory computer readable medium, said computer program comprising program instructions stored thereon which, when executed on an apparatus, cause the apparatus to perform the method according to claim 12.