# US 2022/0022025 A1 · Local Traffic Offload Function with Overloaded S5 and SGI Interface

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

- Number: US 2022/0022025 A1
- Document ID: US20220022025A1
- Status: Published application
- Kind: A1
- Application number: 16/929,029
- Filed: 2020-07-14
- Published: 2022-01-20
- Earliest claimed: 2020-07-14
- Assignees: Celona, Inc.
- Applicants: Celona, Inc.
- Inventors: Srinivasan Balasubramanian
- Web page: https://patentgrep.com/patent/US20220022025A1

## CPC

- H04W 8/082: {for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents}
- H04W 8/26: Network addressing or numbering for mobility support
- H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W 68/12: Inter-network notification
- H04W 76/27: Transitions between radio resource control [RRC] states
- H04W 84/045: {using private Base Stations, e.g. femto Base Stations, home Node B}
- H04W 84/105: {PBS [Private Base Station] network (H04W84/12 - H04W84/16 take precedence)}
- H04W 88/06: adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals
- H04W 88/16: Gateway arrangements
- H04W 92/02: Inter-networking arrangements
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A system and method is disclosed for allowing a Third-Party (TP) User Equipment (UE) to use a base station/access point (BS/AP), such as a 4G eNodeB (eNB) or a 5G gNodeB (gNB) of a private network, such as an enterprise network to access components of a network core, such as an Evolved Packet Core (EPC) in the TP network while also having access to features provided by or through components of an EPC within the private network.

## Claims

### Claim 1

A private network Local Traffic Off-load (LTO) system comprising:
a) a BS/AP within a private network, configured to wirelessly receive communications from, and wirelessly send communications to, a User Equipment (UE);
b) a gateway coupled to the BS/AP and configured to:
i. detect a request by a user equipment (UE) for service from a non-private network; and
ii. route the request for service from the BS/AP to the non-private network to allow the UE to register with the non-private network;
c) an LTO module coupled to the gateway, the LTO module configured to;
i. receive packets from the gateway that were communicated to the gateway by the UE;
ii. identify and maintain within the LTO module, an internet protocol (IP) address of the UE assigned by the non-private network;
iii. recognize a Domain Name System (DNS) query originating from the UE is a request for access to services associated with the private network;
iv. route the DNS query to the private network;
v. receive from the private network a responsive IP address;
vi. respond to the UE DNS request by providing the responsive IP address to the UE through the BS/AP; and
vii. route to the private network, requests from the UE that: (1) have the responsive IP address; and (2) were received from the UE, as determined by the IP address of the UE assigned by the non-private network.

### Claim 2 (depends on 1)

The system of claim 1, wherein the LTO module is further configured to;
a) detect communications that: (1) originate from resources within the private network; and (2) are intended for the UE; and
b) route the detected communication to the BS/AP for transmission to the UE.

### Claim 3 (depends on 1)

The system of claim 1, wherein the BS/AP is an eNodeB (eNB).

### Claim 4 (depends on 1)

The system of claim 1, wherein the MOCN gateway is within the BS/AP.

### Claim 5 (depends on 1)

The system of claim 1, wherein the private network is an enterprise network.

### Claim 6 (depends on 5)

The system of claim 5, wherein the enterprise network is a Citizens Band Radio Service (CBRS) network.

### Claim 7 (depends on 6)

The system of claim 6, wherein the BS/AP is a Citizens Band Radio Service Device (CBSD).

### Claim 8

A private network Local Traffic Off-load (LTO) system comprising:
a) a BS/AP within a private network, configured to wirelessly receive communications from and wirelessly send communications to a User Equipment (UE);
b) an LTO module coupled to the BS/AP, the LTO module configured to;
i. receive packets from the private network having a UE as the destination;
ii. determine that the UE is registered with a non-private network to which the LTO module can communicate over a communications interface;
iii. determine that the UE is in radio resource control (RRC) idle mode;
iv. send over the communications interface a message to cause the non-private network to move the UE from RRC idle mode to RRC connected mode;
v. upon the UE moving to RRC connected mode, sending the received packets to the UE.

### Claim 9 (depends on 8)

The system of claim 8, wherein the communications interface is a pseudo S5/S8 interface.

### Claim 10 (depends on 9)

