Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 22.880 Word version: 14.0.0

0… 5…

5 On network Use Cases p. 10

5.1 MCData affiliation process p. 10

5.1.1 Description p. 10

5.1.2 Pre-conditions p. 10

5.1.3 Service Flows p. 10

5.1.4 Post-conditions p. 10

5.1.5 Potential Impacts or Interactions with Existing Services/Features p. 10

5.1.6 Potential Requirements p. 11

5.2 Air ground air communications (On network) p. 11

5.2.1 Description p. 11

5.2.2 Pre-conditions p. 11

5.2.3 Service Flows p. 11

5.2.4 Post-conditions p. 11

5.2.5 Potential Impacts or Interactions with Existing Services/Features p. 11

5.2.6 Potential Requirements p. 11

5.3 Large data distribution p. 11

5.3.1 Description p. 11

5.3.2 Pre-conditions p. 11

5.3.3 Service Flows p. 11

5.3.4 Post-conditions p. 11

5.3.5 Potential Impacts or Interactions with Existing Services/Features p. 12

5.3.6 Potential Requirements p. 12

5.4 Receiving and Transmitting Data and Voice p. 12

5.4.1 Description p. 12

5.4.2 Pre-conditions p. 12

5.4.3 Service Flows p. 12

5.4.4 Post-conditions p. 12

5.4.5 Potential Requirements p. 12

5.5 Management of Different Combination of Voice and Data p. 13

5.5.1 Description p. 13

5.5.2 Pre-conditions p. 13

5.5.3 Service Flows p. 14

5.5.4 Post-conditions p. 14

5.5.5 Potential Impacts or Interactions with Existing Services/Features p. 14

5.5.6 Potential Requirements p. 14

5.6 Concurrency of data and MCPTT service p. 14

5.6.1 Description p. 14

5.6.2 Pre-conditions p. 14

5.6.3 Service Flows p. 14

5.6.4 Post-conditions p. 14

5.6.5 Potential Requirements p. 15

5.7 Management of Different Sources of Data p. 15

5.7.1 Description p. 15

5.7.2 Pre-conditions p. 16

5.7.3 Service Flows p. 16

5.7.4 Post-conditions p. 16

5.7.5 Potential Impacts or Interactions with Existing Services/Features p. 16

5.7.6 Potential Requirements p. 16

5.8 Situational awareness p. 17

5.8.1 Description p. 17

5.8.2 Pre-conditions p. 17

5.8.3 Service Flows p. 17

5.8.4 Post-conditions p. 17

5.8.5 Potential Impacts or Interactions with Existing Services/Features p. 17

5.8.6 Potential Requirements p. 17

5.9 Sending a multimedia message to another user (on network, off network, IOPS) p. 17

5.9.1 Description p. 17

5.9.2 Pre-conditions p. 18

5.9.3 Service Flows p. 18

5.9.4 Post-conditions p. 18

5.9.5 Potential Impacts or Interactions with Existing Services/Features p. 18

5.9.6 Potential Requirements p. 18

5.10 Managing data group communications (on network, off network, IOPS) p. 18

5.10.1 Description p. 18

5.10.2 Pre-conditions p. 18

5.10.3 Service Flows p. 18

5.10.4 Post-conditions p. 18

5.10.5 Potential Impacts or Interactions with Existing Services/Features p. 19

5.10.6 Potential Requirements p. 19

5.11 Managing a one to one data communications (on network, off network, IOPS) p. 19

5.11.1 Description p. 19

5.11.2 Pre-conditions p. 19

5.11.3 Service Flows p. 19

5.11.4 Post-conditions p. 19

5.11.5 Potential Impacts or Interactions with Existing Services/Features p. 19

5.11.6 Potential Requirements p. 19

5.12 Multimedia message acknowledgement for group communications (on network, off network, IOPS) p. 20

5.12.1 Description p. 20

5.12.2 Pre-conditions p. 20

5.12.3 Service Flows p. 20

5.12.4 Post-conditions p. 20

5.12.5 Potential Impacts or Interactions with Existing Services/Features p. 20

