Content for TR 22.853 Word version: 13.0.0
4 Use cases
4.1 M2M service enablement related use cases
4.2 Application related use cases
5 Potential requirements
6 Conclusions and recommendations
A OMA Architecture Group Network API Dashboard
$ Change history
4 Use cases p. 6
4.1 M2M service enablement related use cases p. 6
4.1.1 Communication patterns p. 6
4.1.1.1 Description p. 6
4.1.1.2 Pre-conditions p. 6
4.1.1.3 Service flows p. 7
4.1.1.4 Post-conditions p. 7
4.1.1.5 Potential impacts or interactions with existing services/features p. 7
4.1.1.6 Potential requirements p. 7
4.1.2 M2M service provider setting via MTC Server various parameters for communication with is MTC devices p. 7
4.1.2.1 Description p. 7
4.1.2.2 Pre-conditions p. 8
4.1.2.2.1 For the broadcasting/multicasting case p. 8
4.1.2.2.2 For the QoS/prioritization case p. 8
4.1.2.2.3 For the scheduling case p. 8
4.1.2.3 Service flows p. 9
4.1.2.3.1 For the broadcasting/multicasting case p. 9
4.1.2.3.2 For the QoS/prioritization case p. 10
4.1.2.3.3 For the scheduling case p. 11
4.1.2.4 Post-conditions p. 11
4.1.2.5 Potential requirements p. 11
4.2 Application related use cases p. 12
4.2.1 Background traffic use cases p. 12
4.2.1.1 Description p. 12
4.2.1.2 Pre-conditions p. 12
4.2.1.3 Service flows p. 12
4.2.1.4 Post-conditions p. 12
4.2.1.5 Relationship with other standardized APIs/interfaces p. 13
4.2.1.6 Potential requirements p. 13
4.2.2 Use case on "Connection Properties Exposure" p. 13
4.2.2.1 Description p. 13
4.2.2.2 Pre-conditions p. 13
4.2.2.3 Service flows p. 13
4.2.2.4 Post-conditions p. 14
4.2.2.5 Relationship with other standardized APIs/interfaces p. 14
4.2.2.6 Potential requirements p. 14
4.2.3 Real-time exposure of Ues footprint p. 14
4.2.3.1 Description p. 14
4.2.3.2 Pre-conditions p. 14
4.2.3.3 Service flows p. 14
4.2.3.4 Post-conditions p. 15
4.2.3.5 Relationship with other standardized APIs/interfaces p. 15
4.2.3.6 Potential requirements p. 15
4.2.4 Charging model choice p. 15
4.2.4.1 Description p. 15
4.2.4.2 Pre-conditions p. 15
4.2.4.3 Service flows p. 16
4.2.4.4 Post-conditions p. 16
4.2.4.5 Potential impacts or interactions with existing services/features p. 16
4.2.4.6 Relationship with other standardized APIs/interfaces p. 16
4.2.4.7 Potential requirements p. 16
4.2.5 Monitoring on application usage use cases p. 16
5 Potential requirements p. 18
5.1 Requirements covered by other existing features p. 18
5.2 Potential additional requirements p. 18
6 Conclusions and recommendations p. 22
A OMA Architecture Group Network API Dashboard p. 23
$ Change history p. 24
