# US 10,122,547 B2 · Enabling high-bandwidth, responsive mobile applications in LTE networks > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,122,547 B2 - Document ID: US10122547B2 - Status: Granted - Kind: B2 - Application number: 15/237,485 - Filed: 2016-08-15 - Published: 2017-02-16 - Granted: 2018-11-06 - Earliest claimed: 2015-08-14 - Assignees: NEC Corporation - Applicants: NEC Laboratories America, Inc. - Inventors: Rajesh Mahindra; Karthikeyan Sundaresan; Junguk Cho; Sampath Rangarajan - Web page: https://patentgrep.com/patent/US10122547B2 ## CPC - H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling} - H04L 12/1407: {Policy-and-charging control [PCC] architecture} - H04L 12/407: with decentralised control - H04L 12/66: Arrangements for connecting between networks having differing types of switching systems, e.g. gateways - H04L 47/2441: relying on flow classification, e.g. using integrated services [IntServ] - H04M 15/66: {Policy and charging system} - H04M 15/8033: {location-dependent, e.g. business or home} - H04W 4/00: Services specially adapted for wireless communication networks; Facilities therefor - H04W 4/24: Accounting or billing - H04W 76/00: Connection management - H04W 76/22: Manipulation of transport tunnels - H04L 67/1036: Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers - H04W 76/12: Setup of transport tunnels - H04W 76/15: Setup of multiple wireless link connections - H04W 88/16: Gateway arrangements - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Systems and methods for standards compatible Mobile Edge Computing (MEC), including splitting Serving gateways (SGWs) and Packet Data Network gateways (PDN-GWs) to provision sufficient resources to deploy data-plane entity instances locally at a Radio Access Network (RAN) edge with one or more cloudlets. One or more local controller nodes is deployed in one or more operator clouds, a dedicated bearer is leveraged to route traffic from the one or more cloudlets through the split SGWs and PDN-GWs, and the dedicated bearer is configured with a traffic flow template (TFT) including an Internet Protocol (IP) address of the one or more cloudlets. Efficient access to one or more MEC applications at the RAN edge is provided to one or more user devices using the dedicated bearer. ## Claims ### Claim 1 A computer implemented method for standards compatible Mobile Edge Computing (MEC), comprising: splitting Serving gateways (SGWs) and Packet Data Network gateways (PDN-GWs) to provision sufficient resources to deploy data-plane entity instances locally at a Radio Access Network (RAN) edge with one or more cloudlets; deploying one or more local controller nodes in one or more operator clouds; leveraging a dedicated bearer to route traffic, using one or more of the local controller nodes, from the one or more cloudlets through the split SGs and PDNs; configuring the dedicated bearer with a traffic flow template (TFT) including an Internet Protocol (IP) address of the one or more cloudlets; and providing one or more user devices efficient access to one or more MEC applications at the RAN edge using the dedicated bearer. ### Claim 2 (depends on 1) The method of claim 1, wherein the configuring the dedicated bearer further comprises initiating application level signaling by the one or more user devices upon receiving a request from the one or more MEC applications. ### Claim 3 (depends on 1) The method of claim 1, wherein the configuring the dedicated bearer further comprises composing a policy control and charging (PCC) rule that includes a service identifier, Quality of Service (QoS) requirements, and TFT information specified by one or more registration servers. ### Claim 4 (depends on 1) The method of claim 1, further comprising initiating a creation of a new dedicated bearer using one or more controllers by sending a message to a Mobility Management Entity (MME) with eNodeB-SGW bearer information including an IP address of a selected local SGW. ### Claim 5 (depends on 4) The method of claim 4, wherein the bearer information includes a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel identifier of the selected local SGW. ### Claim 6 (depends on 1) The method of claim 1, further comprising reducing network delay and computational delay for Augmented Reality (AR) applications using a device-to-device proximity discovery framework. ### Claim 7 (depends on 6) The method of claim 6, wherein network routing is configured only for users subscribed to a particular AR service on the device-to-device proximity discovery framework. ### Claim 8 A system for standards compatible Mobile Edge Computing (MEC), comprising: a splitter for splitting Serving gateways (SGWs) and Packet Data Network gateways (PDN-GWs) to provision sufficient resources to deploy data-plane entity instances locally at a Radio Access Network (RAN) edge with one or more cloudlets; and a processor coupled to a computer-readable storage medium, the processor being configured to: deploy one or more local controller nodes in one or more operator clouds; leverage a dedicated bearer to route traffic, using one or more of the local controller nodes, from the one or more cloudlets through the split SGs and PDNs; configure the dedicated bearer with a traffic flow template (TFT) including an Internet Protocol (IP) address of the one or more cloudlets; and provide one or more user devices efficient access to one or more MEC applications at the RAN edge using the dedicated bearer. ### Claim 9 (depends on 8) The system of claim 8, wherein configuration of the dedicated bearer further comprises initiating application level signaling by the one or more user devices upon receiving a request from the one or more MEC applications. ### Claim 10 (depends on 8) The system of claim 8, wherein configuration of the dedicated bearer further comprises composing a policy control and charging (PCC) rule that includes a service identifier, Quality of Service (QoS) requirements, and TFT information specified by one or more registration servers. ### Claim 11 (depends on 8) The system of claim 8, further comprising one or more controllers configured to initiate creation of a new dedicated bearer by sending a message to a Mobility Management Entity (MME) with eNodeB-SGW bearer information including an IP address of a selected local SGW. ### Claim 12 (depends on 11) The system of claim 11, wherein the bearer information includes a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel identifier of the selected local SGW. ### Claim 13 (depends on 8) The system of claim 8, further comprising a device-to-device proximity discovery framework to reduce network delay and computational delay for Augmented Reality (AR) applications. ### Claim 14 (depends on 13) The system of claim 13, wherein network routing is configured only for users subscribed to a particular AR service on the device-to-device proximity discovery framework. ### Claim 15 A non-transitory computer-readable storage medium including a computer-readable program for standards compatible Mobile Edge Computing (MEC), wherein the computer-readable program when executed on a computer causes the computer to perform the steps of: splitting Serving gateways (SGWs) and Packet Data Network gateways (PDN-GWs) to provision sufficient resources to deploy data-plane entity instances locally at a Radio Access Network (RAN) edge with one or more cloudlets; deploying one or more local controller nodes in one or more operator clouds; leveraging a dedicated bearer to route traffic, using one or more of the local controller nodes, from the one or more cloudlets through the split SGs and PDNs; configuring the dedicated bearer with a traffic flow template (TFT) including an Internet Protocol (IP) address of the one or more cloudlets; and providing one or more user devices efficient access to one or more MEC applications at the RAN edge using the dedicated bearer. ### Claim 16 (depends on 15) The non-transitory computer-readable storage medium of claim 15, wherein the configuring the dedicated bearer further comprises initiating application level signaling by the one or more user devices upon receiving a request from the one or more MEC applications. ### Claim 17 (depends on 15) The non-transitory computer-readable storage medium of claim 15, wherein the configuring the dedicated bearer further comprises composing a policy control and charging (PCC) rule that includes a service identifier, Quality of Service (QoS) requirements, and TFT information specified by one or more registration servers. ### Claim 18 (depends on 15) The non-transitory computer-readable storage medium of claim 15, further comprising initiating a creation of a new dedicated bearer using one or more controllers by sending a message to a Mobility Management Entity (MME) with eNodeB-SGW bearer information including an IP address of a selected local SGW. ### Claim 19 (depends on 18) The non-transitory computer-readable storage medium of claim 18, wherein the bearer information includes a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel identifier of the selected local SGW. ### Claim 20 (depends on 15) The non-transitory computer-readable storage medium of claim 15, further comprising reducing network delay and computational delay for Augmented Reality (AR) applications using a device-to-device proximity discovery framework, wherein network routing is configured only for users subscribed to a particular AR service on the device-to-device proximity discovery framework.