公开(公告)号：US20230388234A1

公开(公告)日：2023-11-30

申请号：US17825645

申请日：2022-05-26

Applicant: Microsoft Technology Licensing, LLC

Inventor： Anuj KALIA ,  Daehyeok KIM ,  Ilias MARINOS ,  Tao JI ,  Nikita LAZAREV ,  Paramvir BAHL

IPC: H04L45/76 ,  H04W40/34

CPC classification number: H04L45/76 ,  H04W40/34 ,  H04W84/045

Abstract: Methods and systems for dynamically re-routing layer traffic between different servers with little user-visible disruption and without modifications to the vRAN software stack are provided. This approach enables operators to initiate a PHY migration either on demand (e.g., during planned maintenances) or to set up automatic migration on unexpected events (e.g., server failures). It is recognized that PHY processing in cellular networks has no hard state that must be migrated. As a result, layer traffic such as the PHY-L2 traffic or L2-PHY traffic can be simply re-routed to a different server. This re-routing mechanism is realized by interposing one or more message controllers (e.g., middlebox) in a communication channel between the PHY and L2.

公开(公告)号：US20230412502A1

公开(公告)日：2023-12-21

申请号：US17825543

申请日：2022-05-26

Applicant: Microsoft Technology Licensing, LLC

Inventor： Anuj KALIA ,  Daehyeok KIM ,  Ilias MARINOS ,  Tao JI ,  Paramvir BAHL

IPC: H04L45/00 ,  H04L45/28

CPC classification number: H04L45/66 ,  H04L45/28

Abstract: Methods and systems for dynamically re-routing layer traffic between different servers with little user-visible disruption and without modifications to the vRAN software stack are provided. For instance, transformations on messages between the L2 and PHY, such as duplication and filtering, enable the system to maintain one or more low-overhead “hot, inactive” PHY clones. A hot, inactive PHY clone may be a duplicate of an operational PHY, where the PHY clone is primed to process a PHY workload of the operational PHY (e.g., “hot”) but is not currently responsible for processing the PHY workload (e.g., low-overhead, inactive). In this way, a PHY workload may be automatically and seamlessly migrated to the hot PHY clone in response to planned downtime (e.g., scheduled maintenance, software upgrades) or unexpected events (e.g., server failures) within the strict transmission time intervals (TTIs) required for processing the PHY workload.