Method and system for multi-core load scheduling in an operating system (OS) less communication network

A method for multi-core load scheduling in an operating system (OS) less communication network, comprising:

• initializing a plurality of threads, and executing on a multi-core processing unit including a plurality of cores, for processing one or more user requests from a plurality of user equipment (UEs);
• synchronizing the plurality of initialized threads with each other for simultaneous processing of one or more incoming packets;
• executing a reinforcement learning (RL) agent in at least one core of the multi-core processing unit, and determining, by the RL agent, a central processing unit (CPU) load on each of the plurality of cores, and an occupancy level of a plurality of buffers of the plurality of cores for processing the one or more incoming packets by dynamically distributing the one or more incoming packets to the plurality of buffers or the plurality of threads;
• enabling or disabling, by the RI agent, a first flag corresponding to each of the plurality of threads for corresponding functionalities based on the determined CPU load on each of the plurality of cores;
• enabling or disabling, by the RL agent, a second flag for distribution of the one or more incoming packets across the plurality of buffers based on the determined occupancy level of the plurality of buffers;
• determining at least one thread among the plurality of threads based on the corresponding enabled first flag;
• determining at least one buffer among the plurality of buffers based on the enabled second flag;
• and
• processing the one or more incoming packets based on each of the at least one determined thread and the at least one determined buffer,
• wherein each of the one or more user requests includes a request for processing of the one or more incoming packets, and wherein the plurality of threads are configured to run on the plurality of cores for processing the corresponding functionalities associated with the one or more incoming packets, and
• wherein each functionality associated with each of the one or more incoming packets comprise one of a packet data convergence protocol (PDCP) stage, a radio resource control (RLC) stage, a medium access control (MAC) stage, and a functional application platform interface (FAPI) stage.

A network entity for load scheduling for functional decomposition of incoming packets in a communication network, comprising:

• an operating system (OS) less multi-core processing unit, comprising at least one processor comprising processor circuitry, configured individually and/or cooperatively, to receive one or more user requests from a plurality of user equipments (UEs), wherein the OS less multi-core processing unit is configured to:
• initialize a plurality of threads, and executing on the multi-core processing unit including a plurality of cores, for processing corresponding functionalities associated with one or more incoming packets received from the plurality of UEs;
• synchronize the plurality of initialized threads with each other for simultaneous processing of the one or more incoming packets;
• execute a reinforcement learning (RL) agent in at least one core of the multi-core processing unit, and determine, by the RL agent, a central processing unit (CPU) load on each of the plurality of cores, and an ingress data-rate of the one or more incoming packets;
• enable or disable, by the RL agent based on each of the determined CPU load and the ingress data-rate, a flag corresponding to each of the plurality of threads for processing the corresponding functionalities associated with the one or more incoming packets;
• determine at least one thread among the plurality of threads based on the corresponding enabled flag;
• and
• process the corresponding functionalities associated with the one or more incoming packets based on the at least one determined thread,
• wherein the plurality of threads are configured to run on the plurality of cores of the multi-core processing unit,
• wherein each of the plurality of cores is responsible for processing a functionality associated with the one or more incoming packets of each UE, and
• wherein the functionality associated with the one or more incoming packets of each UE comprises one of a packet data convergence protocol (PDCP) stage, a radio resource control (RLC) stage, a medium access control (MAC) stage, and a functional application platform interface (FAPI) stage.

A network entity for load scheduling for functional decomposition of incoming packets in a communication network, comprising:

• an operating system (OS) less multi-core processing unit comprising at least one processor comprising processor circuitry, configured individually and/or cooperatively to receive one or more user requests from a plurality of user equipments (UEs), wherein the OS less multi-core processing unit is configured to:
• initialize a plurality of threads, and executing on the multi-core processing unit including a plurality of cores, for processing one or more user requests from a plurality of UEs;
• synchronize the plurality of initialized threads with each other for simultaneous processing of the one or more incoming packets;
• execute a reinforcement learning (RL) agent in at least one core of the multi-core processing unit, and determine, by the RL agent, a central processing unit (CPU) load on each of the plurality of cores, and an occupancy level of a plurality of buffers of the plurality of cores for processing the one or more incoming packets by dynamically distributing the one or more incoming packets to the plurality of buffers or the plurality of threads;
• enable or disable, by the RL agent, a first flag corresponding to each of the plurality of threads for corresponding functionalities based on the determined CPU load on each of the cores;
• enable or disable, by the RL agent, a second flag for distribution of the one or more incoming packets across the plurality of buffers based on the determined occupancy level of the plurality of buffers;
• determine at least one thread among the plurality of threads based on the corresponding enabled first flags;
• determine at least one buffer among the plurality of buffers based on the enabled second flag;
• and
• process the one or more incoming packets based on each of the at least one determined thread and the at least one determined buffer,
• wherein each of the one or more user requests includes a request for processing of the one or more incoming packets, and wherein the plurality of threads are configured to run on the plurality of cores for processing the corresponding functionalities associated with the one or more incoming packets, and
• wherein each functionality associated with each of the one or more incoming packets comprise one of a packet data convergence protocol (PDCP) stage, a radio resource control (RLC) stage, a medium access control (MAC) stage, and a functional application platform interface (FAPI) stage.