Open rjb1000 opened 1 year ago
Draft Change Request to TS 26.517 V17.2.0 here:
Decision to merge the above draft CR into a consolidated CR from @haudiobe at SA4#123-e:
Qualcomm contribution to SA4#123-e incorporates this change:
Change Request revised and noted at SA4#123-e:
This will be further developed at SA4#124 Berlin, including possible merger of related CRs.
Included in CR contributed to SA4#124 (Berlin) by @haudiobe:
CR endorsed as the basis for further work at SA4#124 (Berlin):
No notable progress at SA4#125.
Latest draft CR contributed by @haudiobe was endorsed:
Pushing on to SA4#126.
No notable progress at SA4#126.
Latest draft CR contributed by @haudiobe was endorsed:
Offline editing in progress.
Pushing on to SA4#127.
The Schedule Description has been extensively reworked by @tlohmar, @rjb1000 and @haudiobe in the run up to SA4#127 (Sophia Antipolis) and was endorsed at this meeting:
Further offline editing to occur after this meeting with power granted to SA4 ad hoc meeting to agree a revision of CR0001 to be sent to SA#103 (Maastrict) for agreement.
Result of offline editing after SA4#127:
Power granted to SA4 ad hoc meeting to agree a revision to be sent to SA#103 (Maastricht) for agreement.
Following online editing, Change Request agreed by ad hoc meeting:
This has agreed status in SA4:
Sent to SA#103 (Maastricht) for approval in CR Pack SP-240272.
Background
TS 26.517 describes a Schedule Description metadata unit that is used to advertise the (optional) time schedule for MBS data transmissions.
Problem description
This is a contradiction.
Suggested solution
My assumption is that the Schedule Description metadata unit is intended to apply to the User Service Description since it is provisioned at this level in TS 26.502.
Amend the text in clause 5.2.7 paragraph 2 to align with figure 5.1-1.