# US 12,016,077 B2 · Unified radio access network (RAN)/multi-access edge computing (MEC) platform > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,016,077 B2 - Document ID: US12016077B2 - Status: Granted - Kind: B2 - Application number: 17/457,272 - Filed: 2021-12-02 - Published: 2022-03-24 - Granted: 2024-06-18 - Earliest claimed: 2018-08-08 - Assignees: Verizon Patent and Licensing Inc. - Applicants: Verizon Patent and Licensing Inc. - Inventors: Jignesh S. Panchal; Ratul Kumar Guha; Kalyani Bogineni; Hans Raj Nahata - Web page: https://patentgrep.com/patent/US12016077B2 ## CPC - H04W 8/082: {for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents} - H04L 43/0858: {One way delays} - H04L 45/121: by minimising delays - H04L 45/306: {Route determination based on the nature of the carried application} - H04L 47/56: implementing delay-aware scheduling - H04W 40/12: based on transmission quality or channel quality - H04W 72/543: based on requested quality, e.g. QoS - H04W 76/12: Setup of transport tunnels - H04W 8/20: Transfer of user or subscriber data - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A device can determine, based on a first packet flow associated with a first user device and application identifiers associated with applications accessible by the first user device, that a first packet associated with the first packet flow is destined for a low-latency application having a specified latency range. The device can identify a first low-latency bearer that satisfies the specified latency range associated with the low-latency application. The device can map the first packet flow to the first low-latency bearer. ## Claims ### Claim 1 A method comprising: determining, by a device, that a first packet, associated with a first packet flow, and a second packet, associated with a second packet flow, are destined for a low-latency application having a specified latency range, wherein the device is a unified radio access network (RAN) and multi-edge computing (MEC) platform and wherein the first packet flow is associated with a first user device and the second packet flow is associated with a second user device; identifying, by the device, a first low-latency bearer and a second low-latency bearer configured to satisfy the specified latency range associated with the low-latency application, wherein the first low-latency bearer is between the first user device, the device, and a base station, and wherein the second low-latency bearer is between the second user device, the device, and the base station; mapping, by the device, the first packet flow to the first low-latency bearer; and mapping, by the device, the second packet flow to the second low-latency bearer. ### Claim 2 (depends on 1) The method of claim 1, further comprising: communicating a plurality of packets between the first user device and the second user device. ### Claim 3 (depends on 2) The method of claim 2, wherein the method further comprises: mapping the first low-latency bearer to the second low-latency bearer; and wherein communicating the plurality of packets between the first user device and the second user device is based on mapping the first low-latency bearer to the second low-latency bearer. ### Claim 4 (depends on 1) The method of claim 1, wherein determining that the first packet, associated with the first packet flow, is destined for the low-latency application is based on comparing information regarding the first packet flow and application identifiers; and wherein determining that the second packet, associated with the second packet flow, is destined for the low-latency application is based on comparing information regarding the second packet flow and the application identifiers. ### Claim 5 (depends on 1) The method of claim 1, wherein the device is provided at an edge of a RAN. ### Claim 6 (depends on 1) The method of claim 1, wherein the specified latency range is less than 10 milliseconds. ### Claim 7 (depends on 1) The method of claim 1, further comprising: communicating packets, associated with the first packet flow, using the first low-latency bearer, wherein the packets are communicated between an entity hosting the low-latency application and the first user device. ### Claim 8 A unified radio access network (RAN) and multi-edge computing (MEC) platform, comprising: one or more processors configured to: determine, based on application identifiers associated with applications accessible by a first user device and a second user device, that a first packet, associated with a first packet flow, and a second packet, associated with a second packet flow, are destined for a low-latency application, wherein the first packet flow is associated with the first user device and the second packet flow is associated with the second user device; identify a first low-latency bearer and a second low-latency bearer configured to satisfy a specified latency range associated with a low-latency application, wherein the first low-latency bearer is between the first user device, the unified RAN and MEC platform, and a base station, and wherein the second low-latency bearer is between the second user device, the unified RAN and MEC platform, and the base station; communicate first packets, associated with the first packet flow, using the first low-latency bearer, wherein the first packets are communicated between an entity hosting the low-latency application and the first user device, while bypassing a core network; and communicate second packets, associated with the second packet flow, using the second low-latency bearer, wherein the second packets are communicated between the entity hosting the low-latency application and the second user device, while bypassing the core network. ### Claim 9 (depends on 8) The unified RAN and MEC platform of claim 8, wherein the one or more processors are further to: map the first packet flow to the first low-latency bearer prior to communicating the packets using the first low-latency bearer. ### Claim 10 (depends on 8) The unified RAN and MEC platform of claim 8, wherein a Packet Data Convergence Protocol (PDCP) agent is configured to determine that the first packet is destined for the low-latency application. ### Claim 11 (depends on 8) The unified RAN and MEC platform of claim 8, wherein the unified RAN and MEC platform is in a RAN. ### Claim 12 (depends on 8) The unified RAN and MEC platform of claim 8, wherein the specified latency range is less than 10 milliseconds. ### Claim 13 (depends on 8) The unified RAN and MEC platform of claim 8, wherein the one or more processors are further configured to: map the second packet flow to the second low-latency bearer; and map the first low-latency bearer to the second low-latency bearer. ### Claim 14 (depends on 8) The unified RAN and MEC platform of claim 8, wherein the first user device and the second user device are each one of: a drone, a vehicle, a gaming device, a phone, or a computer. ### Claim 15 A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: one or more instructions that, when executed by one or more processors of a unified radio access network (RAN) and multi-edge computing (MEC) platform, cause the one or more processors to: determine, based on application identifiers associated with applications accessible by a first user device and a second user device, that a first packet, associated with a first packet flow, and a second packet, associated with a second packet flow, are destined for a low-latency application having a specified latency range, wherein the first packet flow is associated with the first user device and the second packet flow is associated with the second user device; identify a first low-latency bearer and a second low-latency bearer configured to satisfy the specified latency range associated with the low-latency application, wherein the first low-latency bearer is between the first user device, the unified RAN and MEC platform, and a base station, and wherein the second low-latency bearer is between the second user device, the unified RAN and MEC platform, and the base station; map the first packet flow to the first low-latency bearer; and map the second packet flow to the second low-latency bearer. ### Claim 16 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: communicate packets, associated with the first packet flow, using the first low-latency bearer, wherein the packets are communicated between an entity hosting the low-latency application and the first user device, while bypassing a core network, wherein the entity is one of: the unified RAN and MEC platform, or a cloud computing resource associated with the unified RAN and MEC platform. ### Claim 17 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the unified RAN and MEC platform is provided at an edge of a RAN. ### Claim 18 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein the first user device is one of: a drone, a vehicle, a gaming device, a phone, or a computer. ### Claim 19 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: map the first low-latency bearer to the second low-latency bearer. ### Claim 20 (depends on 19) The non-transitory computer-readable medium of claim 19, wherein the specified latency range is less than 10 milliseconds.