# US 2026/0313470 A1 · Network exposure function for a service oriented network

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

- Number: US 2026/0313470 A1
- Document ID: US20260313470A1
- Status: Published application
- Kind: A1
- Application number: 19/715,974
- Filed: 2026-06-22
- Published: 2026-10-08
- Earliest claimed: 2023-07-11
- Applicants: Boost SubscriberCo L.L.C.
- Inventors: Mehdi ALASTI; Kazi BASHIR; Siddhartha CHENUMOLU
- Web page: https://patentgrep.com/patent/US20260313470A1

## CPC

- H04W 28/20: Negotiating bandwidth
- H04W 28/0867: {among entities in the downlink}
- H04W 12/06: Authentication
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A cellular network system includes a multi-core network having core slices, at least one cell site, and a network exposure layer. The cell sites are configured to receive communications from a plurality of tenants. The network exposure layer is configured to receive, through the cell site(s), a plurality of requests for bandwidth from an application programming interface (API) of the plurality of tenants. One of the requests includes a first request from a first API of a first tenant. In response to the first tenant being determined to be authenticated using information from the first request, a first core slice is determined to be associated with the first tenant. Data transfers are then provided between the first tenant and the first core slice in response to determining that the first core slice is associated with the first tenant and the first tenant being authenticated.

## Claims

### Claim 1

A cellular network system comprising:
a multi-core network comprising a plurality of core slices; and
a memory device storing a set of instructions that when executed by one or more processors, causes the one or more processors to:
receive, through a network exposure layer, a plurality of requests for bandwidth from an application programming interface (API) of the plurality of tenants comprising a first request from a first API of a first tenant; and
provide data transfers between the first tenant and the first core slice, wherein the network exposure layer comprises a network exposure function (NEF) configured to: communicate between the first API and the multi-core network in response to the first API being authenticated by a common API framework (CAPIF).

### Claim 2 (depends on 1)

The system of claim 1, wherein the network exposure layer is further configured to determine policy rules for the first tenant, enable the data transfer between first tenant and the first core slice only in accordance with the policy rules associated with the first tenant.

### Claim 3 (depends on 2)

The system of claim 2, wherein the network exposure layer is further configured to not enable data transfer between first tenant and core slices other than the first core slice.

### Claim 4 (depends on 1)

The system of claim 1, wherein the network exposure layer is further configured to:
receive a second request from a second API of a second tenant; and
determine whether the second tenant is authenticated.

### Claim 5 (depends on 4)

The system of claim 4, wherein the network exposure layer is further configured to determine a second core slice from the plurality of core slices that is associated with the second tenant, wherein the second core slice is separate from the first core slice.

### Claim 6 (depends on 5)

The system of claim 5, wherein the network exposure layer is further configured to provide data transfers between the second tenant and the second core in response to determining that the second core slice is associated with the second tenant and the second tenant being authenticated.

### Claim 7 (depends on 1)

The system of claim 1, further comprising an API gateway that is configured to receive and translate the plurality of requests into a format usable by the CAPIF or NEF.

### Claim 8

A system for cellular communications for use with a multi-core network having a plurality of core slices, the system comprising:
one or more processors;
a memory device storing a set of instructions that when executed by the one or more processors, causes the one or more processors to:
receive, at a network exposure layer, a plurality of requests for access to the multi-core network through application programming interfaces (APIs) of respective plurality of tenants, the plurality of requests comprising a first request from a first API of a first tenant;
provide data transfers between the first tenant and the first core slice, wherein the network exposure layer comprises a network exposure function (NEF) configured to: communicate between the first API and the multi-core network in response to the first API being authenticated by a common API framework (CAPIF).

### Claim 9 (depends on 8)

The system of claim 8, wherein the network exposure layer is further configured to determine policy rules for the first tenant, enable the data transfer between first tenant and the first core slice only in accordance with the policy rules associated with the first tenant.

### Claim 10 (depends on 9)

The system of claim 9, wherein the network exposure layer is further configured to not enable data transfer between first tenant and core slices other than the first core slice.

### Claim 11 (depends on 8)

The system of claim 8, wherein the network exposure layer is further configured to:
receive a second request from a second API of a second tenant; and
determine whether the second tenant is authenticated.

### Claim 12 (depends on 11)

The system of claim 11, wherein the network exposure layer is further configured to determine a second core slice from the plurality of core slices that is associated with the second tenant, wherein the second core slice is separate from the first core slice.

### Claim 13 (depends on 12)

The system of claim 12, wherein the network exposure layer is further configured to: provide data transfers between the second tenant and the second core in response to determining that the second core slice is associated with the second tenant and the second tenant being authenticated.

### Claim 14 (depends on 1)

The system of claim 1, further comprising an API gateway that is configured to receive and translate the plurality of requests into a format usable by the CAPIF or NEF.

### Claim 15

A method for cellular communications between tenants and a multi-core system, the method comprising:
receiving, at a network exposure layer, a plurality of requests for bandwidth from an application programming interface (API) of the tenants, the plurality of requests comprising a first request from a first API of a first tenant;
determining whether the first tenant is authenticated using information from the first request;
in response to the first tenant being determined to be authenticated, determining a first core slice that is associated with the first tenant, the first core slice being one of a plurality of core slices in the multi-core network; and
providing data transfers between the first tenant and the first core slice, wherein the network exposure layer comprises a network exposure function (NEF) configured to: communicate between the first API and the multi-core network in response to the first API being authenticated by a common API framework (CAPIF).

### Claim 16 (depends on 15)

The method of claim 15, further comprising:
determining policy rules for the first tenant, and
enabling the data transfer between first tenant and the first core slice only in accordance with the policy rules associated with the first tenant.

### Claim 17 (depends on 16)

The method of claim 16, further comprising: not enabling data transfer between first tenant and core slices other than the first core slice.

### Claim 18 (depends on 15)

The method of claim 15, further comprising:
receiving a second request from a second API of a second tenant; and
determining whether the second tenant is authenticated.

### Claim 19 (depends on 18)

The method of claim 18, further comprising determining a second core slice from the plurality of core slices that is associated with the second tenant, wherein the second core slice is separate from the first core slice.

### Claim 20 (depends on 19)

The system of claim 19, further comprising providing data transfers between the second tenant and the second core in response to determining that the second core slice is associated with the second tenant and the second tenant being authenticated.
