Unified radio access network (ran)/multi-access edge computing (mec) platform

{
  "publication_number": "US2020053546A1",
  "country": "US",
  "kind": "A1",
  "title": "Unified radio access network (ran)/multi-access edge computing (mec) platform",
  "abstract": "A device can receive, from a node in a core network, application identifiers associated with applications accessible by a first user device. The application identifiers can be associated with latency requirements. The device can obtain, from the first user device, a first packet associated with a first packet flow. The device can compare information regarding the first packet flow, and the application identifiers to determine that the first packet 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, and communicate packets, associated with the first packet flow, using the first low-latency bearer. The packets can include data packets communicated between an entity hosting the low-latency application and the first user device, while bypassing the core network.",
  "claims": [
    "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; obtaining, by the device and from the first user device, a first packet, wherein the first packet is associated with included in a first packet flow, and wherein the first packet flow is a request communication session associated with the first user device; comparing, by the device, information regarding the first packet flow and the application identifiers; determining, by the device, that the first packet is destined for a low-latency application having a specified latency range based on a first result of 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; mapping, by the device, the first packet flow to the first low-latency bearer; and communicating, by the device, 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. 2. The method of claim 1, wherein the device is in a radio access network (RAN). 3. The method of claim 1, wherein the entity hosting the low-latency application is one of: the device, or a cloud computing resource associated with the device. 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 in about 30 to 50 microseconds. 5. The method of claim 1, wherein the specified latency range is less than 10 milliseconds. 6. 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. 7. The method of claim 6, wherein the first user device and the second user device include one of: a drone, a vehicle, a gaming device, a phone, and/or a computer. 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; 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; compare information regarding the first packet flow and the application identifiers; determine that the first packet is destined for a low-latency application having a specified latency range based on a first result of comparing the information regarding the first packet flow and the application identifiers; identify a first low-latency bearer configured to satisfy the specified latency range associated with the low-latency application; map the first packet flow to the first low-latency bearer; 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 device is in a radio access network (RAN). 10. The device of claim 8, wherein the entity hosting the low-latency application is one of: the device, or a cloud computing resource associated with the device. 11. 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 in about 30 to 50 microseconds. 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 include 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; compare information regarding the first packet flow and the application identifiers; determine that the first packet is destined for a low-latency application having a specified latency range based on a first result of comparing the information regarding the first packet flow and the application identifiers; identify a first low-latency bearer configured to satisfy the specified latency range associated with the low-latency application; map the first packet flow to the first low-latency bearer; 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. 16. The non-transitory computer-readable medium of claim 15, wherein the device is in a radio access network (RAN). 17. The non-transitory computer-readable medium of claim 15, wherein the entity hosting the low-latency application is one of: the device, or a cloud computing resource associated with the device. 18. 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 in about 30 to 50 microseconds. 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; 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."
  ],
  "cpc": [
    "H04W 8/082",
    "H04L 43/0858",
    "H04L 45/121",
    "H04L 45/306",
    "H04L 47/56",
    "H04W 40/12",
    "H04W 72/087",
    "H04W 72/543",
    "H04W 76/12",
    "H04W 8/20"
  ],
  "assignees": [
    "VERIZON PATENT & LICENSING INC"
  ],
  "filing_date": "2018-08-08",
  "publication_date": "2020-02-13",
  "priority_date": "2018-08-08",
  "application_number": "US-201816058753-A",
  "family_id": "69407146",
  "citations": [
    "US2013288729A1",
    "US2017105216A1",
    "US2018248787A1",
    "US2018270743A1",
    "US2018352594A1",
    "US2018367637A1",
    "US2019028934A1",
    "US2019042318A1",
    "US2019098676A1",
    "US2019104030A1",
    "US2019254108A1"
  ]
}