Unified radio access network (RAN)/multi-access edge computing (MEC) platform

1. A method comprising:

obtaining, by a device and from a node in a core network, application identifiers associated with applications accessible by a first user device,

wherein the application identifiers are associated with latency requirements;

comparing, by the device, information regarding a first packet flow associated with the first user device and the application identifiers;

determining, by the device, that a first packet associated with the first packet flow is destined for a low-latency application having a specified latency range based on comparing the information regarding the first packet flow and the application identifiers;

identifying, by the device, a first low-latency bearer configured to satisfy the specified latency range associated with the low-latency application; and

mapping, by the device, the first packet flow to the first low-latency bearer.

2. 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, while bypassing the core network.

3. The method of claim 2 , wherein the device is provided at an edge of a radio access network (RAN).

4. The method of claim 1 , wherein a Packet Data Convergence Protocol (PDCP) agent is configured to determine that the first packet is destined for the low-latency application.

5. The method of claim 4 , wherein the PDCP agent is configured to obtain the first packet by way of a mapping table provided at a radio link control (RLC) layer.

6. The method of claim 4 , wherein the PDCP agent includes a user plane that is virtualized for co-location with the device.

7. The method of claim 1 , further comprising:

obtaining, from a second user device, a second packet,

wherein the second packet is associated with a second packet flow;

comparing information regarding the second packet flow and the application identifiers;

determining that the second packet is destined for the low-latency application having the specified latency range based on a second result of comparing the information regarding the second packet flow and the application identifiers;

identifying a second low-latency bearer configured to satisfy the specified latency range associated with the low-latency application;

mapping the second packet flow to the second low-latency bearer;

mapping the first low-latency bearer to the second low-latency bearer; and

communicating a plurality of packets between the first user device and the second user device based on a mapping between the first low-latency bearer and the second low-latency bearer.

8. A device for wireless communication, comprising:

a memory; and

one or more processors operatively coupled to the memory, the memory and the one or more processors configured to:

obtain, from a node in a core network, application identifiers associated with applications accessible by a first user device,

wherein the application identifiers are associated with latency requirements;

compare information regarding a first packet flow and the application identifiers,

wherein the first packet flow is associated with a request communication session associated with the first user device;

determine that a first packet associated with the first packet flow is destined for a low-latency application based on comparing the information regarding the first packet flow and the application identifiers;

identify a first low-latency bearer configured to satisfy a specified latency range associated with the low-latency application; and

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 the core network.

9. The device 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.

10. The device 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.

11. The device of claim 10 , wherein the PDCP agent includes a user plane that is virtualized for co-location with the device.

12. The device of claim 8 , wherein the specified latency range is less than 10 milliseconds.

13. The device of claim 8 , wherein the one or more processors are further configured to:

obtain, from a second user device, a second packet,

wherein the second packet is associated with a second packet flow;

compare information regarding the second packet flow and the application identifiers;

determine that the second packet is destined for the low-latency application having the specified latency range based on a second result of comparing the information regarding the second packet flow and the application identifiers;

identify a second low-latency bearer configured to satisfy the specified latency range associated with the low-latency application;

map the second packet flow to the second low-latency bearer;

map the first low-latency bearer to the second low-latency bearer; and

communicate a plurality of packets between the first user device and the second user device based on a mapping between the first low-latency bearer and the second low-latency bearer.

14. The device of claim 13 , wherein the first user device and the second user device are one of:

a drone,

a vehicle,

a gaming device,

a phone, and/or

a computer.

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 device, cause the one or more processors to:

obtain, from a node in a core network, application identifiers associated with applications accessible by a first user device,

wherein the application identifiers are associated with latency requirements;

obtain, from the first user device, a first packet,

wherein the first packet is included in a first packet flow, and

wherein the first packet flow is associated with a request communication session associated with the first user device;

determine that the first packet is destined for a low-latency application having a specified latency range based on comparing information associated with the first packet flow and information associated with the application identifiers;

identify a first low-latency bearer configured to satisfy the specified latency range associated with the low-latency application; and

map the first packet flow to the first low-latency bearer.

16. 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 the core network.

17. The non-transitory computer-readable medium of claim 15 , wherein a Packet Data Convergence Protocol (PDCP) agent is configured to determine that the first packet is destined for the low-latency application.

18. The non-transitory computer-readable medium of claim 17 , wherein the PDCP agent is configured to obtain the first packet by way of a mapping table provided at a radio link control (RLC) layer.

19. The non-transitory computer-readable medium of claim 15 , wherein the specified latency range is less than 10 milliseconds.

20. 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:

obtain, from a second user device, a second packet,

wherein the second packet is associated with a second packet flow;

determine that the second packet is destined for the low-latency application having the specified latency range based comparing information associated with the second packet flow and the information associated the application identifiers;

identify a second low-latency bearer configured to satisfy the specified latency range associated with the low-latency application;

map the second packet flow to the second low-latency bearer;

map the first low-latency bearer to the second low-latency bearer; and

communicate a plurality of packets between the first user device and the second user device based on a mapping between the first low-latency bearer and the second low-latency bearer.