-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Context
- TS 26.502 (SA4) defines the Object Distribution Method for MBS User Services in clause 6.2.
- In particular, table 6.1-1 defines rules for populating the abstract Object acquisition identifiers baseline parameter for the four different operating modes of Object Distribution Method.
- TS 29.580 (CT3) specifies the API for provisioning MBS User Services in the MBSF via reference point Nmb10.
- TS 29.581 (CT4) specifies the API used by the MBSF to configure MBS Distribution Sessions via reference point Nmb2 based on those provisioned in MBS User Services.
Description
The semantic rules for populating the set of Object acquisition identifiers is underspecified in both TS 29.580 and TS 29.581.
Suggested solution
TS 29.580
For the case where distMethod is set to OBJECT, specify rules for populating objAcqIds in table 6.2.6.2.5-1 (ObjectDistrMethInfo) along the following lines:
- When objAcqMethod is set to PUSH, the array objAcqIds shall be empty.
- When operatingMode is set to COLLECTION or CAROUSEL, and objAcqMethod is set to PULL the array objAcqIds shall contain exactly one member.
TS 29.581
Add a second sentence in NOTE 2 to table 6.1.6.2.5-1 (ObjDistributionData) as follows:
NOTE 2: Either the objAcquisitionIdsPull attribute or the objAcquisitionIdPush attribute shall be provided, when available. In the case where
objDistributionOperatingModeis set toSINGLEandobjAcquisitionMethodis set toPUSH, the objAcquisitionIdsPull attribute shall be omitted and the objAcquisitionIdPush attribute shall be omitted, indicating that any object may be pushed to the MBSTF.
The above is consistent with table 6.1-1 in TS 26.502.
The current NOTE 2 text incorrectly identifies objAcquisitionIdsPush instead of objAcquisitionIdPush and this needs to be corrected.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status