Abstract: In one embodiment, a method is disclosed, comprising: receiving a packet; processing the packet in a Control Unit–User Plane (CU-UP) as a user-space application with kernel-bypass networking; performing packet Input/Output (I/O) by the CU-UP user-space application, wherein the CU-UP performs Internet Protocol (IP) validation on received user-plane packets before processing Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP) and General Packet Radio Service Tunnelling Protocol (GTPU) protocol stack and performing direct I/O to a Network Interface Controller (NIC) for sending the packet over a network to a Distributed Unit (DU). The method may further comprise using a containerized CU-UP. The method may further comprise using a plurality of worker threads. The method may further comprise using a polling user space networking accelerator framework.

Abstract: A method of providing CU-CP high availability is disclosed, comprising: configuring a single CU-CP instance across a first node and a second node, The single CU-CP instance appears as a single node having multiple IPs to all its peer nodes; keeping session information of the single CU-CP instance at the first node and at the second node; and wherein if the first node fails, the second node may be configured to take up calls from the first node.

Abstract: A system is disclosed for providing Open RAN CU-UP high availability, the system comprising: at least one active CU-CP; at least one active CU-UP in communication with the at least one active CU-CP; and at least one standby CU-UP in communication with the at least one active CU-CP; wherein when a message may be received from a CU-CP that detects a failure of the at least one active CU-UP, the at least one standby CU-UP may be configured to take over and become an active CU-UP, thereby providing failover redundancy for the at least one active CU-UP.

Abstract: A method is disclosed for providing a telecom microservice rolling upgrade, the method comprising: providing, by a Service Management and Orchestration (SMO), a new instance of F1 demux in a same cluster and namespace; advertising the new instance of the F1 demux to all PODs and micro services; informing, by the SMO, an old F1 demux to start a version upgrade to a new instance; sending, by the old F1 demux, a trigger to start a reconcile procedure to a new F1 demux; advertising that the old instance of the F1 demux is not available to take up new calls from internal PODs and micro-service, and is accepting traffic via the new F1 demux only; routing, by the old F1 demux, all incoming F1 traffic from a Distributed Unit (DU) to the new F1 demux; and instructing the DU, by the old F1 demux, to add a Transport Network Layer (TNL) association of the new F1 demux.

Abstract: Systems and methods are provided for telecom cloud scale down. In one embodiment, a method is provided comprising: deploying a coordinating node, which may be a CU-CP or CU-UP, in a microservices cloud infrastructure; receiving, at an internal controller at the coordinating node, a trigger request for scale down preparation; sending, from the internal controller, a scale down request to a first stateful telecom microservice; sending, from the first stateful telecom microservice, at least one existing session state distribution request to at least one additional stateful telecom microservice; distributing existing connection and session information to the at least one additional stateful telecom microservice; and sending, from the first stateful telecom microservice to the internal controller, a scale down preparation completion message, thereby performing telecom cloud scale down while mitigating disruptions to subscriber service.

Abstract: Methods and systems are presented for providing a 4G-5G Open RAN User Plane Path. In one embodiment a method includes keeping, by a Distributed Unit (DU)/Centralized Unit (CU)-User Plane (UP), a list of local switch enabled subscribers; receiving an uplink data packet for a local switch enabled subscriber from a source device; comparing, by the DU/CU-UP, if a destination Internet Protocol (IP) address matches with any of IP addresses in the local switch enabled subscriber destination device IP addresses; and when the destination IP address matches, then switching by the DU/CU-UP the traffic and sending the data packet as a downlink traffic towards the destination device.

Abstract: In one embodiment, a method is disclosed, comprising: receiving a packet; processing the packet in a Control Unit-User Plane (CU-UP) as a user-space application with kernel-bypass networking; performing packet Input/Output (I/O) by the CU-UP user-space application, wherein the CU-UP performs Internet Protocol (IP) validation on received user-plane packets before processing Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP) and General Packet Radio Service Tunnelling Protocol (GTPU) protocol stack and performing direct I/O to a Network Interface Controller (NIC) for sending the packet over a network to a Distributed Unit (DU). The method may further comprise using a containerized CU-UP. The method may further comprise using a plurality of worker threads. The method may further comprise using a polling user space networking accelerator framework.

