System and method for supporting low latency applications in a cloud radio access network
There is provided a system that includes a local cloud radio access network (RAN), and a remote cloud RAN. The local cloud RAN processes latency-sensitive applications, and the remote cloud RAN processes latency-tolerant applications. User traffic is appropriately routed to the correct cloud RAN based on the application. User equipment (UE) has no knowledge of which network is being used for processing, i.e., this network processing split is done in a manner that is transparent to the UE, e.g., by dynamically selecting a different access point name for local vs. remote processing. The processing split of the RAN between the local cloud RAN and the remote cloud RAN is done in a dynamic manner depending on the number of devices requiring low latency support. This allows the local cloud RAN to be very compact and low-cost since it does not have to process the latency-tolerant traffic.
1. A system for cloud radio access network (RAN) deployment, wherein said system comprises:
a local cloud RAN that processes latency-sensitive applications, wherein said local cloud RAN includes a local scheduler and implements a first waveform numerology optimized for said latency-sensitive applications;
a remote cloud RAN that processes latency-tolerant applications, wherein said remote cloud RAN includes a remote scheduler and implements a second waveform numerology optimized for said latency-tolerant applications;
a switch that distributes data for said latency-sensitive applications for processing in said local cloud RAN, and distributes data for said latency-tolerant applications for processing in said remote cloud RAN;
a controller that controls said switch and coordinates time-frequency resources between said local cloud RAN and said remote cloud RAN;
a first fronthaul interface through which radio units connect to said local cloud RAN; and
a second fronthaul interface through which said local scheduler and said remote scheduler communicate with one another to share said time-frequency resources.
2. The system of claim 1 ,
wherein said remote scheduler informs said local scheduler of available time/frequency resources for scheduling latency-sensitive user equipment, and
wherein said local scheduler schedules said latency-sensitive user equipment based on said available time/frequency resources.
3. The system of claim 1 ,
wherein said local cloud RAN informs said remote cloud RAN of currently available resources that said local cloud RAN has for supporting latency critical applications, and
wherein said remote cloud RAN adjusts a resource allocation split between said local cloud RAN and said remote cloud RAN.
4. The system of claim 3 ,
wherein said resource allocation split is changed based on resources being used by said local cloud RAN exceeding or falling below a threshold.
5. The system of claim 1 , further comprising:
a remote radio unit that performs cell level processing while user level processing is performed at either said local cloud RAN or said remote cloud RAN.
6. The system of claim 1 , further comprising:
a remote radio unit at which is implemented a physical layer of a protocol stack,
wherein said local cloud RAN and said remote cloud RAN process medium access control and upper layers of said protocol stack.
7. The system of claim 1 ,
wherein said system dynamically routes traffic from user equipment, between said local cloud RAN and said remote cloud RAN, based on an access point name change.
8. A method for cloud radio access network (RAN) deployment, wherein said method comprises:
processing latency-sensitive applications in a local cloud RAN, wherein said local cloud RAN includes a local scheduler and implements a first waveform numerology optimized for said latency-sensitive applications;
processing latency-tolerant applications in a remote cloud RAN, wherein said remote cloud RAN includes a remote scheduler and implements a second waveform numerology optimized for said latency-tolerant applications,
utilizing a switch that distributes data for said latency-sensitive applications for processing in said local cloud RAN, and distributes data for said latency-tolerant applications for processing in said remote cloud RAN;
utilizing a controller that controls said switch and coordinates time-frequency resources between said local cloud RAN and said remote cloud RAN;
utilizing a first fronthaul interface through which radio units connect to said local cloud RAN; and
utilizing a second fronthaul interface through which said local scheduler and said remote scheduler communicate with one another to share said time-frequency resources.
9. The method of claim 8 ,
wherein said method further comprises:
said remote scheduler informing said local scheduler of available time/frequency resources for scheduling latency-sensitive user equipment; and
said local scheduler scheduling said latency-sensitive user equipment based on said available time/frequency resources.
10. The method of claim 8 , further comprising:
said local cloud RAN informing said remote cloud RAN of currently available resources that said local cloud RAN has for supporting latency critical applications; and
said remote cloud RAN adjusting a resource allocation split between said local cloud RAN and said remote cloud RAN.
11. The method of claim 10 , further comprising:
changing said resource allocation split based on resources being used by said local cloud RAN exceeding or falling below a threshold.
12. The method of claim 8 , further comprising:
performing cell level processing in a remote radio unit while performing user level processing at either said local cloud RAN or said remote cloud RAN.
13. The method of claim 8 , further comprising:
implementing a physical layer of a protocol stack at a remote radio unit; and
processing medium access control and upper layers of said protocol stack at said local cloud RAN and said remote cloud RAN.
14. The method of claim 8 , further comprising:
dynamically routing traffic from user equipment, between said local cloud RAN and said remote cloud RAN, based on an access point name change.