Handling core network connection failure
In general, the current subject matter relates to handling core network connection failure. In some implementations, an F1 interface can be set up between a centralized unit (CU) of a base station and a distributed unit (DU) of the base station. Setting up the F1 interface can include transmitting core connectivity status information from the CU to the DU, and the core connectivity status information can indicate to the DU whether or not the CU has connectivity with a core network.
1 . A system, comprising:
at least one processor, and
at least one non-transitory storage media storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
setting up an F1 interface between a centralized unit (CU) of a base station and a distributed unit (DU) of the base station, wherein setting up the F1 interface comprises transmitting core connectivity status information from the CU to the DU, the core connectivity status information indicating to the DU whether or not the CU has a connection with a core network; and
in response to the core connectivity status information indicating that the CU does not have a connection with the core network, causing the DU, under an absence of the connection with the core network, to be in an active state such that the DU provides support to Non-Standalone (NSA) user equipments (UEs) and the DU does not provide support to Standalone (SA) UEs.
2 . The system of claim 1 , wherein, in response to the core connectivity status information indicating to the DU that the CU does not have a connection with the core network, the DU is configured to disable System Information Block Type 1 (SIB1) scheduling or disable 5G System (5GS) tracking area code (TAC) transmission in SIB1; and
in response to the core connectivity status information indicating to the DU that the CU have a connection with the core network, the DU is configured to enable SIB1 scheduling with 5GS TAC.
3 . The system of claim 1 , wherein, in response to the core connectivity status information indicating to the DU that the CU does not have a connection with the core network, the operations further comprise causing the DU to be in the active state; and
the operations further comprise, after causing the DU to be in the active state, in response to the CU gaining a connection with the core network, causing the DU to provide support to the SA UEs.
4 . The system of claim 3 , wherein transmitting core connectivity status information comprises transmitting a first GNB-CU CONFIGURATION UPDATE message from the CU to the DU, the first GNB-CU CONFIGURATION UPDATE message including the core connectivity status information as an information element (IE); and
causing the DU to provide support to the SA UEs comprises transmitting a second GNB-CU CONFIGURATION UPDATE message from the CU to the DU.
5 . The system of claim 1 , wherein transmitting core connectivity status information comprises transmitting a GNB-CU CONFIGURATION UPDATE message from the CU to the DU, the GNB-CU CONFIGURATION UPDATE message including the core connectivity status information as an information element (IE).
6 . The system of claim 5 , wherein the core connectivity status information includes a value that is set to a first value to indicate that the CU has a connection with the core network and that is set to a second, different value to indicate that the CU does not have a connection with the core network.
7 . The system of claim 6 , wherein, with the value being set to the second value, the DU is configured to disable System Information Block Type 1 (SIB1) scheduling or disable 5G System (5GS) tracking area code (TAC) transmission in S1B1; and
with the value being set to the first value, the DU is configured to enable SIB1 scheduling with 5GS TAC.
8 . The system of claim 1 , wherein the base station is a gNodeB, and the core network is a 5G core network.
9 . A computer-implemented method, comprising:
setting up an F1 interface between a centralized unit (CU) of a base station and a distributed unit (DU) of the base station, wherein setting up the F1 interface comprises transmitting core connectivity status information from the CU to the DU, the core connectivity status information indicating to the DU whether or not the CU has a connection with a core network; and
in response to the core connectivity status information indicating that the CU does not have a connection with the core network, causing the DU, under an absence of the connection with the core network, to be in an active state such that the DU provides support to Non-Standalone (NSA) user equipments (UEs) and the DU does not provide support to Standalone (SA) UEs.
10 . The method of claim 9 , wherein, in response to the core connectivity status information indicating to the DU that the CU does not have a connection with the core network, the DU disables System Information Block Type 1 (SIB1) scheduling or disables 5G System (5GS) tracking area code (TAC) transmission in SIB1 scheduling; and
in response to the core connectivity status information indicating to the DU that the CU does not have a connection with the core network, the DU enables SIB1 scheduling with 5GS TAC.
11 . The method of claim 9 , wherein, in response to the core connectivity status information indicating to the DU that the CU does not have a connection with the core network, the operations further comprise causing the DU to be in the active state; and
the method further comprises, after causing the DU to be in the active state, in response to the CU gaining a connection with the core network, causing the DU to provide support to the SA UEs.
12 . The method of claim 9 , wherein the base station is a gNodeB, and the core network is a 5G core network.
13 . At least one non-transitory storage media storing instructions that, when executed by at least one processor, cause the at least one processor to perform operations comprising:
setting up an F1 interface between a centralized unit (CU) of a base station and a distributed unit (DU) of the base station, wherein setting up the F1 interface comprises transmitting core connectivity status information from the CU to the DU, the core connectivity status information indicating to the DU whether or not the CU has a connection with a core network; and
in response to the core connectivity status information indicating that the CU does not have a connection with the core network, causing the DU, under an absence of the connection with the core network, to be in an active state such that the DU provides support to Non-Standalone (NSA) user equipments (UEs) and the DU does not provide support to Standalone (SA) UEs.
14 . The storage media of claim 13 , wherein, in response to the core connectivity status information indicating to the DU that the CU does not have a connection with the core network, the DU is configured to disable System Information Block Type 1 (SIB1) scheduling or disable 5G System (5GS) tracking area code (TAC) transmission in SIB1; and
in response to the core connectivity status information indicating to the DU that the CU have a connection with the core network, the DU is configured to enable SIB1 scheduling with 5GS TAC.
15 . The storage media of claim 13 , wherein, in response to the core connectivity status information indicating to the DU that the CU does not have a connection with the core network, the operations further comprise causing the DU to be in the active state; and
the operations further comprise, after causing the DU to be in the active state, in response to the CU gaining a connection with the core network, causing the DU to provide support to the SA UEs.
16 . The storage media of claim 13 , wherein the base station is a gNodeB, and the core network is a 5G core network.