# US 2024/0406694 A1 · Network slicing coordination over next generation radio access networks

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

- Number: US 2024/0406694 A1
- Document ID: US20240406694A1
- Status: Published application
- Kind: A1
- Application number: 18/326,879
- Filed: 2023-05-31
- Published: 2024-12-05
- Earliest claimed: 2023-05-31
- Assignees: Radisys Corporation
- Applicants: Radisys Corporation
- Inventors: Bhawani Sankar SATPATHY; Rajendra Prasad KODAYPAK
- Web page: https://patentgrep.com/patent/US20240406694A1

## CPC

- H04W 4/50: Service provisioning or reconfiguring
- H04W 24/02: Arrangements for optimising operational condition
- H04W 48/18: Selecting a network or a communication service
- H04W 84/042: {Public Land Mobile systems, e.g. cellular systems}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A gNB-DU and a gNB-CU coordinate network slice information over an F1 interface by exchanging F1 setup request/response or gNB-DU configuration update/acknowledge messages indicating PLMNs and supported network slice information. In some embodiments, a UE provides its slice information that is checked at the gNB for support at an AMF. In response to determining that the UE network slice provisioning is unsupported, the gNB-DU triggers an RRC message including network slice information of neighboring cells.

## Claims

### Claim 1

A method, performed by a gNB-CU, for coordinating network slice information over an F1 interface with a gNB-DU, the method comprising:
receiving a first message from the gNB-DU over the F1 interface, in which the first message is an F1 setup request or an gNB-DU configuration update, and the first message indicating a first PLMN set provisioned at the gNB-DU with each PLMN of the first PLMN set having a first associated S-NSSAI set;
comparing the first PLMN set with a second PLMN set provisioned at the gNB-CU, each PLMN of the second PLMN set having a second associated S-NSSAI set, to determine matching network slice information for any common PLMNs among the first and second PLMN sets; and
triggering a second message for the gNB-DU, in which the second message is an F1 setup response or an gNB-DU configuration update acknowledge, and in which the second message indicates the matching network slice information for the common PLMNs among the first and second PLMN sets.

### Claim 2 (depends on 1)

The method of claim 1, in which, in response to all network slice information matching for a common PLMN, the second message omits a TAI slice support list associated with the common PLMN.

### Claim 3 (depends on 1)

The method of claim 1, in which, in response to a subset of network slice information differing for a common PLMN, the second message includes a TAI slice support list indicating matching network slice information for the common PLMN.

### Claim 4 (depends on 3)

The method of claim 3, in which the second message includes an extended TAI slice support list to supplement the TAI slice support list.

### Claim 5 (depends on 1)

The method of claim 1, in which the first message is the F1 setup request and the second message is the F1 setup response.

### Claim 6 (depends on 1)

The method of claim 1, in which the first message is the gNB-DU configuration update and the second message is the gNB-DU configuration update acknowledge.

### Claim 7 (depends on 1)

The method of claim 1, further comprising omitting from the second message any common PLMNs lacking at least one matching S-NSSAI.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
receiving a third message from the gNB-DU, in which the third message is a UL RRC message transfer indicating an S-NSSAI list generated in response to a UE indicating whether it has UE-supported network slicing information; and
triggering a fourth message for an initial registration of the UE with an AMF, the fourth message including allowed NSSAI information that is based on the UE-supported network slicing information.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
determining whether the UE-supported network slicing information matches AMF-supported network slice information; and
in response to determining there is no match, triggering a UE context release message including an anr-NSSAISupportList, the anr-NSSAISupportList indicating network slicing information for neighboring cells.

### Claim 10

A method, performed by a gNB-DU, for coordinating network slice information over an F1 interface with a gNB-CU, the method comprising:
generating a first message for the gNB-CU, in which the first message is an F1 setup request or an gNB-DU configuration update, and the first message indicating a first PLMN set provisioned at the gNB-DU with each PLMN of the first PLMN set having a first associated S-NSSAI set, the first message causing the gNB-CU to compare the first PLMN set with a second PLMN set provisioned at the gNB-CU, each PLMN of the second PLMN set having a second associated S-NSSAI set, so as to determine matching network slice information for any common PLMNs among the first and second PLMN sets;
in response to the first message, receiving a second message from the gNB-CU, in which the second message is an F1 setup response or an gNB-DU configuration update acknowledge, and in which the second message indicates matching network slice information for the common PLMNs among the first and second PLMN sets; and
storing the matching network slice information for coordination of UE-supported network slicing information with the matching network slice information.

### Claim 11 (depends on 10)

The method of claim 10, further comprising receiving a third message from a UE, the third message including the UE-supported network slicing information.

### Claim 12 (depends on 11)

The method of claim 11, further comprising determining that the UE-supported network slicing information is unsupported by an AMF and triggering an RRC release message including anr-NSSAISupportList indicating network slice support of neighboring cells.

### Claim 13 (depends on 11)

The method of claim 11, further comprising determining that the UE-supported network slicing information is unsupported by the gNB-DU and triggering an RRC release message including anr-NSSAISupportList indicating network slice support of neighboring cells.

### Claim 14 (depends on 10)

The method of claim 10, in which, in response to all network slice information matching for a common PLMN, the second message omits a TAI slice support list associated with the common PLMN.

### Claim 15 (depends on 10)

The method of claim 10, in which, in response to a subset of network slice information differing for a common PLMN, the second message includes a TAI slice support list indicating matching network slice information for the common PLMN.

### Claim 16 (depends on 15)

The method of claim 15, in which the second message includes an extended TAI slice support list to supplement the TAI slice support list.

### Claim 17 (depends on 10)

The method of claim 10, in which the first message is the F1 setup request and the second message is the F1 setup response.

### Claim 18 (depends on 10)

The method of claim 10, in which the first message is the gNB-DU configuration update and the second message is the gNB-DU configuration update acknowledge.
