| Discussion and conclusion:
Qualcomm commented that they considered this a valid scenario for using legacy S1 for sending a second PDU before receiving a downlink PDU ack. Vodafone commented that it should be left to RAN WG3 to make this work. This was left for further off-line discussion and a response drafted in TD S2 160668. Final response in TD S2 160828.
TD S2 160668 (LS OUT) [DRAFT] Reply LS on Multiple uplink NAS PDUs in CIoT optimization. To: RAN WG3. CC: CT WG1, RAN WG2.
Discussion and conclusion:
Response to TD S2 160485. A number of clarifications were needed and this was revised, also to remove 'draft' in TD S2 160828 which was approved.
SCEF connection Issue
TD S2 160277 (DISCUSSION) Options to establish SCEF connection for Non IP data for CIoT. (Source: Cisco Systems Inc., Intel).
Abstract: Options to establish SCEF connection for Non-IP data for CIoT.
Discussion and conclusion:
Alcatel-Lucent commented that this suggests a chain of mappings which are unnecessary if option 2.1 is used. Qualcomm added that the SCEF ID can be included in DNS response messages. There was a long discussion on this contribution and it was concluded that the more clarification on whether the UE/Application needs to be aware of the type of connection set-up being used, or whether the service presented to the UE is uniform. This was then noted.
TD S2 160423 23.682 CR0154R5 (Rel 13, 'B'): Introduction of non IP data delivery via the SCEF for cellular IoT. (Source: Samsung, Alcatel-Lucent, Cisco Systems Inc, Nokia Networks, Intel). (Revision of TD S2 154400).
Abstract: Summary of change: The NIDD procedures are described; those procedures are: - Configuration for NIDD procedure - MO NIDD procedure - MT NIDD procedure.
Dostları ilə paylaş: | 