The system of claim 9, wherein the pseudo S5/S8 interface is a modified S5/S8 interface having a field that instructs a receiving Evolved Packet Core (EPC) to move a UE from an RRC idle mode to an RRC connected mode.

### Claim 11

A private network Local Traffic Off-load (LTO) system comprising:
a) a BS/AP within a private network, configured to wirelessly receive communications from and wirelessly send communications to a User Equipment (UE);
b) an LTO module coupled to the BS/AP, the LTO module configured to;
i. receive packets from the private network having a UE as the destination;
ii. determine that the UE is registered with a non-private network to which the LTO module can communicate over a communications interface;
iii. determine that the UE is in radio resource control (RRC) idle mode;
iv. generate a page to a plurality of eNB s within the enterprise network;
v. receiving a response to the page;
vi. reconfigure the response from the UE to appear as a mobile originated message to the non-private network core.

### Claim 12

A private network Local Traffic Off-load (LTO) system comprising:
a) a BS/AP within a private network, configured to wirelessly receive communications from and wirelessly send communications to a User Equipment (UE);
b) a Local Gateway (LGW) coupled to the BS/AP and configured to:
i. receive a request from the UE to gain access to a non-private network to which the LGW is coupled over an interface;
ii. in response to the received request:
1. route the received request to a private network Evolved Packet Core (EPC) to assign a first UE IP address to the requesting UE, the first IE IP address from within the private network domain;
2. route the received request to a non-private network EPC to assign to the requesting UE a second UE IP address, the second UE IP address from within the non-private network domain;
iii. receive the first UE IP address;
iv. receive the second IP UE address;
v. associate the first UE IP address with the second UE IP address;
vi. receive communications from the non-private network EPC directed to a UE at the second UE IP address;
vii. translating the second UE IP address within the received communication to the first UE IP address; and
viii. transmitting the received communication with the translated UE IP address to the UE.

### Claim 13 (depends on 12)

The system of claim 12, wherein the LGW is further configured to provide the first IP UE address to the non-private network EPC for use in registering the UE to the non-private network.

### Claim 14 (depends on 13)

The system of claim 13, wherein the first and second UE IP addresses are communicated to the LGW through the non-private network core.

### Claim 15 (depends on 12)

The system of claim 12, further comprising a private network core configured to provide the first IP UE address to the non-private network EPC over a communication interface between the private network core and a non-private network core for use in registering the UE to the non-private network.

### Claim 16 (depends on 12)

The system of claim 12, wherein the LGW is further configured to:
a) receive communications from the non-private network EPC, the received communications having the second IP UE address and being intended for the UE;
b) translate the second IP UE address to the first IP UE address; and
c) provide the communication with the translated first IP UE address to the BS/AP for transmission to the UE.

### Claim 17 (depends on 16)

The system of claim 16, wherein the LGW is further configured to:
a) receive communications from the private network, the received communications having the first UE IP address and intended for the UE; and
b) providing the received communications with the first UE IP address to the BS/AP for transmission to the UE.

### Claim 18 (depends on 12)

The system of claim 12, wherein:
a) the BS/AP is further configured to receive a communication from the UE, the communication having the first UE IP address and a Dynamic Network Service (DNS) query for a service within the non-private network; and
b) the LGW is further configured to receive the DNS query, translate the first UE UP address to the second UE IP address and provide the communication having the DNS query and the second UE IP address to the non-private network.

### Claim 19 (depends on 18)

The system of claim 18, wherein the LGW is further configured to:
a) receive a response to the DNS query, the response having a responsive IP address for use in accessing resources within the non-private network and having the second UE IP address;
b) translate the second UE IP address into the first UE IP address; and
c) send the DNS query response to the BS/AP for transmission to the EU.

### Claim 20 (depends on 12)

The system of claim 12, wherein:
a) the BS/AP is further configured to receive a communication from the UE, the communication having the first UE IP address and a DNS query for a service within the private network; and
b) the LGW is further configured to receive the DNS query and provide the communication having the DNS query and the first UE IP address to the private network.

### Claim 21 (depends on 20)

The system of claim 20, wherein the LGW is further configured to:
a) receive a response to the DNS query, the response having a responsive IP address for accessing resources within the private network and having the first UE IP address; and
b) send the DNS query response to the BS/AP for transmission to the EU.
