The above-described example with respect to option A will be described below in more detail.
In a situation such as option A, slot boundaries with respect to links (an access link with a UE and a backhaul link with a child node) on which a node performs scheduling can be configured as follows. (Slot boundaries may mean boundaries of multiple slots in the present disclosure).
-
- Alt 1. A period from a period in which DL starts to a period in which another DL starts may be a slot boundary. In this case, G_UD and/or G_DU periods may be included in a slot.
- Alt 2. A period from a period in which DL starts to a period in which the next DL starts may be a slot boundary. In this case, G_UD and/or G_DU periods may be included in a slot.
- Alt 3. A period from a period in which DL starts to a period in which UL ends may be a slot boundary. Here, only one DL period and one UL period can be present in the slot boundary. In this case, a G_DU period may be included in a slot. Furthermore, in this case, a slot length can be set to be less than a conventional slot length by G_UD. In addition, a gap of G_UD may be present between slots.
- Alt 4. A period from a period in which DL starts to a period in which UL ends may be a slot boundary. Here, a plurality of DL periods and only one UL period can be present in the slot boundary. In this case, a G_DU period may be included in a slot. Furthermore, in this case, a slot length can be set to be less than a conventional slot length by G_UD. In addition, a gap of G_UD may be present between slots.