Abstract: A system is disclosed for providing Open RAN CU-UP high availability, the system comprising: at least one active CU-CP; at least one active CU-UP in communication with the at least one active CU-CP; and at least one standby CU-UP in communication with the at least one active CU-CP; wherein when a message may be received from a CU-CP that detects a failure of the at least one active CU-UP, the at least one standby CU-UP may be configured to take over and become an active CU-UP, thereby providing failover redundancy for the at least one active CU-UP.

Abstract: A method is disclosed for providing a telecom microservice rolling upgrade, the method comprising: providing, by a Service Management and Orchestration (SMO), a new instance of F1 demux in a same cluster and namespace; advertising the new instance of the F1 demux to all PODs and micro services; informing, by the SMO, an old F1 demux to start a version upgrade to a new instance; sending, by the old F1 demux, a trigger to start a reconcile procedure to a new F1 demux; advertising that the old instance of the F1 demux is not available to take up new calls from internal PODs and micro-service, and is accepting traffic via the new F1 demux only; routing, by the old F1 demux, all incoming F1 traffic from a Distributed Unit (DU) to the new F1 demux; and instructing the DU, by the old F1 demux, to add a Transport Network Layer (TNL) association of the new F1 demux.

Abstract: A method is disclosed for providing singleton micro-service high availability, comprising: identifying, by an internal controller, that a pod/container has crashed; initiating, by the internal controller, a label change for an existing similar pod labeled as standby to active; matching a singleton micro-service selector label criterion; advertising the newly re-labeled existing similar pod as part of a singleton micro-service; and receiving, by the newly relabeled pod in the system, traffic directed on an IP address of the singleton micro-service.

Abstract: A wireless network system is described. In some scenarios MME/MSC/SGSN may act as a client which has huge amount of real-time data to be delivered towards server. For this speedy and reliable delivery requirement, a approach has been proposed which will use multiple parallel HTTP connections for delivery and also make sure that the events related to a particular node is delivered in right order. The multiple HTTP connections are used for parallel delivery so that in case one connections fails then it may not impact other existing connections. The number of connections may grow dynamically up to the configured limit depending on the data delivery requirements and then it may dynamically shrink once the load is reduced. A key based approach is proposed where each connected node will be assigned a unique key which will be used for sequencing the messages related to events of this particular node.

Abstract: Systems and methods are provided for telecom cloud scale down. In one embodiment, a method is provided comprising: deploying a coordinating node, which may be a CU-CP or CU-UP, in a microservices cloud infrastructure; receiving, at an internal controller at the coordinating node, a trigger request for scale down preparation; sending, from the internal controller, a scale down request to a first stateful telecom microservice; sending, from the first stateful telecom microservice, at least one existing session state distribution request to at least one additional stateful telecom microservice; distributing existing connection and session information to the at least one additional stateful telecom microservice; and sending, from the first stateful telecom microservice to the internal controller, a scale down preparation completion message, thereby performing telecom cloud scale down while mitigating disruptions to subscriber service.

Abstract: A method is disclosed for providing singleton micro-service high availability, comprising: identifying, by an internal controller, that a pod/container has crashed; initiating, by the internal controller, a label change for an existing similar pod labeled as standby to active; matching a singleton micro-service selector label criterion; advertising the newly re-labeled existing similar pod as part of a singleton micro-service; and receiving, by the newly relabeled pod in the system, traffic directed on an IP address of the singleton micro-service.

