A.2 Combined state diagram for gNB cell
28.5413GPP5G Network Resource Model (NRM)Management and orchestrationStage 2 and stage 3TS
This is the Combined state diagram for gNB cell.
Figure A.2-1: Combined gNB cell state diagram
The gNB-DU maintains cell states. The following table is the gNB cell state transition table.
In 3-split and 2-split deployment scenarios, the interactions between gNB-CU and gNB-DU are standardized. The interactions specified under the column "The state transition events and actions" of "The gNB Cell state transition table" below shall be present for the state transition.
In the non-split deployment scenarios, the interactions between gNB-CU and gNB-DU are not standardized. The interactions between gNB-CU and gNB-DU specified under the column "The state transition events and actions" of "The gNB Cell state transition table" can be replaced by other means that is not standardized.
Table A.2-1: The gNB Cell state transition table
|
Transition number |
The state transition event and actions |
|
1 |
Event: Receive request to unlock. Action: None. |
|
2 |
Event: Receive request to lock. Action: None. |
|
2a |
Event: Receive request to lock Action: Send to gNB-CU the "gNB-DU Configuration Update message" with served cell to delete. |
|
3 |
Event: When the required cell resource is physically installed and working. Action: none. |
|
4 |
Event: When the required cell resource is not physically installed or is not working. Action: Send to gNB-CU the "gNB-DU Configuration update message" with cell to delete. |
|
4a |
Event: When the required cell resource is physically uninstalled or is not working. Action: Send to gNB-CU the "GNB-DU Configuration Update message" with served cell to delete. |
|
5 |
Event: Receive from gNB-CU the "F1 Setup Response message" (identifying the cell to be activated). The cell is activated successfully. Actions: Do nothing or send gNB-CU the "gNB-DU Configuration Update message" with Cell stated as active’ —– or —– Event: Receive from gNB-CU the "gNB-CU Configuration Update message" (identifying cell to be activated e.g., in case that the cell was not activated using the "F1 Setup Response message"). Actions: The cell is activated successfully. Send to gNB-CU the "gNB-CU Configuration Update Response" to confirm the cell is in active state. —– or —– Event: Receive from gNB-CU the "gNB-DU Configuration Update Acknowledge message" (identifying cell to be activated e.g., in case that the cell was not activated using the "F1 Setup Response message") and the cell is activated successfully Actions: Do nothing. |
|
6 |
Event: Receive from gNB-CU the "gNB-CU Configuration Update message" and responds with gNB-CU Configuration Update Acknowledge messages. Actions: Respond with gNB-CU Configuration Update Acknowledge messages. —– or —– Event: Event: DU experiences an internal failure and decided to place the cell into inactive state. Actions: Send to gNB-CU the "gNB-DU Cell status Update message" |
|
7 |
Event: Send to gNB-CU the "F1 Setup request" (identifying the cell that is configured and ready to be activated). Actions: none. —– or —– Send to gNB-CU the "gNB-DU Configuration Update message" with the served cell to add. Actions: none. |
|
8 |
Event: Sends to gNB-CU the "gNB-DU Configuration Update message" with served cell to delete. Receive response from gNB-CU the "gNB-DU Configuration Update Acknowledge message". Actions: None. |
|
9 |
Event: Receive request to shut down. Actions: None. |
|
10 |
Event: Last user quit. Actions: Send to gNB-CU the "GNB-DU Configuration Update message" with served cell to delete. |
|
11 |
Event: When a cell is created and is configured. Actions: None |
|
12 |
Event: When a cell is deleted. Action: None. |
Annex B (normative):
NetworkSlice and NetworkSliceSubnet state handling