Local Traffic Offload Function with Overloaded S5 and SGI Interface
AssigneeCelona, Inc.
InventorSrinivasan Balasubramanian
Life of this patent
Estimating the term…
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.
Claims21
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.
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.
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.
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.
Dependencies are inferred from the claim text.