Abstract: In a first embodiment, a method is disclosed of providing Stream Control Transmission Protocol (SCTP) high availability in a cloud, the method comprising: keeping track, by an internal controller of an internal service discover framework, internal changes in a cluster; determining, by the internal controller, if any SCTP pods crash; informing, by the internal controller, remaining SCTP pods about changes in the environment; determining, by the controller, to distribute a number of connections in each remaining SCTP pod; and initiating, by the remaining pods, SCTP connection reestablishment.

Abstract: A wireless network system is described. In some scenarios MME/MSC/SGSN may act as a client which has huge amount of real-time data to be delivered towards server. For this speedy and reliable delivery requirement, a approach has been proposed which will use multiple parallel HTTP connections for delivery and also make sure that the events related to a particular node is delivered in right order. The multiple HTTP connections are used for parallel delivery so that in case one connections fails then it may not impact other existing connections. The number of connections may grow dynamically up to the configured limit depending on the data delivery requirements and then it may dynamically shrink once the load is reduced. A key based approach is proposed where each connected node will be assigned a unique key which will be used for sequencing the messages related to events of this particular node.

Abstract: A method is disclosed, comprising: determining, at an application pod, Responsibility of allocation/deallocation of individual protocol identifier; receiving, at a centralized identifier Range allocator, a request from the application pod, the request including an address of the application pod; assigning, at the centralized identifier range allocator, a new range in response to the received request; sending, from the centralized identifier range allocator to a database, and responding, from the centralized identifier range allocator to the application pod, the new identifier range.

Abstract: The presently described invention provides gNB-CU-UP data plane high availability in a public or private cloud. In one embodiment, a method of providing gNB-CU-UP data plane high availability in public/private cloud includes identifying, by an internal controller, when a data-plane Pod crashes; initiating, by the internal controller, procedures to make a passive POD to an active state; the procedures including at least one of: maintaining, by the passive POD, all flows of all active PODs in it as backup; identifying, by the passive POD, flows of the impacted data-plane POD and marking those flows to an active state; marking remaining non-active flows at the passive POD to be removed; triggering, by the internal controller, label changing of the passive data-plane POD; migrating data-plane Internet Protocol (IP) of crashed POD to the passive data-plane POD; and launching, by a Service Management and Orchestration (SMO), a new passive POD for backup.

Abstract: This disclosure provides dynamic spawning of CU-UP instances and migration of some of active subscribers from overloaded CU-UP instance to newly created CU-UP instance without service disruption. In one embodiment, a method of migrating an active subscriber from a first Centralized Unit-User Plane (CU-UP) instance to a newly provided second CU-UP instance includes determining a first CU-UP requires service; spawning the second CU-UP instance; and migrating a subscriber from the first CU-UP instance to the second CU-UP instance.

Abstract: In a first embodiment, a method is disclosed of providing Stream Control Transmission Protocol (SCTP) high availability in a cloud, the method comprising: keeping track, by an internal controller of an internal service discover framework, internal changes in a cluster; determining, by the internal controller, if any SCTP pods crash; informing, by the internal controller, remaining SCTP pods about changes in the environment; determining, by the controller, to distribute a number of connections in each remaining SCTP pod; and initiating, by the remaining pods, SCTP connection reestablishment.

Abstract: A method is disclosed for providing a telecom microservice rolling upgrade, the method comprising: providing, by a Service Management and Orchestration (SMO), a new instance of F1 demux in a same cluster and namespace; advertising the new instance of the F1 demux to all PODs and micro services; informing, by the SMO, an old F1 demux to start a version upgrade to a new instance; sending, by the old F1 demux, a trigger to start a reconcile procedure to a new F1 demux; advertising that the old instance of the F1 demux is not available to take up new calls from internal PODs and micro-service, and is accepting traffic via the new F1 demux only; routing, by the old F1 demux, all incoming F1 traffic from a Distributed Unit (DU) to the new F1 demux; and instructing the DU, by the old F1 demux, to add a Transport Network Layer (TNL) association of the new F1 demux.