5.12.6 Potential Requirements p. 20

5.13 Multimedia message acknowledgement one to one (on network, off network, IOPS) p. 20

5.13.1 Description p. 20

5.13.2 Pre-conditions p. 20

5.13.3 Service Flows p. 20

5.13.4 Post-conditions p. 21

5.13.5 Potential Impacts or Interactions with Existing Services/Features p. 21

5.13.6 Potential Requirements p. 21

5.14 Remote control p. 21

5.14.1 Description p. 21

5.14.2 Pre-conditions p. 21

5.14.3 Service Flows p. 21

5.14.4 Post-conditions p. 21

5.14.5 Potential Impacts or Interactions with Existing Services/Features p. 21

5.14.6 Potential Requirements p. 21

5.15 Command/control centre p. 22

5.15.1 Description p. 22

5.15.2 Pre-conditions p. 22

5.15.3 Service Flows p. 22

5.15.4 Post-conditions p. 22

5.15.5 Potential Impacts or Interactions with Existing Services/Features p. 22

5.15.6 Potential Requirements p. 22

5.16 Robots remote control (On network, off network, IOPS) p. 22

5.16.1 Description p. 22

5.16.2 Pre-conditions p. 22

5.16.3 Service Flows p. 22

5.16.4 Post-conditions p. 22

5.16.5 Potential Impacts or Interactions with Existing Services/Features p. 23

5.16.6 Potential Requirements p. 23

5.17 Robots identification (On network) p. 23

5.17.1 Description p. 23

5.17.2 Pre-conditions p. 23

5.17.3 Service Flows p. 23

5.17.4 Post-conditions p. 23

5.17.5 Potential Impacts or Interactions with Existing Services/Features p. 23

5.17.6 Potential Requirements p. 23

5.18 Database enquiry (On network) p. 24

5.18.1 Description p. 24

5.18.2 Pre-conditions p. 24

5.18.3 Service Flows p. 24

5.18.4 Post-conditions p. 24

5.18.5 Potential Impacts or Interactions with Existing Services/Features p. 24

5.18.6 Potential Requirements p. 24

5.19 Operational data synchronization p. 24

5.19.1 Description p. 24

5.19.2 Pre-conditions p. 24

5.19.3 Service Flows p. 26

5.19.4 Post-conditions p. 26

5.19.5 Potential Impacts or Interactions with Existing Services/Features p. 26

5.19.6 Potential Requirements p. 26

5.20 Call rejection and queuing (On network) p. 27

5.20.1 Description p. 27

5.20.2 Pre-conditions p. 27

5.20.3 Service Flows p. 27

5.20.4 Post-conditions p. 27

5.20.5 Potential Impacts or Interactions with Existing Services/Features p. 27

5.20.6 Potential Requirements p. 27

5.21 First aid use case p. 27

5.21.1 Description p. 27

5.21.2 Pre-conditions p. 27

5.21.3 Service Flows p. 28

5.21.4 Post-conditions p. 28

5.21.5 Potential Impacts or Interactions with Existing Services/Features* p. 28

5.21.6 Potential Requirements p. 28

5.22 Location Sharing Use Case p. 28

5.22.1 Description p. 28

5.22.2 Pre-conditions p. 28

5.22.3 Service Flows p. 28

5.22.4 Post-conditions p. 28

5.22.5 Potential Impacts or Interactions with Existing Services/Features p. 28

5.22.6 Potential Requirements p. 29

5.23 Multiple events and priority management (On network) p. 29

5.23.1 Description p. 29

5.23.2 Pre-conditions p. 29

5.23.3 Service Flows p. 29

5.23.4 Post-conditions p. 29

5.23.5 Potential Impacts or Interactions with Existing Services/Features p. 29

5.23.6 Potential Requirements p. 30

5.24 Mobility use cases p. 30

5.24.1 Description p. 30

5.24.2 Pre-conditions p. 30

5.24.3 Service Flows p. 30

5.24.4 Post-conditions p. 31

