Reply LS on issues related to support of IMS voice over NB-IoT NTN connected to EPC
This is a reply LS from RAN2 to SA2 addressing multiple technical questions related to the support of IMS voice over NB-IoT NTN (Non-Terrestrial Network) connected to EPC. RAN2 provides responses to specific questions raised by SA2 regarding RoHC, scheduling methods, DRB support, and SRB configurations.
SA2 Question: Does RAN2 have any observation on how many consecutive packets lost or erroneously decompressed will trigger the RoHC state fall back at the compressor when using RoHC?
RAN2 Response:
- RAN2 is not able to make any observation on this matter
- The implementation of ROHC functions (e.g., compression and decompression) falls outside of RAN2 scope
SA2 Question: Can RAN2 confirm whether scheduling methods for support of IMS voice over NB-IoT NTN can handle the voice packets of different sizes changing dynamically?
RAN2 Response:
- Scheduling methods may handle voice packets of different sizes through:
- Semi-persistent scheduling
- Dynamic scheduling
- Over-provisioning of resources in UL
- RAN2 will further study and discuss the details of the scheduling mechanism to avoid potential issues
SA2 Question: Is it feasible to support more than 2 DRBs for a UE accessing NB-IoT in Rel-20?
RAN2 Response:
- RAN2 understands that it is technically feasible to support more than 2 DRBs for a UE accessing NB-IoT in Rel-20
SA2 Question 9: Can RAN2 provide feedback on whether it is possible to define a new SRB that will be used to carry voice media?
SA2 Question 10: If the answer to the above question is yes, can RAN2 confirm whether such SRB(s) are defined, whether it is technically feasible to support and configure RLC UM for such SRB(s) for example: in NB-IoT deployments over GEO satellite, when SRBs are used to carry voice media?
RAN2 Response:
- RAN2 understands it is technically feasible to introduce SRB with RLC UM for voice packet
RAN2 discussed both Control Plane (CP) and User Plane (UP) solutions for supporting IMS voice over NB-IoT NTN:
RAN2 respectfully asks SA2 to take the replies and information provided into consideration.