5.24.5 Potential Impacts or Interactions with Existing Services/Features p. 31

5.24.6 Potential Requirements p. 31

5.25 MCData Emergency Alert Triggered by Location p. 31

5.25.1 Description p. 31

5.25.2 Pre-conditions p. 31

5.25.3 Service Flows p. 32

5.25.4 Post-conditions p. 32

5.25.5 Potential Impacts or Interactions with Existing Services/Features p. 32

5.25.6 Potential Requirements p. 32

5.26 MCData Emergency Group Transmission p. 32

5.26.1 Description p. 32

5.26.2 Pre-conditions p. 32

5.26.3 Service Flows p. 32

5.26.4 Post-conditions p. 32

5.26.5 Potential Impacts or Interactions with Existing Services/Features p. 33

5.26.6 Potential Requirements p. 33

6 Off network Use Cases p. 33

6.1 Use case 1 p. 33

6.1.1 Description p. 33

6.1.2 Pre-conditions p. 33

6.1.3 Service Flows p. 33

6.1.4 Post-conditions p. 33

6.1.5 Potential Impacts or Interactions with Existing Services/Features p. 33

6.1.6 Potential Requirements p. 33

7 Isolated E-UTRAN Operation for Public Safety Use Cases p. 34

7.1 Use case 1 p. 34

7.1.1 Description p. 34

7.1.2 Pre-conditions p. 34

7.1.3 Service Flows p. 34

7.1.4 Post-conditions p. 34

7.1.5 Potential Impacts or Interactions with Existing Services/Features p. 34

7.1.6 Potential Requirements p. 34

8 Priority Management p. 34

8.1 Priority Management (On network) p. 34

8.1.1 Description p. 34

8.1.2 Pre-conditions p. 34

8.1.3 Service Flows p. 34

8.1.4 Post-conditions p. 35

8.1.5 Potential Impacts or Interactions with Existing Services/Features p. 35

8.1.6 Potential Requirements p. 35

9 Mobility p. 35

9.1 A complex network context p. 35

9.1.1 Different networks p. 35

9.1.2 Mobility management needs p. 35

9.1.3 Priority management between networks, load balancing between networks p. 36

10 Considerations p. 36

10.1 Considerations on security p. 36

10.2 Considerations on MCData service p. 36

10.3 Considerations on MCVideo requirements in IOPS mode p. 36

11 Potential Requirements p. 37

11.1 General p. 37

11.2 Consolidated requirements for new MCData services p. 37

11.2.1 Generic capabilities p. 37

11.2.1.1 Simple messaging capability p. 37

11.2.1.2 File distribution capability p. 38

11.2.1.3 Data streaming capability p. 39

11.2.1.4 IP proxy capability p. 39

11.2.1.5 Priority p. 40

11.2.2 MCData services common for on network and off network p. 40

11.2.2.1 Conversation management p. 40

11.2.2.1.1 Conversation management for one to many transmissions p. 40

11.2.2.1.2 Conversation management for one to one data transmissions p. 40

11.2.2.2 Data forwarding p. 40

11.2.2.3 Delivery notification p. 41

11.2.2.4 Location sharing p. 41

11.2.2.5 MCData emergency alert triggered by location p. 41

11.2.2.6 Robots p. 41

11.2.3 MCData services requirements specific to on network use p. 42

11.2.3.1 Database enquiries and secured internet access p. 42

11.2.4 MCData services requirements specific to IOPS mode p. 42

11.3 Consolidated requirements on open interface for MCData p. 42

11.4 MC Service interworking requirements p. 42

11.4.1 Groups p. 42

11.4.2 Affiliation p. 42

11.4.3 Simultaneous non coordinated use p. 42

11.4.4 Simultaneous coordinated use p. 43

11.4.5 Inter MCService priority and pre-emption p. 43

11.5 Consolidated requirements on mobility, priority management, service continuity and load balancing p. 43

11.5.1 Priority management p. 43

11.5.2 Mobility management p. 44

11.5.3 Load balancing p. 44

12 Conclusion and Recommendations p. 44

$ Change history p. 45